- David McMahon
If you are installing and starting a new CQ instance you may experience the following exception:
*ERROR* [FelixStartLevel] org.apache.jackrabbit.core.RepositoryImpl failed to start Repository: Unable to register data store in cluster.
javax.jcr.RepositoryException: Unable to register data store in cluster.
Caused by: java.net.UnknownHostException: <server_hostname>: <server_hostname>
… 56 more
To view the solution, read the original blog post at The Adobe Enterprise Product Blog.
Check out some useful tips and tricks published as part of the CQ Best Practice content series:
- Useful variations in the authoring environment URL
- Troubleshoot CRXDE performance issues
- Advanced CRX search
- Validate user input in multifield components
- Define how users can interact with a component
- Include resources in JSP files
Read the article here: http://helpx.adobe.com/content/help/en/adobe-cq/using/tips-tricks.html
- David McMahon
If you are using the CQ5.5 authoring environment to add links to DAM assets through the rich-text editor dialog by drag-and-drop, then you may notice that some of these links will be marked invalid after clicking OK on the dialog.
A invalid link appears like the “banking” text below, whereas a valid link appears like the “investors” text.
You may also see errors similar to the following in the error.log:
*ERROR* [0:0:0:0:0:0:0:1  GET /libs/wcm/core/content/pageinfo.json HTTP/1.1] com.day.cq.wcm.core.impl.servlets.PageInfoServlet Request path does not resolve to a resource: /content/dam/geometrixx/documents/GeoSphere_D%20a%20tasheet.pdf
The links are marked invalid when the assets in DAM contain spaces in the file-name (e.g. GeoSphere_D a tasheet.pdf). Such file-names are being parsed by a URL encoder and the spaces get converted to the %20 code at the wrong place.
Read the workaround at The Adobe Enterprise Product Blog.
We’ve just published two new articles in the CQ best practice series:
A list of the five articles published so far is at this URL. In the days to come, we’ll post more best practices, tips, and tricks that you can apply to your work.
Read the original blog post at The Doc Fox.
-- Jörg Hoh
About a year ago I wrote an improved version of backup for CRX 2.1 and CRX 2.2. The approach is to reduce the amount of data which is considered by the online backup mechanism. With CRX 2.3 this approach can still be used, but now an even better way is available.
A feature of the online backup — the blocking and unblocking of the repository for write operations — is now available not only to the online backup mechanism, but can be reached via JMX.
Read the complete post at Things on a Content Management System blog.
- Samartha Vashishtha, Content and Community Lead @ Adobe
We’ve just published the following three CQ best practice articles:
These articles are the first few in the CQ best practices series. In the days to come, we’ll post more best practices, tips, tricks, and troubleshooting information that you can apply to your work.
Read the original post at The Doc Fox.
- Scott Macdonald, Senior Content and Community Lead @ Adobe
Have you ever wondered how to create a custom CQ widget that performs tasks not available with out of the box CQ components. In this situation, you can create a CQ widget that uses third-party libraries that lets your CQ application perform custom tasks. For example, assume that you want to create a CQ application that lets you view a specific street by using Google Map APIs.
Perhaps, you want your CQ component to accept latitude and longitude values and then show the results, as shown in the following illustration.
If you are interested in learning how to create CQ components that use third-party libraries, then check out the following article: http://helpx.adobe.com/adobe-cq/using/integrating-custom-cq-widgets-third-party.html.
Read the original post at Scott's Digital Community.
- Sensei Martin
Have you worked out that TAR Optimiser does not run at midnight? Normally, the OOTB default for running the TAR optimiser is 2am - 5am. This can be changed in the repository.xml/workspace.xml files. But, if you specify a start time of 00:00 it won't run. I'm sure I've posted this elsewhere but just to re-iterate you can make the TAR optimiser run faster & do more work by reducing the optimizeSleep parameter. We've managed to get away with 0.25 without any noticeable performance impact to the live servers (CQ 5.3).
This tip was originally posted at the My Day CQ Blog.