If you are using CQ5 in Internet Explorer 8 or 9, you may notice phantom fields appearing after dismissing a dialog in the browser, and then scrolling the browser page.

TestCase1
1) Goto /content/geometrixx/en/toolbar/feedback.html
2) Open the dialog of one field (eg. Name)
3) Cancel the dialog
4) Scroll the browser window
=> Phantom form fields appear.

TestCase2
1) Goto /content/geometrixx-outdoors/en/men.html
2) Open the edit dialog of the “Navigation Products”-Component
3) Click on “Cancel”
4) Scroll the browser window
=> Phantom form fields appear.

Reason

This issue is caused by a problem in the CSS which controls the layout of the page in author mode.

Solution

This issue will be fixed in CQ 5.6.1 and later versions.

Workaround

To workaround this issue in CQ5.5  SP2.1 you can use the following overlay to fix the CSS: reset_css_overlay_44088-1.0.zip

reference: (44088/CQ5-29678)

Overview of tools in 1st release:

• Logs Viewer – Provides an easy way to download all CQ logs.  The tail functionality will open a new window and start tailing the log file.  Multiple log directories can be configured via Logs Tail Plugin.  The crx-quickstart/logs is used as default if configuration is not bound.  This tool can also be used with curl.  Allows you to package up all the logs in one single click making it easy to provide the logs when opening a Daycare ticket.  Detailed info here: http://helpx.adobe.com/content/help/en/cq/kb/logsviewer.html
• Tar PM Scan – Scans tar files and displays node path and size for each record.  This can be useful when analyzing abnormal workspace growth.  Large individual node sizes could indicate a flat hierarchy (i.e. a large child node list > 1000).  The same nodes appearing repeatedly in the scan could indicate a code issue or some other problem related to updating the same nodes repeatedly.  Detailed info here: http://helpx.adobe.com/content/help/en/cq/kb/tarpmscan.html
• Thread Dumps Collection & Analysis - Takes thread dumps at regular intervals and saves them in a file under crx-quickstart/threads.  The page will also display a list of links to existing thread dump files.  The tool can use jstack, if it is installed on the system, or JVM MBean.  Detailed info here: http://helpx.adobe.com/content/help/en/cq/kb/thread-dumps-collection-analysis.html
• Content Compare & Import – Used to compare and import content differences from one CQ instance to another CQ instance.  This helps to ensure consistency across servers.  Detailed info here: http://helpx.adobe.com/content/help/en/cq/kb/contentcompareimport.html

Download and install

The tools are supported for use with CQ5.5, AEM5.6 and later versions.  Here are the instructions to download and install the support tools: http://helpx.adobe.com/cq/kb/support-tool-installation.html

If you are using the classic UI (/socoadmin) for social moderation in AEM5.6, you may notice some strange behaviour as follows

If you are activating images in DAM, and then searching for those images in DAM search as detailed below, you may notice that the image activation status appears as “pending” in the search results.

1. Open DAM
2. Navigate to a folder with images (example: /content/dam/geometrixx/banners)
3. Activate all the images.
4. Ensure that the image status is published.
5. Switch to DAM search.
6. Enter a search string (example: .png)

Result: The activated images appear as pending for activation.

Reason

This is an issue in CQ5.5 and has been resolved in AEM 5.6 and later versions.

Solution

Upgrade to AEM 5.6.

reference: (43813/CQ5-23686)

If you are using custom ECMA scripts in workflows with CQ5, you may encounter an error similar to the following when executing the workflow:

