TS762 to TS732 upgrade .page structure changed

All,

From TS 672 to 7.3.2 the .page xml structure seems to have changed.
Since the .page files generated by the system are rendered by an external rendering engine, all new or updated content wil break the rendering, hence the customer website.

The new structure has the elements ….. added around the element

6.7.2:structure

templatedata/portalcontent/linklist/data/linklist-footer

....etc

7.3.2:structure

templatedata/portalcontent/linklist/data/linklist-footer

....etc

I like to understand this structure change and more important, would like to know if it is possible to have the pages rendered in the old structure again.

TIA

Find more posts tagged with

Comments

Rick Poulin

Since the .page files generated by the system are rendered by an external rendering engine

Say what? You/they built something custom to render .page artifacts? If I read that right, you're so far off the supported path that you should have expected this kind of thing, especially jumping 6 years' worth of TS history.

I like to understand this structure change and more important, would like to know if it is possible to have the pages rendered in the old structure again.

The reason for it is that it plays into the targeting functionality, whether you use it or not. AFAIK, LiveSite has page converters that automatically upgrade older page formats, but I don't know offhand if it converts your page whenever you edit+save it, or whether it does this at runtime (presumably it's both). But one thing's for sure, you can't expect TS7.3.2 to produce pages in the old structure going forward, so you might as well just deal with it as part of your upgrade.

Say what? You/they built something custom to render .page artifacts? If I read that right, you're so far off the supported path that you should have expected this kind of thing, especially jumping 6 years' worth of TS history.

I explained the situation unclear.

The .page files are published to a websphere application server, where the websphere application 'renders' the .page xml to present it.
Nothing special is done in teamsite with the pages.

LiveSite has page converters that automatically upgrade older page formats, but I don't know offhand if it converts your page whenever you edit+save it, or whether it does this at runtime.

So far I found it's done during edit and save.

The reason I want to keep the old structure for now is that I can control development/change actions on the TeamSite side in this company.
Getting changes (regardless how small) done in the websphere application takes ages to implement since that has to go trough an extremely lengthy and burocratic change process.

I therefore look for an intermediate solution to at least finish the TS upgrade.

And don't worry, once that websphere application is updated to handel the new structure, I'll return in TS to that new default structure as well. Although less experianced with livesite, I've been around the TeamSite block long enough to know not to mess with TS core and defaults (to much).

It will probably be an extra WF task or DNR solution to update the XML structure when files are published.

Rick Poulin

Gotcha. TS 7.3 publishing to a LS 6.7 runtime. That's just crazy talk.

I'd suggest doing the opposite, if you absolutely can't keep them in sync. LS 7.3 *should* be able to render pages published by TS 6.7. Even so, you said there's no bottleneck on upgrading the authoring side, so why not start your TS upgrade the minute the runtime upgrade goes through? What's the rush on upgrading TS, only to implement a bunch of unsupported hacks to make the output look like 6.7? Not to mention, your preview may very well behave differently than your runtime, leading to unexpected weirdness after deployment. And the worst thing for users is the unexpected. You can't come back from that.

Migrateduser

If anyone knows were I can find the local DTD(s) for the page files, we can make sure we stick to that definition.