Document does not allow you to save any changes

Aspose.PDF Product Family
6

Hi Ken,

I’m sorry to inform you that it is not possible to enable extended features in a PDF file using Aspose.Pdf or Aspose.Pdf.Kit. However, our team is working on a related issue, that is to keep the extended features enabled if the form is filled and saved using Aspose.Pdf.Kit. This issue is under process and might take some time before it can be fully resolved. Are you interested in that sort of functionality?

Please share your thoughts with us.
Regards,

7

Hi

I am interested in this kind of functionality where the extended features are kept after a PDF form/file has been modified by aspose.pdf.kit. Is this possible now?

8

Hello John,

Thanks for considering Aspose.

I am afraid the requested feature is currently not available. However for the sake of implementation, we have logged this requirement as PDFKITNET-20907 in our issue tracking system. We will further look into the details of this requirement and will keep you updated on the status of correction.

Your patience and comprehension is greatly appreciated in this regard. We apologize for your inconvenience.

9

any news about this issue ?

10

Hello Dimitri,

Thanks for your patience.

Our development team is working hard to get this issue resolved and I am afraid the problem is not yet fixed. However, I have requested the development team to share the ETA regarding its resolution. Soon you will be updated with the status of correction. We apologize for your inconvenience.

11

Hi codewarrior,


I have stumbled upon this issue myself of the Reader Usage rights not being applied to PDF’s generated by aspose.pdf, therefore limiting the ability to save form data locally.

Has there been any update to this matter? If not is there a work-around in place until a formal solution has been developed?

Please let me know,

Cheers.
12

Hi Brian,

Thanks for using our products.

We are trying our level best to get this issue fixed but I am afraid its not yet completely resolved. As soon as we have some definite updates regarding its resolution, we would be more than happy to update you with the status of correction. Please be patient and spare us little time.

In the meantime, if you need to get the data filled inside PDF document, you may consider using the approach specified over following link for Posting AcroForm data to an external web page.

13

Hi Codewarrior,

I am trying to prefill data on a PDF form after extending user rights. I am unable to prefill using my current code which worked perfectly without extending user rights.

The issue that I am coming across is that the prefill does not work and the form does not get saved correctly. There is an issue with xml that is generated on form save. The xml structure consists of XElements that are not correct.

I think this issue may be related to this thread or am I missing something. Any update on this issue will be appreciated.

Thanks,
Smita

14

Hi Smita,

Sorry for replying you so late.

As stated in this forum thread, currently Aspose.Pdf for .NET does not support the feature to enable or keep the extended rights feature enabled once the PDF document is manipulated with Aspose.Pdf for .NET. The issue is already under investigation and soon you will be updated with the required information.

However concerning to your query I am trying to prefill data on a PDF form after extending user rights. I
am unable to prefill using my current code which worked perfectly
without extending user rights. can you please share the source PDF document before and after enabling the extended rights feature so that we can test the scenario at our end. Also please share the code snippet and other required documents. We are really sorry for this inconvenience.

15

Hi,

I have also encountered this problem. Is there a resolution to the problem?

The problem occurs after editing the PDF programatically and then saving the PDF.

When the PDF is opened in Adobe Reader, the user cannot edit any of the forms.

"Extended Features" needs to be enabled. Can this be done through the code?

Thanks,

Shane.

16

Hello Shane,


Thanks for using our products.

I am afraid the reported issues cannot be fixed, because according to Adobe Systems Inc., Adobe LiveCycle Reader Extensions enables PDF forms designers to extend the use of Adobe Reader to allow for any advanced functionalities that they put into their forms, such as the ability to save or submit a PDF form. The ability to extend Adobe Reader this way is only possible using Adobe’s products.


Unfortunately, it is not possible for any non-Adobe owned product, to either create PDFs with extended usage rights or modify the extended usage rights on existing PDFs that were created with Adobe LiveCycle or Acrobat 9.


In addition, if you modify a PDF – in any way, shape or form, with any none-Adobe product – that has had extended usage rights applied to it, it will invalidate the extended usage rights, resulting in an error message similar to the one listed below popping up when you open the document. This document contained certain rights to enable special features in Adobe Reader. The document had been changed since it was created and these rights are no longer valid. Please contact the author for the original version of this document.


We are really sorry for this inconvenience.

17

I understand that modifying the PDF will disable the "Reader Extension" priveledge in the PDF. .... but is there a way just to set default form field values without clearing the "Reader Extensions"?

Basically a user with Acrobat Pro X creates a "template" PDF and enables Reader Extensions so that Adobe Reader users can fill form fields and save PDF. Then I want to use Aspose.PDF to populate a few form fields and save the new PDF and then distribute that PDF to Adobe Reader users. Is there any way to keep the "Reader Extensions" enabled? It seems that it is cleared after setting form fields. I thought that form data was separate from the actual PDF. I dont want to modify the PDF ... just set some form fields.

Is that possible?

18

... The reason I think this might be possible is becase Adobe Reader can start filling in some form fields, hit Save, and then another user can open up that "modified" PDF in Adobe Reader and continue to edit form fields because the Reader Extension ability is still enabled. So I was hoping that simply editing form fields does not remove this capability.

thx!

19

Hi Jay,

I have shared the details of your requirement with the development team to further investigate this issue. Once they complete there investigation and share there results, I will update you via this forum thread.

Sorry for the inconvenience,

20

Hi Jay,<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" />

Please share the sample document(s) and you code sample with us. This will help the development team to investigate your issue.

Thank You & Best Regards,

21

Sure. Attached are two PDF documents.

unlocked.pdf - this file was enabled for Reader entensions. Notice you can fill in form fields and save.

locked_after_FillField.pdf - this file used ASPOSE Form.FillField to fill in a form field. Notice when you open it, it says Extended features no longer available and you cannot fill in form fields.

If you open unlocked.pdf and manually type in form fields, and then save the PDF to a new file name, notice that you CAN still edit form fields on the new file. Somehow Adobe Reader is "saving" the Reader Extensions characteristic even after modifying form fields similar to the ASPOSE Form.FillField.

22

Hi Jai,

Thank you for sharing the documents.

I have shared your documents with our development team with the details shared by you. Our development team will further look into your requirement and share there feedback. We will update you via this forum thread regarding any updates via this forum thread.

Thank You & Best Regards,

23

The issues you have found earlier (filed as PDFNEWNET-20907) have been fixed in Aspose.Pdf for .NET 7.2.0.

This message was posted using Notification2Forum from Downloads module by aspose.notifier.
(1)
24

Hello,

I am having this same issue using the trial version of Aspose PDF 7.6.0. Is it only a problem because I am using the trial version?

We are evaluating the trial version to see if it will meet our needs and so far it seems like it will if this issue is no longer a problem and works in the current version.

Specificaly what I would like to know is

  1. Is this just an issue in the current trial version?
  2. Will the paid for version of Aspose PDF version 7.6.0 solve this problem?

Thanks

25

Hi Rod,


Thanks for your inquiry. Please follow the thread for your query.

Sorry for the inconvenience.

Best Regards,