*ERROR* POST /etc/workflow/instances HTTP/1.1] com.day.cq.workflow.rule.impl.ScriptingRuleEngine
Unable to execute rule /etc/workflow/scripts/workitem.ecma: Failure running script /etc/workflow/scripts/workitem.ecma:
ReferenceError: “workItem” is not defined (/etc/workflow/scripts/workitem.ecma#2)
org.apache.sling.api.scripting.ScriptEvaluationException: Failure running script /etc/workflow/scripts/workitem.ecma:
ReferenceError: “workItem” is not defined (/etc/workflow/scripts/workitem.ecma#2)

Reason

In an OR step for a workflow, only the workflowData, jcrSession, and workflowSession objects are available to be used within the check() function.

Solution

You should use the workflowData, jcrSession, and workflowSession objects in your ECMA script to implement the logic.

reference: (44185/CQ5-11022)

If you are using CQ5.3/CRX2.2 you may notice the following error in the log files:

*ERROR* DelegatingObservationDispatcher: Error while dispatching events. (DelegatingObservationDispatcher.java, line 129)
 java.lang.NullPointerException
  at org.apache.jackrabbit.core.security.authorization.acl.CompiledPermissionsImpl.canRead(CompiledPermissionsImpl.java:215)
  at org.apache.jackrabbit.core.security.DefaultAccessManager.canRead(DefaultAccessManager.java:251)
  at org.apache.jackrabbit.core.observation.EventConsumer.canRead(EventConsumer.java:306)
  at org.apache.jackrabbit.core.observation.EventConsumer.prepareEvents(EventConsumer.java:158)
  at org.apache.jackrabbit.core.observation.ObservationDispatcher.prepareEvents(ObservationDispatcher.java:184)
  at org.apache.jackrabbit.core.observation.EventStateCollection.prepare(EventStateCollection.java:459)
  at org.apache.jackrabbit.core.observation.DelegatingObservationDispatcher.dispatch(DelegatingObservationDispatcher.java:126)
  at org.apache.jackrabbit.core.observation.DelegatingObservationDispatcher.dispatchEvents(DelegatingObservationDispatcher.java:99)
  at org.apache.jackrabbit.core.observation.EventStateCollection.dispatch(EventStateCollection.java:475)
 ...

Reason

This error occurs due to an issue in Jackrabbit issue: https://issues.apache.org/jira/browse/JCR-3272.

It occurs as the canRead() method in CompiledPermissionsImpl.java is checking for read access on an item that does not exist anymore.  It should therefore throw a RepositoryException, instead of resulting in an NPE.

We have had previous reports of this issue, but it did not have any effect on the server state or stability. In the later hotfixpacks for CRX, this NPE will be logged at the WARN level and not ERROR.

Solution

This has been fixed in a later release of the Jackrabbit core, version 2.4.  You can ignore this error or apply the latest crx-hotfixpack from PackageShare to resolve the problem.

reference: (43919/CRX-4113)

If you are using Chrome with CQ5.5 SP1 and attempting to insert variables into newsletters as detailed below, you may notice that the variables are not inserted as expected.

You are searching in CQ5 for text contained within assets like PDF & Word documents in DAM, and not getting any results.

Solution

This issue is resolved in CQ5.5 SP1 and SP2 and later versions.  You should download these updates from PackageShare and update your CQ instance.

After updating CQ new documents in DAM will be indexed, but the existing documents will not.  Perhaps this is acceptable if you are just setting up a new instance, and do not have any existing documents that you need indexed.

To get existing documents indexed, you will have to re-build the lucene index as follows:
[1] Open http://<host>:<port>/system/console/bundles
[2] Find the ID for the following bundles

• Apache PDFBox (org.apache.pdfbox)
• Apache Tika core (org.apache.tika.core)
• Apache Tika parsers (org.apache.tika.parsers)

[3] Look into crx-quickstart/launchpad/felix for the folders corresponding to the 3 IDs in [2]:

• crx-quickstart/launchpad/felix/bundleXX

[4] For each bundle in [3], change the value in the bundle.startlevel from 15 to 14
[5] Restart CQ and check in the Felix console that the 3 bundles has the start level set to 14.
[6] Stop CQ
[7] Delete crx-quickstart/repository/workspaces/crx.default/index folder
[8] Restart CQ and wait for the indexing to complete

reference: (44511/GRANITE-761)

If you are deploying a system bundle fragment for the 1st time to CQ, you may notice that the CQ server shuts down.

Solution

This issue is fixed in later CQ versions.  If you have an M&S contract and require an urgent hotfix for this in CQ5.5 SP2.1 you should contact Daycare support.

Workaround

Restart the CQ instance manually and everything should work as normal.

reference: (44186/NPR-2555)

If you have installed a hotfix for CRX you may encounter problems accessing CRXDE Lite accompanied by the following error in the server.log:

*MARK * servletengine: Servlet threw exception:
java.lang.IllegalStateException: I18nManager not initialized
at com.day.crx.i18n.I18nManager.getInstance(I18nManager.java:59)
at org.apache.jsp.de.index_jsp._jspService(index_jsp.java:59)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:98)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:328)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:315)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at com.day.j2ee.servletengine.ServletRuntimeEnvironment.service(ServletRuntimeEnvironment.java:228)
at com.day.j2ee.servletengine.RequestDispatcherImpl.doFilter(RequestDispatcherImpl.java:315)
at com.day.j2ee.servletengine.RequestDispatcherImpl.service(RequestDispatcherImpl.java:334)
at com.day.j2ee.servletengine.RequestDispatcherImpl.service(RequestDispatcherImpl.java:378)
at com.day.j2ee.servletengine.ServletHandlerImpl.execute(ServletHandlerImpl.java:315)
at com.day.j2ee.servletengine.DefaultThreadPool$DequeueThread.run(DefaultThreadPool.java:134)
at java.lang.Thread.run(Thread.java:662)

