Stories
Slash Boxes
Comments

SoylentNews is people

Submission Preview

Link to Story

User Messages Improved! (After a Hiccup)

Accepted submission by martyb at 2020-07-07 15:31:48
Rehash

I rolled out an improvement to the site's message processing template. =)

tl;dr Messages that someone replied to a comment you had posted now contain links that take you directly to the *comment* instead of to the *story*. I made a mistake rolling out the change which will show up as extra text (__seclev__ 500 __version__ $Id$) below the text of the message. That was live for about an hour and is now fixed. Enjoy the new convenience!

Read on for more details, if you are curious.

Previously, when you got a message that a user had replied to a comment you posted, you'd get links in the message that took you to the story. Then, you'd have to scroll down to see the actual message. Now, clicking on either message link takes you directly to the message, itself.

Before:

The Mighty Buzzard has posted a comment, Re:resolution choice [soylentnews.org], in reply to your comment, resolution choice [soylentnews.org], attached to Fraunhofer HHI Announces Finalization of H.266/VCC Codec, With Up to 50% Bitrate Reduction vs. H.265 [soylentnews.org].

After:

The Mighty Buzzard has posted a comment, Re:resolution choice [soylentnews.org], in reply to your comment, resolution choice [soylentnews.org], attached to Fraunhofer HHI Announces Finalization of H.266/VCC Codec, With Up to 50% Bitrate Reduction vs. H.265 [soylentnews.org].

Unfortunately, I made a mistake in updating the *in-memory* copy of the template (default;comments;reply_msg). I accidentally included text that is needed in the template *file* (/rehash-master/plugins/Messages/templates/reply_msg;comments;default)

Though they *appear* the same, as text, the links under "Re:resolution choice" and "resolution choice" are different.

The Mighty Buzzard noticed the error and was instrumental in tracking it down. (Thanks Buzz!)

Any messages that were *generated* during this time (today between 1400-1500 UTC give-or-take) will show:

__seclev__ 500 __version__ $Id$

at the bottom of the message text.

Things should be back to normal; I apologize for any inconvenience my mistake caused.

(I'd prefer you think it was part of my Sooper Sekret plan to get TMB to help test my changes! =)


Original Submission