When a PDF created in LiveCycle is opened in a browser window, we receive the "Please wait... If this message is not eventually" etc etc

[brentschaus]

I use LiveCycle ES3 Version 10

All QA testing was done using Adobe Acrobat XI, or Adobe Reader 11.

When we try to view a preview of the PDF, when sent as an email attachment, we receive the error message shown below.

We've put the document onto our server. When anyone clicks on the link:

• Internet Explorer: it works! Believe it or not.
  
  
• Chrome: error message (see below)
  
  
• Firefox: requires changing the default reader from Adobe Reader to Firefox's reader; otherwise, we see the error below.

I fear that it has something to do with how I've saved the document. As I've said, though, the document works when opened from a folder on one of our local drives, or from an email attachment.

Any insight?

Thanks in advance!

[Jono Moore]

As with Firefox you also have to turn off Chrome's internal PDF viewer. 

http://howto.cnet.com/8301-11310_39-20074274-285/how-to-disable-chromes-pdf-viewer/

Unfortunately the built-in PDF viewers don't fully support the PDF spec. Same with the Mac OS PDF viewer.

--
You received this message because you are subscribed to the Google Groups "Adobe LiveCycle Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to livecycle+...@googlegroups.com.
To post to this group, send email to live...@googlegroups.com.
Visit this group at http://groups.google.com/group/livecycle.
For more options, visit https://groups.google.com/groups/opt_out.

[brentschaus]

Thanks, Jono... I just realized I got it backwards, above, with the Firefox example.

Sadly, we don't want our merchants to have to adjust their browsers settings in order to download a single PDF form.

One potential solution I came across said that forcing the PDFs to download solves the problem. This might be the solution for us. Do you foresee any potential issues?

(thanks, again!)

I ran into this issue on my site as well. I addressed it by forcing the PDF to download instead of open in the browser. You can force download with a few lines in an .htaccess file on an Apache webserver. Instead of making all of my PDF files download, I created a separate folder on the server just for the PDF files that don't display in the browser properly, and I put the .htaccess file in that folder (so it doesn't affect the rest of the site).

 

Simply create a plain text file and name it .htaccess (no other extension), copy the following code into it, and upload it as ASCII to your server in the same folder with the PDF files that are giving you a headache.

 

<FilesMatch "\.(pdf)$">
  ForceType application/octet-stream
  Header set Content-Disposition attachment
</FilesMatch>

 

If you are on a Windows server, you'll have to use another method.

[Jono Moore]

I don't know of any problems off-hand but I don't do web stuff. 

[swapnil patil]

Hi ,

I have managed to resolve this by disabling chrome pdf viewer .

but now we are making mobile app to search and view document. 

In android os default browser, it downloads document. but in ios browser and some browser on android platform it opens doc in url.

there i am still facing problem to open editable pdf documents. we are using xfa form.

We are using adobe livecycle ES2

Please help if any one having solution for same.

Regards,

Swapnil P.

--
Thanks and Regards,
Swapnil P Patil.
: People matter, results count

[Murali Raghavan]

You will need es4 html 5 forms for it to work on all platforms and browsers. Xfa forms need acrobat plugin to work.

[swapnil patil]

I want to use ES2 only.

for me it will be acceptable that from mobile, user only can view the pdf not edit.

so i am looking some thing to make pdf viewable on mobile devices.

[Murali Raghavan]

I am not sure if xfa forms work in mobile adobe reader. If the user does not need to edit it u can convert it to a flattened pdf and send it out.

[Dave Venance]

So the mobile Readers on Android and iOS as well as the chrome PDF viewers do not support the newer dynamic XFA forms. If you need to do data capture on those platforms, I would recommend using LiveCycle Forms Pro ES4. It can take your XFA template design and render it as an HTML5 form that will work everywhere.

If you only need to present the PDF on those platforms, you can use LiveCycle Output to render a flat non-interactive PDF that should be viewable with any PDF viewer.

Dave Venance
4Point

[tarekahf]

I am very happy I found this thread. I started facing this issue when I wanted to access the XFA Forms I developed on Android devices some time ago. Then, I realized that this is not as easy as I though.

