Archive for December, 2012

CQ5.5 SP2.1: Links/References are not updated following move/rename

Issue

If you are using CQ5.5 SP2.1 and move/rename pages in the tree, you may notice that the links/references to those pages are not updated as expected.

Method

Add links in /content/geometrixx/en/products/triangle.html, pointing to the parent page, a sibling page, and a child page.
Move /content/geometrixx/en/products to /content/geometrixx/en/productsRenamed.

Result

None of the links in /content/geometrixx/en/products/triangle are adjusted to the new target /content/geometrixx/en/productsRenamed/….

Reason

This works in the base version CQ 5.5 and is a regression introduced by SP 2.1

Solution

This issue will be fixed in the next service-pack for CQ5.5 and later versions.  If you require a hotfix for this issue for SP2.1, please contact the support team through Daycare and request “cq-5.5.0-hotfix-2582″.

reference: (40612/CQ5-23844)

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

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: 10.0/10 (1 vote cast)

LiveCycle Designer ES2: Designer hangs after renaming the binding file

Issue

While editing an XDP in certain versions of LiveCycle Designer ES2, if the data binding file on disk is renamed, designer registers this change and offers to reload the current form.  If you then click Save, it again offers to reload the current form.  After clicking “Yes” to reload the form, you may notice that Designer hangs.

Method:
1. Download test_files.zip
2. Extract the 2 files to the same local folder
3. Open XDP in Designer
4. Rename the binding XML file in your local folder
5. You will see a dialog in Designer asking to reload the form, click Yes
6. Click Save
7. Again the dialog in Designer asking to reload the form, click Yes

Result:
Designer hangs

Solution

This is an issue in certain versions of LiveCycle Designer ES2 and has been addressed in later versions, including Designer ES3.  If you require a quickfix for this issue in LiveCycle Designer ES2 you should contact the enterprise support team.

reference: (183667516/3337854)

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

LiveCycle Designer ES2: Multiple pages imported to a single Master Page causing overlap

Issue

If you are importing a multi-page PDF into LiveCycle Designer ES2 to create a form using the “…Flowable Layout > Place Content In > Master Pages” method you may notice that the content of the pages are placed in a single Master page causing overlap.

Solution

This is an issue in LiveCycle Designer ES2 and has been addressed in later versions, including Designer ES3.  If you require a quickfix for this issue in LiveCycle Designer 9 you should contact the enterprise support team.

reference: (183629724/3337453)

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

LiveCycle Designer ES2: Corners appear unexpectedly when clicking on hidden rectangle object

Issue

If you are editing older XDP forms from LiveCycle Designer 7.1, or 8,  in Designer ES2, and you have hidden rectangle objects in the form design, you may notice that when selecting these hidden objects in the hierarchy, visible corners suddenly appear on these objects.  These hidden rectangle objects are created automatically when importing Word documents into Designer to create a form.

Reason

The problem is caused by the import from doc/PDF where the edge property for the rectangle is created and set to hidden, but no corners property is created.  When you create a new form in Designer (without importing), the edge and corner properties for a rectangle are always created together and the presence for both usually kept in synch.
It seems that when Designer finds a rectangle without a corner property it creates it automatically with visible corners.

Rectangle in XML after import from word:
               <rectangle>
                  <edge thickness=”0pt” presence=”hidden”/>
               </rectangle>

Rectangle in XML after selecting it on canvas:
               <rectangle>
                  <edge thickness=”0pt” presence=”hidden”/>
                  <corner radius=”5.08mm”/>
               </rectangle>

Rectangle in XML after manually fixing it in Designer (XML Source or Object Palette):
               <rectangle>
                  <edge thickness=”0pt” presence=”hidden”/>
                  <corner radius=”5.08mm” presence=”hidden”/>
               </rectangle>

Workaround

You can change the line style to “solid” and back to “none”, and then the corners property in XML is synchronized (presence=hidden) with the line edge property as expected.

Solution

This is an issue in LiveCycle Designer ES2 and will be fixed in Designer 10 and later versions.  If you require a quickfix for Designer 9 you should contact the enterprise support team.

The logic has now been changed, so that when Designer creates the corner property, it checks if the relevant edge is hidden, and sets the presence for the corners to match.

reference: (183589079/3322036)

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