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; } } }

Potential bug in UI Toolkit XML

System

Thanks to Greg Zevin's help, I think we uncovered either a documentation bug or a bug in the XML parser that processes the UI configuration files (ui_custom.xml). Every place in the UI Customization Guide where it gives examples for adding Custom Menu Items, it closes the <link> tag with </link>, which is what I did in an example I initially could not get to work properly - I kept getting a bizarre error when trying to log into TeamSite after rebuilding the web app. When I tried it again, changing only the end tag for the <link> tag to />, then it works. So either the docs are wrong or the XML parser is not doing the right thing when it encounters a </link> tag.

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

Find more posts tagged with

Comments

gzevin

Dave,

just a little correction - I believe that the parser is wrong - because you still were writing a valid and DTD-valid XML - the parser should not really care what kind of notation you are using - say, in DCTs you can use either <text> </text> or simple <text ... /> tags ....

but let's wait for the answer ...

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU

Migrateduser

Looks like I am a moron again today. David Yun caught my problem with my XML and I was missing an ending > at the end of my opening <link tag, which is why I was getting errors. I apologize for jumping the gun and thinking the bug was in the product. The bug was just sitting in my chair.

However, even though I am an idiot, I am not a complete idiot. I stared at that XML for hours and didn't see that missing >. In fact, because of the obscure error messages I was getting (see attached file if you are curious what the error messages were) I wasn't sure if it was my XML, or a value was incorrect in one of my name/value pairs, or if there was a special character somewhere I couldn't see. I didn't know what I was looking for because the error message didn't tell me. In workflow, if I have badly formed XML in my job spec, it tells me. In OpenDeploy, if I mess up my XML config, the admin tool shows me exactly where it's badly formed. I think a similar mechanism needs to be in place for the UI Toolkit. When my customization configs get to be as big, or bigger, as the one in the customer_samples path, badly formed XML is going to be a needle in a haystack to find without better error messaging.

But still, in this case, I messed up.

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

Migrateduser

I forgot to attach my error messages...

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

Gregg Faus

Yeah that is unfortunate that a syntax error like that cannot be error handled better. Fortunately though, that is why a product XMLSpy is so handly. If you don't want to pony up the money, you can find free validation tools out there too.

Migrateduser

I'm guessing most, if not all, XML Validation tools require a DTD to verify against? If that's the case, then until Interwoven gives us those DTDs I'm pretty much screwed. According to the docs for the UITK they can't expose the DTDs just yet - unless I'm reading the doc wrong.

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

preflight.PNG

properties.PNG

Gregg Faus

Well I guess I was just referring to the lowest form of validation which is ensuring XML is well-formed. I guess validation against a DTD would be quite nice too, but as you say, these aren't available yet.

gzevin

in general, I'd say that the install_webapps tool should alert if something is wrong, *before* we see that the GUI is broken Smiley Happy

)

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU