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

Externals not executing in Runtime

Binettoid

Ts 7.1 w LS.
Hi guys,
I have a page calling several prefixes and externals from a couple of different components. In the TeamSite preview it works fine but when i publish it to "production" (= our staging server) Runtime, neither of the two components seem to execute. They should both be calling a UserManager.java : loadUser method. A page that only calls this from one component works fine in the same runtime.
Anyone have any idea why?
Any tips appreciated!

Find more posts tagged with

Comments

Emanuel

Did you check the caching policy of the components??

"cache until published" components may have odd behaviour with dynamic externals.

vpatel

Did you deploy the relevant JAR / Java / Config files to your Runtime when you deployed the .page file?

Binettoid

Hi guys, thanks for your responses.

Ok cacheing issues might make some sense - what would you suggest for a component that handles user logins and is session-based and shown on most pages? Is "do not cache" a complete no-no, performance-wise?

I did deploy all the relevant jar files ( build, build runtime.zip, extract to LiveSiteDisplayServices/runtime/web ) and as I said, another page using the component works fine.

N.B. I've since noticed that redeploying sometimes fixes this issue. One page is now fixed (the one running multiple components calling the same external) but another one is still broken.
Sadly my deploy PLC -> production has been playing up and is now failing reliably, so I am not able to re-publish pages any more.....

vpatel

If re-publishing is fixing your problems then it sounds more like caching issue...Given that, if a component is truely dynamic then you should not cache it -- for example a login or targeted component wouldn't be normally cached. Yes performance-wise a non-cached would be more expensive than a cached component but you want that security/experience with relevant components.