Posts tagged "button"

CQ5: new page/site buttons disabled in WCM siteadmin


If you are using WCM siteadmin and wish to create a new page/site using the available buttons, they may appear disabled so that you are unable to click on them.  Firstly, you should check your permissions for these actions and/or check with an administrator or admin account.  If these problems persist it may be related to an issue in your repository structure.


These buttons can also be disabled if there is an invalid Page node in the /content tree.  A cq:Page node must have a child named jcr:content of type cq:PageContent, otherwise it is invalid and can lead to this issue.  The root /content node is not of type cq:Page and therefore does not require a jcr:content child of type cq:PageContent, but every other Page node below /content should have this structure.

It seems that if the invalid node is a top-level page/site in the content tree (e.g. /content/geometrixx) then it will affect the site actions for all other top-level nodes, and other nodes in that specific tree.
If the invalid node is a sub node (e.g. /content/geometrixx/en/services), then it seems to only affect the site actions for that level in that tree.

Such invalid nodes can appear in the tree if they were created outside of WCM (i.e. using CRXDE, or Content Explorer), or by importing a package containing such invalid nodes.


Check your content tree for such invalid page nodes, and repair the nodes as required, by creating a jcr:content child node of type cq:PageContent.

reference: (37890)

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

Acrobat/Reader 10: Save button not working for PDFs referenced from long URLs


If you are using Adobe Acrobat/Reader in Firefox/Chrome to view PDF files from long URLs you may notice that  the Save button is not working as expected.  It may be disabled (greyed out), or it may be enabled, but clicking on the button does not bring up the Save dialog to save the PDF to the local file system.

In some organisations the PDF files may be loaded from complex applications which require long URLs to serve parameters with the PDF.  For example:

The URL above will show the PDF, but the Save button will not work as expected:


This is an issue with some versions of Adobe Acrobat/Reader 10 in Firefox/Chrome, and will be resolved in a later update for Acrobat/Reader.  The issue occurs when the URL contains more than 259 characters, as Firefox attempts to use this URL as the file-name in the Save dialog.  Such a long URL can exceed a file system limit and therefore the Save dialog does not appear.


  • Use shortened URLs to avoid the issue.
  • Use Acrobat/Reader in Internet Explorer.
  • Use Acrobat/Reader 9 with Firefox/Chrome.


This issue does not happen with the latest version of Acrobat/Reader 11, and will be fixed in a future release of Acrobat/Reader 10.

reference: (183411841/3319248)

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

Acrobat/Reader 9: HTTP submit button does not open local files


Security restrictions in Adobe Reader and Acrobat 9 restrict you from opening local files (Excel, Word, and so on) from within a PDF using Javascript (launchURL).  This action poses a security risk for the PDF file, and could allow dangerous files to be opened, and a script to be executed.

In previous versions of Acrobat or Reader (before 9.0), you can point the HTTP Submit button to a file:// URL on a network/local file system. The local file was “downloaded” using the browser’s plug-in. This behavior is not the intention of the HTTP Submit button. So, it’s been locked down in Acrobat and Reader 9 and later.

The HTTP submit button is used to send the form’s data to a server once the form has been filled. The resulting PDF can then be displayed to the user.

To reference or open local files from a PDF, run the PDF file in a privileged context (in the Javascript console or in a batch process). Or, certify the PDF file.  If you are running Acrobat or Reader in a browser context, you could put the local file on a web server and use the HTTP URL.

You can find more information to this security restriction under “app” and then the “methods” tab, and then under the launchURL method:

Extract from the JavaScript Documentation:

Note: Beginning with Acrobat 8.1, file and JavaScript URLs can be executed only when operating in a privileged context, such as during a batch event. File and JavaScript URLs begin with the scheme names javascript or file.

reference: (181917275)

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

LiveCycle Workspace ES: how to disable/hide the complete button


When working with forms in Workspace, you automatically get a complete button which often hides the submit buttons on the form.  It is a common requirement to hide this complete button, especially if you have pre-submit validation scripts on your form, or multiple submit buttons depending on the context.


You can disable this button in the following ways:

  1. You can customize the Workspace interface in Flex Builder
  2. You can modify the standard rendering services (for e.g. you can remove the route to the last two steps “Workspace enable” and “Reader extend” in the LC7UpgradeRender service)
  3. Use multipe in-direct submit buttons on the form, that contain a call to the click event of the hidden FS_SUBMIT button


The submit/complete button will still be available on the card/list view in the Workspace todo list.  This enables users to submit the form without even opening the form itself in Workspace.  In order to disable this button in the card view, you have two choices.  Firstly you can specify the ‘Form must be saved’ setting in ‘Form Data Mappings’ in Workbench.  The other option is to change the “client_routes_formViewOnly” to “true” in the workspace global settings, as described here:

under: Workspace Administration Help > Importing and Exporting Global Settings > Workspace ES global settings

Additional Information

To understand the situations when the complete button is displayed, and when the form submit buttons are displayed, please refer to the following description of the Inject Form Bridge service.


Adds javascript code to an Adobe PDF form or Adobe Acrobat form to enable it to function within LiveCycle Workspace ES. The PDF form must have been created using Adobe LiveCycle Designer ES, version 8.2, or Adobe Acrobat 7.0.5 or later.

If your process uses Adobe XML forms (XDP files), you can render the form to PDF and then use the Inject Form Bridge operation. To render to PDF, you use the renderPDFForm operation that the Forms service provides.

Workspace ES provides a Complete button that users click to submit their forms. However, forms can also include submit buttons. When the Inject Form Bridge operation is used on a form, Workspace ES either hides the submit button, or disables the Complete button.

Form design


The form includes no submit button.

Workspace ES disables the Complete button and users cannot submit the form.

The form includes one submit button.

Workspace ES hides the submit button and enables the Workspace ES Complete button.

The form includes a button (indirect submit) that points to a submit button (direct submit)

Indirect-submit buttons always take precedence over direct-submit buttons, even if multiple submit buttons exist. Workspace ES always shows the indirect submit buttons.

Workspace ES hides the submit button and enables the Workspace ES Complete button.

The form includes multiple indirect-submit buttons that point to one or more direct-submit buttons.

Workspace ES disables the Workspace ES Complete button. The user must click the appropriate button on the form to submit it.

The user can still save a draft version of the form or take the form offline

The form includes either an indirect- or direct-submit button in a repeating subform.

Workspace ES excludes these buttons for submitting the form in Workspace ES.

Note: When the submit button, that was added to the form design with the Process Fields,  is hidden, the button still provides the functionality for submitting the form.

Submit requests are handled by Workspace ES, which acts as an intermediary between the LiveCycle ES server and the form. Also, forms can be used both offline and online.

reference: (180833713)

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