Reason

This problem is usually caused by a version mis-match in JAR library files which were installed through the CRX hotfix.

Solution

You should check for JAR conflicts with the versions contained in the hotfix as listed in the hotfix release notes.

You may need to copy the JAR files from:

…\crx-quickstart\server\runtime\0\_crx\WEB-INF\lib

to here:

…\crx-quickstart\server\lib\container

If this is a non-quickstart installation, then there are instructions in the HF release notes to manually delete older versions of JAR libs:

“Make sure to delete previous versions of installed Java libraries below <crx-webapp>/WEB-INF/lib to avoid classloading issues.”

reference: (33826)

Issue

If you are using a ClearableComboBox widget on the second tab of a dialog, the widget is rendered with 0px width after selecting a value, which means the value is hidden/clipped.

-Install attached package into a CQ instance, it’s a modified dialog for the text component
-Open /content/geometrixx/en.html and drag a text component to the parsys
-Open the dialog for the text component
-Click on the tab “Bug Test” and select a value from the Combobox “ClearableComboBox”
-Important: Click on the tab “Text” to move away from the “Bug Test” tab
-Close the dialog with OK and open it again (usually just switching between tabs also shows the issue)
-Click on the tab “Bug Test”

Result: ClearableComboBox is rendered with no width, so value is not visible

Expected: ClearableComboBox to be rendered correctly so value is visible (ComboBox works fine)

Workaround
Using the ClearableComboBox widget on the 1st tab in the dialog, works fine.

Solution

You must add a new property hideMode to the dialog tab (not the combobox) in your custom text component, and set it’s value to offsets.  See the following screenshot for more details.

With this property set, the combobox width is maintained even when the dialog tab/panel is not visible.

reference: (43540/CQ5-29349)

Event Type:    Error
Event Source:    Application Error
Event Category:    None
Event ID:    1000
Date: …
Time: …  
User: … 
Computer: …
Description:
Faulting application acrobat.exe, version 10.1.4.38, faulting module acrobat.dll, version 10.1.4.38, fault address 0×00021212.

Reason

This is an issue with Acrobat/Reader 10.1.4 affecting compatibility with this LiveCycle plugin.

Solution

This issue is fixed in Acrobat/Reader 10.1.5 and later versions.

reference: (3322093)

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)

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)