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

stderr or stdout from an external that fails during preview

Bowker

Is there a log file where stderr or stdout is sent for an external while previewing a component? My External is "blowing up" and I don't know what the error is.

Find more posts tagged with

Comments

tec_iwov

you should be using standard logging and try catch blocks.

for rendering these will end up under [teamsite install dir]\local\logs\iwui\livesite.preview.log

Rick Poulin

you should be using standard logging and try catch blocks.

for rendering these will end up under [teamsite install dir]\local\logs\iwui\livesite.preview.log

They'll end up in that log unless you've redirected logging for your custom classes with the log4j.xml config (which I'd recommend doing). However, that log should contain any uncaught exceptions, and a similar one should be catching them on the runtime. Note that when components blow up, the stack trace is usually printed as an HTML comment in the crapped page as well.