Archive for February, 2012

CQ 5.4: how to export the user list as a CSV file

Problem

If you are using CQ 5.4 you will notice that the user report is displayed in the browser and you cannot save/export any of the information in this list.

You can view the user report from the “Tools” console in CQ5.  Select “Reports” in the left-hand pane, then double-click the user report in the right-hand pane to open it for viewing and/or configuration.

Solution

It is possible to export the user report as CSV content. You can do this in 3 steps.

  1. Overlay the /libs/cq/reporting/components/reportpage/ component to /apps/cq/reporting/components/reportpage/.
    For detailed instructions on how to overlay a component watch the following video:
    http://blogs.adobe.com/aaa/2011/11/walkthrough-of-overlaying-or-overriding-a-stock-cq-or-adep-wem-component.html
  2. In /apps/cq/reporting/components/reportpage/body.jsp replace the <body> section with the code in body_code.txt and save the changes.
  3. Navigate to the user report again and now you will see a link at the top to “Export” the content as CSV formatted text. This export function has different behaviour depending on the browser version.

Note: it is important to overlay the reportpage component in “apps”, rather than editing the file in “libs”, as libs is overwritten anytime you install a hotfix or a product update from Adobe, and therefore your changes are lost.  It is a best practice to overlay components to apps, and then you always have a backup of the original component in libs.

reference: (32200)

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

Acrobat/Reader 10.1.2: Grey blank page displayed when accessing a PDF from a secure site (HTTPS)

Issue

If you are accessing PDF files in the browser from a secure site (i.e. over a HTTPS connection), then you may be presented with a grey blank page, rather than the PDF file. Hitting “Refresh” in the browser will display the PDF file correctly.

Reason

This is a bug in the 10.1.2 version of Acrobat/Reader and has been resolved in the next quarterly release of Acrobat/Reader 10.1.3.  Update to 10.1.3 to resolve this issue, or use the workaround below if you cannot update to 10.1.3 immediately.

Solution

1. Open Acrobat or Reader.

2. Choose Help > Check for Updates.

Reader/Acrobat will install the update automatically.

If you prefer, you can download and install the update yourself. Click the appropriate link below and locate the 10.1.3 update.

Workaround

  1. Log in to your computer as an Administrator.
  2. Click the link to download the AdobeAcrobatReaderPatch10.1.2_cpsid_93026.zip  file.
  3. Unzip the file to extract the executable AdobeAcrobatReaderPatch10.1.2_cpsid_93026.exe.
  4. Close Adobe Acrobat/Adobe Reader if it is running.
  5. Do one of the following to run the AdobeAcrobatReaderPatch10.1.2_cpsid_93026.exe file:
    1. Double-click the AdobeAcrobatReaderPatch10.1.2_cpsid_93026.exe file.
    2. Run the AdobeAcrobatReaderPatch10.1.2_cpsid_93026.exe file in silent mode by specifying the -silent flag on the command line. Open the command prompt ‘As Administrator’ to avoid UAC prompt dialog.
      Example: <path to AdobeAcrobatReaderPatch10.1.2_cpsid_93026.exe> -silent
  6. Once the process is completed, you receive a prompt stating the result of the operation. You can choose to restart the system (if prompted) at that moment or later, but a restart will be needed to ensure that the fix has been applied correctly.
    Note: When run in silent mode, all dialog boxes are suppressed. No success message or error message appear.
  7. A log is created in the temp directory (%temp%) with the name AcroPatchApplication1012.log. (The changes sometimes only take effect after you restart your computer)

Additional Information

This issue is also being discussed in the following forums:

http://forums.adobe.com/thread/948331?tstart=0

http://forums.adobe.com/thread/948648?tstart=0

reference: (3087872)

http://helpx.adobe.com/acrobat/kb/troubleshoot-pdf-printing-acrobat-reader.html

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

Acrobat/Reader: Attach to Email button not working for PDFs referenced from long URLs

Issue

