Comments / Mentions Bug Fixed

Kansas City, Missouri
May 21, 2013 3:58pm CST
A bug was introduced with a recent upgrade that placed double @@ symbols when clicking on the "Comment" link underneath someone else's comment. As a result, these were not recorded as mentions as desired. This bug has been fixed and released to the website.
4 people like this
3 responses
@GoAskAlice (5811)
21 May 13
Awesome! I'll cross this one off the list then.
2 people like this
22 May 13
1 person likes this
22 May 13
@PhredWreck It's part of Mylot's biological warfare plot.
1 person likes this
@owlwings (43915)
• Cambridge, England
22 May 13
@GoAskAlice It's all to do with DNA. If you release corrected bugs onto the website, it is hoped that they will breed with the rest of the bugs and produce 'corrected' offspring. Of course, as every programmer knows, correcting one bug and releasing it into the wild very often generates five more completely new and unrelated ones - especially if the code hasn't been documented or annotated.
1 person likes this
@owlwings (43915)
• Cambridge, England
22 May 13
The bug still exists in the "Report" screen, however: "Reporting this post will flag @@myLotBugs for a violation of myLot's Rules for Acceptable Conduct. Are you sure you wish to continue?" (Naturally, I answered "No" once I had copied the text!) Incidentally, it is still quicker to type the formatting codes. Highlighting the text to be formatted and hitting one of the 'format' buttons merely puts an open and close code in at the start of the highlight. Yes, it is possible to choose the format before typing but you then have to manually place the cursor between the codes, which is tricky and basically useless. [u]Nesting codes[/i] (even when done correctly) does not work at all.
1 person likes this
@owlwings (43915)
• Cambridge, England
22 May 13
I promise that I did type those nested codes correctly! (And re-did it three times). The editor actually changes the codes and turns the 'close underline' into a 'close italic'!
@buenavida (9985)
• Sweden
21 May 13
Another bug I detected. I went to an old discussion and tried to delete one of the responses but it did not disappear, except for a little while. Then the response was there again. I hope this will work in the future. Thanks for working to correct bugs!
@owlwings (43915)
• Cambridge, England
22 May 13
@PhredWreck If the 'Delete' button was there at all, then @buenavida must have been trying to perform a legitimate action, therefore it does look like a genuine bug.
1 person likes this
@owlwings (43915)
• Cambridge, England
22 May 13
@PhredWreck You are allowed to delete: 1) Your own comments and responses. 2) Any comments/responses which are below one of your posts in the hierarchy.
1 person likes this
@owlwings (43915)
• Cambridge, England
22 May 13
@PhredWreck I said "allowed" but I suppose I should have said "clearly meant to be allowed"! I believe that I did once manage to delete a comment to one of my responses (both the response and the comment were made before the new site was up, as I recall). I seem to remember checking back on the discussion and seeing that the comment had stayed removed but I can't be certain about that.
1 person likes this