Posts tagged "siteadmin"

CQ5.5 SP1: Editing page properties in siteadmin does not work correctly

Issue

If you are using CQ5.5 SP1 and you edit the page properties in siteadmin, this may not work as expected.  For example, vanity URLs added to the page properties may not work correctly.

Reason

The issue with the page properties occurs because the node jcr:primaryType gets changed from cq:PageContent into nt:unstructured, due to a change in the latest Sling POST servlet.  The only way to avoid this node change with SP1  is to edit the page properties of a page using the sidekick within each page view.

Solution

This issue is resolved in CQ5.5 SP2.1, and later versions.

Workaround

If you cannot update to SP2.1 at this time there is a workaround using an overlay which you can install to avoid this problem.

Download and install the attached content package (SiteAdmin.Actions.js-overlay_40752.zip), containing an overlay of SiteAdmin.Actions.js, which prevents the nodetype of the jcr:content node being changed to nt:unstructured.  Once the package is installed, please make sure to clear your browser cache to avoid potential client-side caching issues.

After upgrading to SP2.1 be sure to remove this overlay.

reference: (40752/CQ5-18787)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 7.0/10 (3 votes cast)

CQ5: new page/site buttons disabled in WCM siteadmin

Issue

If you are using WCM siteadmin and wish to create a new page/site using the available buttons, they may appear disabled so that you are unable to click on them.  Firstly, you should check your permissions for these actions and/or check with an administrator or admin account.  If these problems persist it may be related to an issue in your repository structure.

Reason

These buttons can also be disabled if there is an invalid Page node in the /content tree.  A cq:Page node must have a child named jcr:content of type cq:PageContent, otherwise it is invalid and can lead to this issue.  The root /content node is not of type cq:Page and therefore does not require a jcr:content child of type cq:PageContent, but every other Page node below /content should have this structure.

It seems that if the invalid node is a top-level page/site in the content tree (e.g. /content/geometrixx) then it will affect the site actions for all other top-level nodes, and other nodes in that specific tree.
If the invalid node is a sub node (e.g. /content/geometrixx/en/services), then it seems to only affect the site actions for that level in that tree.

Such invalid nodes can appear in the tree if they were created outside of WCM (i.e. using CRXDE, or Content Explorer), or by importing a package containing such invalid nodes.

Solution

Check your content tree for such invalid page nodes, and repair the nodes as required, by creating a jcr:content child node of type cq:PageContent.

reference: (37890)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 10.0/10 (2 votes cast)

CQ5.4: How to display a confirmation dialog when activating pages

Issue

If you are using CQ5.x you will notice that there is a confirmation dialog for deleting/deactivating pages in the WCM console.  No such confirmation dialog is presented when you activate a page.  In some projects it may be a requirement to present such a confirmation dialog for activation also.

Solution

You will have to overlay:
/libs/cq/ui/widgets/source/widgets/wcm/SiteAdmin.Actions.js
to
/apps/cq/ui/widgets/source/widgets/wcm/SiteAdmin.Actions.js
Create the same folder structure in apps and then copy the SiteAdmin.Actions.js node from libs to the same folder in apps. This will ensure the jcr:content node under the JS file is also copied.

Then edit the SiteAdmin.Actions.js from apps.  You should replace the CQ.wcm.SiteAdmin.activatePage function with the lines (435-520) from this SiteAdmin.Actions.js file.

Note

Ideally you should not not completely overlay the siteadmin.Actions.js as you might run into problems when a SP brings a new SiteAdmin.Actions.js with it. Instead just overlay the function you want to change.  Use the clientlib approach and create a new JS file, attach it to the same clientlib as the SiteAdmin.Actions.js and redefine the function you want to change in that new JS file.

reference: (35823)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 1.0/10 (1 vote cast)