Hi ,
I am using livecycle designer ES and livecycle reader extensions es to create some PDF files. I want to use the new feature action builder, so I downloaded the designer ES3. After creating some new files, I tried to use livecycle reader extensions es (old version) to convert the file to add the saving function to adobe reader. It could not convert the file successfully and stuck at downloading the file page as the attached screen. Does that mean I have to upgrade livecycle reader extensions es to es3? Thanks in advance.
Regards,
Craig
Solved! Go to Solution.
Views
Replies
Total Likes
There were problems like this that were caused by a flashplayer security patch. See https://groups.google.com/forum/?fromgroups=#!topic/livecycle/ZRj27vcLXOI
My memory is a bit hazy on this, as it was three years ago.
There was a LiveCycle blog on this November 11, 2008
http://blogs.adobe.com/livecycle/2008/11/livecycle_and_flash_player_10.html
Flash Player 10 broke the Reader Extensions sample application included with LiveCycle ES 8.0.1, and 8.2.1. When you use it, it will essentially hang. The workaround is to revert back to Flash Player 9 on those machines you use as LiveCycle clients.
This problem has been fixed in LC 8.2.1 SP3 as well as in ES2.
The key is to either upgrade your server or downgrade to an earlier (9) version of the flash player. (copying from the google group)
As you said, this issue is due to the changes in security in flash
player 10. The Reader Extensions webUI leverages flex. For LiveCycle
8.2.1, the file dialog automatically pops up after conversion is
complete. However, in flash player 10, there were changes to how file
reference are is handled. Since it is possible to pop up a file
dialog based on user action), and automatically poping up that file
dialog based on the old code base will no longer work. This is a
known issue in LC ES 8.2.1, and downgrading to flash player 9 works.
However, in fix pack 2 of LiveCycle ES Update 1. (8.2.1.2), this bug
on flash player 10 has been resolved with an explicit button to
download the file.
Views
Replies
Total Likes
Is there any error in the log? I don't see a reason this shouldn't work.
Views
Replies
Total Likes
There were problems like this that were caused by a flashplayer security patch. See https://groups.google.com/forum/?fromgroups=#!topic/livecycle/ZRj27vcLXOI
My memory is a bit hazy on this, as it was three years ago.
There was a LiveCycle blog on this November 11, 2008
http://blogs.adobe.com/livecycle/2008/11/livecycle_and_flash_player_10.html
Flash Player 10 broke the Reader Extensions sample application included with LiveCycle ES 8.0.1, and 8.2.1. When you use it, it will essentially hang. The workaround is to revert back to Flash Player 9 on those machines you use as LiveCycle clients.
This problem has been fixed in LC 8.2.1 SP3 as well as in ES2.
The key is to either upgrade your server or downgrade to an earlier (9) version of the flash player. (copying from the google group)
As you said, this issue is due to the changes in security in flash
player 10. The Reader Extensions webUI leverages flex. For LiveCycle
8.2.1, the file dialog automatically pops up after conversion is
complete. However, in flash player 10, there were changes to how file
reference are is handled. Since it is possible to pop up a file
dialog based on user action), and automatically poping up that file
dialog based on the old code base will no longer work. This is a
known issue in LC ES 8.2.1, and downgrading to flash player 9 works.
However, in fix pack 2 of LiveCycle ES Update 1. (8.2.1.2), this bug
on flash player 10 has been resolved with an explicit button to
download the file.
Views
Replies
Total Likes
Thanks, Chuck. After I downgrade the flash palyer, it works fine.
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies