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

Can a Page-Post-Controller forward a rendered page to another URL

Paul Neiswander

Windows 2008 64 R2

Teamsite/LS 7.4.1

We are trying to utilize SitePublisher to create pages that will generate Freemarker scripts instead of HTML. This means that after LiveSite renders the page we need to forward the page to the Freemaker servlet for processing and sending back to the user (and doing a bunch of other integrations). We are trying to give the authors their "normal" authoring experience with hafving to "publish" to a DEV Freemarker preview server .... etc.

Can anyone confirm that a post-page controller is accomplish this? I have seen what seems to be conflicting documentation -- one that controllers can use ForwardAction to and others that suggest Post-Page controllers execute "before" externals - which implies that run for the page is fully rendered.

If this cannot be done - or is a bad idea - I would appreciate any other ideas - especially if this or something similar has been done before.

Thanks

Paul Neiswander

Find more posts tagged with

Comments

Rick Poulin

It can't be done because LiveSite writes to the reponse writer directly. That means that once a page gets rendered, there is no further opportunity to internally forward the request.

What you could do, however, is use SitePub to generate your "pages" on the authoring side and then publish that as freemarker assets, optionally doing some post processing in workflow. This way, you still retain the authoring experience per your requirements, you're just not using LiveSite as the rendering engine.

cesarecastro

We too had a requirement to generate custom html (its actually xml encoded html) while maintaining the previewing and authoring experience in Teamsite.

We ended up with using standard html 5 templates that work in TeamSite integrated with our custom CSS that work both in TeamSite and our Site. Hence avoiding the need to deploy to a preview server as the content displays in TeamSite exactly how it displays on the site.

This was accomplished, as it was explained before, by processing the SitePub output html in the workflow.

PNeiswander

Thanks to both of you for you input.

I had a feeling the post-page forward was not going to work. I was trying to avoid the alternative "post-processing into freemarker assets" approach or duplicating the page generation logic into two different rendering methods.

We might be able to utilize the HTML 5 approach - maybe I can externanlize the Freemarker calls and rendere them into the component.

Anyway - much apprecated.

Paul Neiswander