Fixed Layout Component Update Error

All,

Seeing this weird issue, we have created a new custom fixed layout:

<Canvas Id="simple" html-id="simple-id" css-class="simple-canvas" row-spacing="10px" inline-css="false">
<Name>Simple <Row Id="row-0">
<Area Id="row-0-area-1" component-spacing="0" width="liquid">
<Name>Main</Name>
</Area>
</Row>
</Canvas>

Created a page using this layout, added a single, simple component, Finished/Closed. Touch/Submit the component then repoen the page, the Out-of-Date dialog opens, if Update or Overwrite clicked will cause the following message:

"One or more components on the page have not been displayed because the area to which they belong has been removed from the fixed layout configuration.

When you save the page these components will be permanently removed from the page.

To recover these components, you should cancel page edit (without saving changes) and restore the area that has been removed from the fixed layout configuration."

The page then opens with no components.

Any ideas what might be causing this?

Adam.

TS 6.7.2

Out-of-Date Fixed Layout Custom

Find more posts tagged with

Comments

Faizi

Have you checked your log file?

As per your TS version you should check servletd log file. That will give some pointer. In later version log file is content_center.

You can see some OOTB fixed-layout examples in component-guide site.

Rick Poulin

Created a page using this layout, added a single, simple component, Finished/Closed.

Are you sure you created a brand new page after modifying the layout?

What happens is that SitePub remembers changes you made in the current session, even if you haven't saved them. What could have happened is you added a component, then deleted that area from the layout, then went back to editing that page. The component won't be rendered (because it has nowhere to live), but it's still "on the page" (in the Java BusinessPage object's component mapping), which is why that error would come up upon any action that would modify the BusinessPage object.

Azudio

rpoulin - The page was a new page created with the new layout adding ain sample component. 'Finished', closed, component was then touched, submitted. Page was reopened, Out-of-Date dialog opened, Update, message shown saying that the area has been removed. At no stage was the layout altered.

Faiz- In the loggers admin page I set to debug the entire com.interwoven.livesite classes and reloaded and monitored the logs - no exceptions or warnings/errors shown, so no helpful clues there either.

Adam.

Rick Poulin

rpoulin - The page was a new page created with the new layout adding ain sample component. 'Finished', closed, component was then touched, submitted. Page was reopened, Out-of-Date dialog opened, Update, message shown saying that the area has been removed. At no stage was the layout altered.

Ok well then create a new page this way, add your component, then save and close.

Then before reopening, inspect the .page XML. Specifically, look at each instance matching the following XPath, and make sure the value matches an Area/@Id in your layout definition.
/Page/Page_Content/Component/ContainerProperties/FixedLayoutArea/@ID

Also make sure that you get the expected layout file name at /Page/Page_Display_Properties/PageType/Layout/@canvas-path

If that's still not it.. make sure your layout is submitted so that no workarea version contradicts staging maybe.. I'm reaching, but maybe your older version has an issue with something like that.

edit: you could also try using more 'unique' IDs in your layout.. I'm reaching, but maybe your version gets confused with those IDs, since they're in the same format as what it generates when you don't explicitly specify them.

Azudio

Ok well then create a new page this way, add your component, then save and close.

Then before reopening, inspect the .page XML. Specifically, look at each instance matching the following XPath, and make sure the value matches an Area/@Id in your layout definition.
/Page/Page_Content/Component/ContainerProperties/FixedLayoutArea/@ID

Also make sure that you get the expected layout file name at /Page/Page_Display_Properties/PageType/Layout/@canvas-path

If that's still not it.. make sure your layout is submitted so that no workarea version contradicts staging maybe.. I'm reaching, but maybe your older version has an issue with something like that.

edit: you could also try using more 'unique' IDs in your layout.. I'm reaching, but maybe your version gets confused with those IDs, since they're in the same format as what it generates when you don't explicitly specify them.

This is the results of this test:

simple.xml (layout file, snip)
...
<Area Id="row-0-area-1" component-spacing="0" width="liquid">
<Name>Main</Name>
</Area>
...

/Page/Page_Content/Component/ContainerProperties/FixedLayoutArea/@ID = <FixedLayoutArea ID="row-0-area-1" index="0"/>

/Page/Page_Display_Properties/PageType/Layout/@canvas-path = <Layout canvas-path="simple.xml">fixed-layout</Layout>

So it all looks ok, so I'm not sure why SP is unable to link up correctly. To clarify this error only happens when you click Update or Overwrite, if you cancel, the page opens with the component still there (as expected) with the component highlighted in yellow, but if I then 'check for updates' and Update it throws the same error and the component disappears, so its clearly something in the update process that is failing.

Rick Poulin

So it all looks ok, so I'm not sure why SP is unable to link up correctly. To clarify this error only happens when you click Update or Overwrite, if you cancel, the page opens with the component still there (as expected) with the component highlighted in yellow, but if I then 'check for updates' and Update it throws the same error and the component disappears, so its clearly something in the update process that is failing.

What about using a different syntax for your IDs.. does that work any better?

Sounds like you might need to open a case with support (I agree -- your page XML values look as they should).