When creating a version of a page, it appears that Hybris recursively follows all attributes of the page in order to make clones of dependencies. This appears
to include fields such as page navigationNodes and restrictions, which relate to other pages. The result is that when versioning a page that is part of a nav
node hierarchy or page restriction's page set, all of the pages in that hierarchy get versioned at once. With a handful of nav nodes, and a few restrictions
containing a few dozen pages each the attempt to version one page takes (at least) several hours, or fails with a stack overflow in a server environment. A
stack trace is attached.
Pages that don't have nav nodes and don't have restrictions that contain multiple other pages get versioned quickly.
We would normally expect that versioning a page would include creating versions of its slots, components, etc., but would not include other pages that the
target page is loosely related to through things like nav nodes.
SAP Commerce 1811
KBA , CEC-COM-CPS , SAP Commerce , CEC-COM-CPS-WEB , Store frontend, Web CMS, Accelerators , Problem
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.