Just to make sure I understand what is required.

In order to make the forms fully functional on Android then we must use Adobe LiveCylce ES4 Forms Server (Desinger not enouhg) right?

What about Digital Signatures?

Will Digital Signature Fields be functional if the XFA Form is rendered using HTML 5?

Tarek.

[brentschaus]

Thanks for your replies, everyone. I'm glad that some of you find this thread useful.

I'll be taking ES4 for a test drive... it sounds as if it may be the answer we need.

In the meantime, we're looking at forcing a PDF download...  our Bus Dev folk like the idea, as it saves time reminding clients to download the file(s)..

We prepare these forms on behalf of merchants and, in turn, it's their customers that download the forms. We dislike the idea of asking customers two steps down the line to adjust their browser settings.

Brent

[Murali Raghavan]

Some Adobe links for ES4: Digital Signatures are not supported, they have scribble pad for it.

Basics:

Introduction to Mobile Forms : http://helpx.adobe.com/livecycle/help/mobile-forms/introduction.html

 

Mobile Forms Architecture : http://helpx.adobe.com/livecycle/help/mobile-forms/mobile-forms-architecture.html

 

Feature differentiation between Mobile Forms and PDF Forms : http://helpx.adobe.com/livecycle/help/mobile-forms/feature-differentiation-mobile-forms-pdf.html

 

Rendering & Submitting:

Creating a Custom Profile : http://helpx.adobe.com/livecycle/help/mobile-forms/creating-profile.html

 

Rendering Form Template : http://helpx.adobe.com/livecycle/help/mobile-forms/rendering-form-template.html

 

Designing Forms:

Designing form templates : http://helpx.adobe.com/livecycle/help/mobile-forms/designing-form-template.html

 

Scripting support : http://helpx.adobe.com/livecycle/help/mobile-forms/scripting-support.html

 

[tarekahf]

Thank you Murali.

What will happen if you render an XFA Form under LiveCycle ES4 using HTML5, and the form has Digital Signature? How the Signature Field will be rendered?

What is scribble pad? Is this a replacement for Digital Signature?

Tarek.

[Murali Raghavan]

It appears as a text field and data entered will not be retained. U will need alternate subforms for html5 and pdf

[Murali Raghavan]

Scribble pad captures ur signature drawn via touch / mouse as a base 64 image. Can also captures latitude longitudinal details.  This Control Doesnt work with older versions of acrobat before 11 if converted to pdf.

[tarekahf]

Thank you again Murali,

Appreciate it if you could point me to any reference to Scribble Pad for more information, and with a demo if possible.

Tarek.

[Darren]

Hi Tarek,

Info on Scribble signatures is here: http://helpx.adobe.com/livecycle/help/mobile-forms/scribble-support.html. Scribbles work in any HTML5 browser also - not just mobile devices. You can just draw with the mouse.

• Scribble signatures work in both HTML5 and PDF. HTML5 you can scribble with the mouse or your finger. PDF prompts you to upload an image file (jpg, gif, png, tif)
  
• Digital signatures only works in PDF land. HTML5 seems to just create a blank box that you cant interact with which makes sense as its not a PDF.

You need to determine what requirements you need to fulfil and switch the visibility of the subforms based on host.appType. It will return "HTML 5" if you are running inside mobile forms. You can use this method to switch calls to web services as HTML5 will leverage jQuery from the profile page to achieve what you need. 

Be aware that there is currently an issue with scribble signatures and Mobile Workspace on iPad we discovered. These are not rendered under ES4 SP1 currently for some reason. The should work fine rendering stand-alone in Safari etc

Cheers,

Darren

[Belinda Franklin]

I have had the same issue until today. I realized that I was saving the form as as an Adobe Dynamic XML Form in Live Cycle.  When I save the form as an Adobe Static PDF form I am able to view the PDF in Chrome. Hopefully this works for others.

[Bastian Landherr]

Hey,

chrome added an own pdf viewer, which can't handle dynamic PDFs. Change the std PDF Viewer (as URL: chrome://plugins/) to Adobe Reader / Acrobat.

IE is the only Browser in your list without an internal view ;)

Greetings