If you are using servlets or scripts to serve your PDF files in the browser, and you then want to use the standard “Attach to Email” button on the Acrobat/Reader toolbar (also available under the File menu) to forward the PDF to another user by email, you may notice that the PDF does not get attached to the email in some situations.

Reason

When you click on the Acrobat/Reader “Attach to Email” button on the toolbar it sends a request to your default email client to compose a new message.  It will also attempt to create the PDF attachment using the file name specified in the URL where the actual PDF is stored.

The URL may be too long to create a PDF file as attachment if it contains very long parameters as follows:

http://localhost:8080/Simple_Servlet/DMShowPDF?command=getdocuments&PDF=path/123_4567890abcdefghijklmnopqrstuvwxyz_0_0.pdf&sig=0123456789abcdefghijklmnopqrstuv&ts=0123456789012&category=new&stage=EDITING%3B%3B%3B1%3B%3B%3B&docid=S0123456789abcdefghijklmnopqrst&ext=.PDF

In this case the filename of the resulting PDF attachment would be:

123_4567890abcdefghijklmnopqrstuvwxyz_0_0.pdf&sig=0123456789abcdefghijklmnopqrstuv&ts=0123456789012&category=new&stage=EDITING%3B%3B%3B1%3B%3B%3B&docid=S0123456789abcdefghijklmnopqrst&ext=.PDF

This can exceed operating system limits, and therefore the attachment does not get created/added to the email message.

Workaround

Simply reducing the length of the URL, particularly the string which will be used for the PDF attachment file name, will allow the PDF attachment to be created.  Even just reducing it by a few characters is sufficient.

Solution

A cleaner solution however, would be to re-structure the URLs so they are shorter, and/or move the PDF parameter to the last parameter position as follows:

http://localhost:8080/Simple_Servlet/DMShowPDF?command=getdocuments&sig=0123456789abcdefghijklmnopqrstuv&ts=0123456789012&category=new&stage=EDITING%3B%3B%3B1%3B%3B%3B&docid=S0123456789abcdefghijklmnopqrst&ext=.PDF&PDF=path/123_4567890abcdefghijklmnopqrstuvwxyz_0_0.pdf

In this case, the attachment file name will be:

123_4567890abcdefghijklmnopqrstuvwxyz_0_0.pdf

reference: (182987737)

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

LiveCycle Output ES2: “Failure to automatically determine column ’5′ width”

Issue

If you are using LiveCycle Output to generate PDF documents using XDP files as input, you may encounter the following exception and no PDF will be returned:

0000012a XMLFormAgentW E com.adobe.livecycle.formsservice.logging.FormsLogger logMessage
ALC-OUT-002-017: mid,tid: 29435,23593162.1 sev: f text: Failure to automatically determine column '8' width.
0000012a FormServerExc E com.adobe.livecycle.formsservice.logging.FormsLogger logMessage
ALC-OUT-002-013: XMLFormFactory, PAexecute failure: "(com.adobe.document.xmlform.ReturnStatus@39133913)
Failure to automatically determine column '5' width."

If you load the same XDP file in Designer ES2 and goto PDF Preview, you may notice the same message as a warning in the log, but the PDF will be correctly rendered and displayed:

Failure to automatically determine column '5' width

Reason

This exception is occurring because of a problem in the Form design.  If you have a table in your form design with, let’s say 4 columns, you should check this table to ensure you don’t have a row with more than 4 fields defined.  This can occur especially when you have created the field objects first, and then converted a whole collection of objects into a table later on.  The extra (5th) field, can exist in a 4-column table if it has a width of “0″.

Here is an sample form to demonstrate the problem: support_test

Cell5 in Row1 is the extra field causing the problem in this case.

Solution

Simply delete the extra field as it is not visible anyway due to the “0″ width.

In future LiveCycle versions we will make changes in Output to return the PDF, and only show this message as a warning in the server log.  This will match the behaviour in Designer ES2 and Forms.

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