nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Brought down our Site with a simple change to the Sitemap!

Bowker

Did you know that you can't put special characters (like = for example) in the value of a parameter in the sitemap?

If you do your LiveSite Display Services server will invalidate the whole site.

This probably is not what you would want to do!

(Yes that's an hour of my life I'll never get back!)

Find more posts tagged with

Comments

nipper

I knew there was a thread about that before. Did not know it would bring the site down. That is kind of abrupt. Nice way to start a Thursday.

RonaldV

Maybe we should explain the ls-developers about xml-encoding?

Bowker

I thought the same, but as it turns out you can't put an equal sign ( = ) in the value either. That's okay to put into XML. The only thing I can think of is that there is a parsing error with splitting on the =. I believe the same issue occurs if you put a name in without a value.

ISCBorisB

I thought the same, but as it turns out you can't put an equal sign ( = ) in the value either. That's okay to put into XML. The only thing I can think of is that there is a parsing error with splitting on the =. I believe the same issue occurs if you put a name in without a value.

You may want to try = (or = same thing) instead. I certainly do not know if that will work, but it should be trivial to test.

Bowker

Actually you would want to use %3d for and equal sign. The name "query-string" implies "URL Encoding" not "HTML Encoding"

However, I'm not comfortable having "users" convert this stuff correctly. Therefore I have told them only letters, numbers, forward slash, percent, period, dash and underscores are allowed.

ISCBorisB

Actually you would want to use %3d for and equal sign. The name "query-string" implies "URL Encoding" not "HTML Encoding"

True, but this is just another variation of the same "Numeric Entity" theme. You will not know what (if anything)
works until you try. Whatever name implies, if the query gets parsed first, decimal and hex entities are interchangeable
as far as any XML parser is concerned