Posts tagged "dialog"

CQ5.5: When to restart CQ after installing a service pack


If you are installing a service pack (SP) on top of CQ5.5 you will see a dialog recommending to restart the instance after you have run the SP installation:

Do not restart the instance at this point, as the contents of the service pack are still being extracted and installed in the background.  Restarting at this point could result in unknown problems, and you may have to repeat the SP installation.


You can monitor the log output in error.log and wait until the log no longer has new “BundleEvent STARTED” entries, before restarting the instance.  This usually takes 2 – 5 minutes depending on server specifications.

Monitoring log output may not be a good solution for large enterprise organisations which may have many CQ instances to update, and may need to use some kind of automated install script or process documentation.  In this case, you can either add a pause to the installation documentation (e.g. 15 or 30 minutes), or use a script to check for installation completion as described under 2 below.

1. Monitor the log output to figure out when to restart

The release notes for SP2.1 do contain instructions relating to this process (

Quickstart Install Process

  1. Login to Package Share and download SP2 package:
  2. Back in Package Manager – Install package
  3. After the package install is done – the PackageManager tells you to restart. DO NOT RESTART. The actual install of the package only starts now in background, given that the packages have been placed in /install folders. The best way to follow the process of the install is to tail the error.log
    The background install starts with “ Extracting day/cq550/update:cq-update-pkg:5.5.8” and stops with bundles been restarted – best seen by “BundleEvent STARTED” log entries.
  4. After the error.log goes quiet with “BundleEvent STARTED” messages
  5. Restart the instance
  6. The Welcome Screen should now show the updated Version String: Adobe CQ, Version Service Pack 2

2.  Use a script to automatically check for installation completion

You can use the script below which polls the server to check when the SP contents have been extracted, and then waits another few minutes for the relevant bundles to be started.  You can use the script on its’ own, or you could integrate it into existing scripts which you use to automatically install the CQ servicepack.

1. use a script similar to the following (designer for CQ5.5 SP2.1, you may need to adjust the cq-update-pkg version for other service packs)

until [ $res -eq 0 ]
    curl -u admin:admin -D- http://<cq_server_hostname>/etc/packages/day/cq550/update/ 2>/dev/null | head -1 | grep -q “HTTP/1.1 200”
    if [ $((count++ % 10)) -eq 0 ]
     echo “Waiting for service pack installation to finish…”
    sleep 1
sleep 300
echo “Service pack installation complete. You can restart the instance now.”

2. start the script in a terminal
3. install SP2.1
4. check the script output and await the completion message

5. restart the instance

reference: (39810/CQ5-22648)

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

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


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.


You will have to overlay:
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.


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: 6.5/10 (4 votes cast)

Acrobat/Reader: how to disable the “Reading Untagged Document” dialog


When you open a PDF document in Acrobat/Reader you may encounter the following dialog:

You may want to disable this dialog from appearing as it can effect your productivity if it appears for every document you open.


Accessibility tools like screen readers are used to read the contents of PDF files displayed in Acrobat/Reader.  Screen readers rely on the documents tags to read the contents of the document.  This dialog appears when Acrobat/Reader detects that screen reader software is installed and informs the user that the document has no tags (and therefore cannot be read by any screen reader).  The dialog is used to then create tags for the document so that it is accessible.

Windows itself has screen readers installed by default in certain versions and these may be activated causing this dialog to appear.  We have also received reports that other non-Accessibility software and device drivers cause this dialog to appear, as the software and drivers incorrectly use some system flags usually reserved for Accessibility tools.


We are working with Accessibility software vendors to find a more reliable way of registering such software to ensure Adobe Acrobat/Reader correctly detect it.  The goal is to avoid Accessibility functionality being launched in Acrobat/Reader due to the mis-use of the system flags by non-Accessibility software.

In the meantime you can use one of the workarounds below to avoid this issue.


You can prevent this dialog from appearing in a number of different ways:

1. Always use the default settings and create tags for the document

In this case you should just select the option “Always use the settings from the Reading preferences (Do not show this dialog again)”.  The options defined in the Acrobat/Reader Preferences under the Reading section will be used to create tags for each PDF file (that do not already contain tags) opened in Acrobat/Reader.

2. Disable the confirmation dialog in the Preferences

You can also disable this “Readung untagged document” dialog in the Reading Preferences by un-checking the option Edit > Preferences > Reading > “Confirm before tagging documents”.  This option writes the following registry key which could also be used for enterprise deployments:

[HKEY_CURRENT_USER\Software\Adobe\Acrobat Reader\9.0\Accessibility]


You can also disable the Accessibility Setup-Assistant dialog using the following registry key:

[HKEY_CURRENT_USER\Software\Adobe\Acrobat Reader\9.0\Accessibility]


3.Remove the Accessibility plugins from Acrobat/Reader

If you do not require any accessibility features in Acrobat/Reader and you have not been successful disabling the dialog using the methods above, then you can always close Acrobat/Reader and remove the Accessibility.api and ReadOutLoud.api from the plugins folder.  You should keep a copy of these plugins in another folder as a backup.  When you restart Acrobat/Reader it should no longer display this dialog.

reference: (182470670/1877982)

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

Acrobat/Reader: how to handle the Adobe Approved Trust List (AATL) update dialog


When you use Adobe Acrobat or Reader to open PDF documents that were signed or certified using certificates, you may see the following message:

A new security settings update is available from Adobe Systems.  Would you like to install it now?”  This dialog is a trusted Adobe dialog referring to updates to the root certificate list (AATL) in Acrobat or Reader.


AATL or Adobe Approved Trust List is a program that allows millions of users around the world to create digital signatures. The signatures are trusted whenever the signed document is opened in Adobe Acrobat 9 or Reader 9 or later.  The list of trusted certificates is updated from time to time in case some certificates have been added, renewed, or have expired.

These updates are distinguished from the standard product updates for Acrobat or Reader, which can be triggered by choosing Help > Check For Updates.

Related preferences

If you want to check for certificate updates, choose Edit > Preferences > Trust Manager > Click Update Now under the section Automatic Updates. The same update dialog box opens. Using this option, the certificate updates are loaded from a trusted server.

To enable the automatic update check, choose Edit > Preferences > Trust Manager > Load Trusted Root Certificates From An Adobe Server.  To enable the automatic check without any notification, deselect Ask Before Installing.

Assuming that you have enabled the automatic check, the certificate updates are triggered under the following conditions:

  1. you open a file that has a digital signature, and
  2. you have never checked for updates before, or
  3. you have checked before, but
    1. 28 days have elapsed and
    2. there is a new update available

You can select Yes and the trusted certificate list in Acrobat or Reader is updated. If you want to see the trusted list, choose Open Adobe Reader > Document > Manage Trusted Identities. In the window that opens, choose Display > Certificates. The entire Trusted Certificates list currently installed with your Reader appears.

Enterprise deployment

If you are working in an enterprise environment and want to control these settings for an enterprise deployment, use the Customization wizard to activate or deactivate these options.

Additional information

 reference: (182278250)

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

Acrobat/Reader: suppress the dialog after signing a PDF with a PenPad


 If you are using a PenPad to sign PDF documents in Acrobat or Reader you will receive the following dialog after successfully signing the document:

You may wish to disable this dialog permamently to avoid it displaying to the end-users.


 You can allow the dialog to appear once, and the users can then select the checkbox “Do not show this message again“.  Alternatively you can add a registry key which will disable this dialog permanently:

HKCU\Software\Adobe\Adobe Acrobat\10.0\AVAlert\cCheckbox\cppklite\isignDone REG_DWORD, 1

reference: (181681026/2662231)

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

LiveCycle Workbench ES: QPAC properties dialog not appearing for LC7 components


When importing processes from LiveCycle7 into Workbench ES, and clicking on the LiveCycle7 component in Workbench, the properties dialog for that component may not appear. This behaviour can also be observed when attempting to drag one of these LiveCycle7 components onto a new process map in Workbench.


When the LC7 Components in Workbench have not been updated to be compatible with the ES compatibility layer, you will not see the properties dialog. Most QPACs from LC7 need to be updated for use in LC ES, especially to use the new “lc7form” variable, in place of the old LC7 “form” variable type.

This information can be found in the following document:

If you analyse the QPAC JAR file and open the in a text editor, you can check the version. The version of Adobe’s QPACs which are compatible with ES all start with version 8.x for example “AdobeVersion:”. If the version of the QPAC is 7.x, then it has not been updated for use in ES. This applies to the Adobe QPACs only. Other software vendors may not use the same version numbering.


Get a version of the QPAC compatible with the LC ES compatibility layer, and deploy it in the LC7.x Components view in Workbench ES. You will then be able to view and change the properties of the activities in your LC7 imported process maps.

reference: (180802977/2302710)

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