If you are using the sidekick on an author instance of CQ, you may notice that the toolbar at the bottom which includes the design and preview mode buttons, is not visible or available.
The functionality in the sidekick is determined by the ACLs (Access-Control-Lists) defined in the CQ server. If you do not have the appropriate privileges then functionality may be hidden in your sidekick. Sometimes the sidekick may become unstable if you add faulty components to the page, or after you have installed some packages that may have overwritten required objects in your application, breaking some dependencies.
You should first try to clear your browser cache, and then reload the page from WCM console to refresh the sidekick.
You should also ensure you have the correct privileges to access the appropriate design in /etc/designs. This can be changed by an administrator on the Users tab in the siteadmin console. If the privileges appear to be correct, then try to disable them, save, and then re-enable them and save. The sidekick should now display the toolbar again as expected.
In CQ5.4 you could start the server in debug mode using the [CQ_HOME]/crx-quickstart/server/server.bat file. The server folder is no longer there in CQ5.5 on Windows.
To start the server in debug mode you can edit the [CQ_HOME]/crx-quickstart/bin/start.bat file and add the same debug parameters from a server.bat in an existing CQ5.4 installation, or you can use the command line below:
java -Xmx512m -Xdebug -Xrunjdwp:transport=dt_socket,server=y,address=30303,suspend=n -jar cq-author-4502.jar
You may notice that the “Attach Debugger” entry in the CRXDE menu is still disabled even after starting the server in debug mode. You should analyse the console output on server startup to check for issues related to heap/memory problems which may result in a new process being forked. The debug options used to start the parent JVM are not passed on to the forked process by default.
You can resolve this by adding more heap to the JVM, and/or by specifying the -nofork command line option to prevent forking. You can also force the forked process to use the parent JVM parameters by specifying the -forkargs [<arg>...] command line option.
You can find more information on the options mentioned above, and other server startup options under the following link: