none
> special symbols in headings > bug " / ' \ RRS feed

  • Question

  • > special symbols in headings > bug "  / ' \

    In topik subjects special symbols appears like (>) as you can see in this topic.


    Best regards, Sergiu
    Monday, June 29, 2009 2:10 PM

Answers

  • Sorry. We had an issue before the June release (about 2 weeks before that) in which new threads with special characters such as &, #, ", etc... are being stored as HTML encoded values. Part of the release for June included a lot of encoding fixes. However, since some of those thread titles with special characters we're already stored as HTML encoded values (" etc...) and we needed to decode those characters back to it's non encoded values.

    Basically, some of those characters we're being HTML encoded upon save and we needed to decode those values.

    Any new threads after the June release (6/25) is fine. The issue started to occur on 6/12.

    Thank you
    STO Forums Test Lead
    • Marked as answer by Sergiu Dudnic Tuesday, June 30, 2009 5:16 PM
    Tuesday, June 30, 2009 4:40 PM

All replies

  • Check this thread.
    Hans Passant.
    • Marked as answer by Sergiu Dudnic Monday, June 29, 2009 5:07 PM
    • Unmarked as answer by Sergiu Dudnic Tuesday, June 30, 2009 5:16 PM
    Monday, June 29, 2009 3:19 PM
  • Do you see any other threads that actually have html encoding strings in the thread title?

    If so, post it here. We've cleaned up a lot of those threads last week.

    Thanks.
    STO Forums Test Lead
    Monday, June 29, 2009 7:32 PM
  • what is means "cleaning"? if new threads appears, you should "clean" it every time?
    Best regards, Sergiu
    Tuesday, June 30, 2009 7:42 AM
  • Sorry. We had an issue before the June release (about 2 weeks before that) in which new threads with special characters such as &, #, ", etc... are being stored as HTML encoded values. Part of the release for June included a lot of encoding fixes. However, since some of those thread titles with special characters we're already stored as HTML encoded values (" etc...) and we needed to decode those characters back to it's non encoded values.

    Basically, some of those characters we're being HTML encoded upon save and we needed to decode those values.

    Any new threads after the June release (6/25) is fine. The issue started to occur on 6/12.

    Thank you
    STO Forums Test Lead
    • Marked as answer by Sergiu Dudnic Tuesday, June 30, 2009 5:16 PM
    Tuesday, June 30, 2009 4:40 PM