none
HTML quoting is "baaaaack" RRS feed

  • Question

  • It's been a chronic problem one way or another.  Back in spades with the today's update.  Check the thread titles:

    http://social.msdn.microsoft.com/Forums/en-US/vclanguage/thread/79fc4002-2471-4e47-906d-a477d92301f2
    http://social.msdn.microsoft.com/Forums/en-US/suggest/thread/3d7dd534-44e9-4f25-b211-a718910861bd
    http://social.msdn.microsoft.com/Forums/en-US/winforms/thread/50f6baf5-e4fd-4373-8d47-1fba10339d07
    Hans Passant.
    • Edited by nobugz Friday, June 26, 2009 1:03 AM
    Friday, June 26, 2009 12:16 AM

Answers

  • Our team fixed around 950+ threads this morning that had the HTML encoding strings in the thread title. We should be done fixing all of those threads in the next hour.

    Thanks all for the patience.

    Fyi, New threads that got submitted in the first and second week of June got affected.


    STO Forums Test Lead
    • Edited by Don Tan Friday, June 26, 2009 7:10 PM
    • Proposed as answer by Don Tan Friday, June 26, 2009 7:10 PM
    • Marked as answer by nobugz Friday, June 26, 2009 11:01 PM
    • Unmarked as answer by nobugz Friday, June 26, 2009 11:01 PM
    • Unproposed as answer by nobugz Friday, June 26, 2009 11:01 PM
    • Marked as answer by nobugz Friday, June 26, 2009 11:01 PM
    Friday, June 26, 2009 1:03 AM

All replies

  • Hi Hans,

    We'll fix those thread titles. This release included encoding fixes that allows thread titles to take valid XML chars. In the last Forums update, thread titles are being encoded upon input (saved) in turn being stored in the backend as the actual html encoded string.

    Thanks.
    STO Forums Test Lead
    Friday, June 26, 2009 12:55 AM
  • Our team fixed around 950+ threads this morning that had the HTML encoding strings in the thread title. We should be done fixing all of those threads in the next hour.

    Thanks all for the patience.

    Fyi, New threads that got submitted in the first and second week of June got affected.


    STO Forums Test Lead
    • Edited by Don Tan Friday, June 26, 2009 7:10 PM
    • Proposed as answer by Don Tan Friday, June 26, 2009 7:10 PM
    • Marked as answer by nobugz Friday, June 26, 2009 11:01 PM
    • Unmarked as answer by nobugz Friday, June 26, 2009 11:01 PM
    • Unproposed as answer by nobugz Friday, June 26, 2009 11:01 PM
    • Marked as answer by nobugz Friday, June 26, 2009 11:01 PM
    Friday, June 26, 2009 1:03 AM
  • I can see you editing the titles.  Old threads are fine, just new threads added after the update get mangled.  How long do you plan to keep this up?  I added another one.

    Hans Passant.
    Friday, June 26, 2009 1:11 AM
  • Nope, old threads get mangled too when somebody posts to them.

    Hans Passant.
    Friday, June 26, 2009 1:25 AM
  • This release should have the correct encoding fixes. Unfortunately, any threads that's been created since our last release (2 weeks ago) will need to be fixed.

    Please post any threads that you see with encoded titles and I'll be more than happy to fix it. "or" if you're a moderator of that Forum, you can right click on Edit and open it a new window and click Save. When you did, it's going to edit the thread with the correct html char and re-save it. It may ask you to enter a reason.

    Thanks again and apologize for the churn regarding these encoding issues
    STO Forums Test Lead
    Friday, June 26, 2009 1:25 AM
  • Btw, there are a lot more threads out there (roughly ~700 threads that are affected - last 2 weeks) with html encoding values in the thread title. I'll work with the team to mass fix those titles.

    Thanks.


    STO Forums Test Lead
    Friday, June 26, 2009 1:39 AM
  • Wow, that had to be painful.  Thanks.

    Curious: what happened two weeks ago?

    Hans Passant.
    Friday, June 26, 2009 11:00 PM
  • A couple of weeks ago we deployed an update to fix a few bugs, this update also unfortunately introduced the encoding issue Don mentioned above that was fixed with yesterday's update. So we basically had a couple weeks worth of threads with improperly encoded subjects.
    Community Forums Program Manager
    Saturday, June 27, 2009 5:02 AM
    Answerer