Quantcast
Channel: Aspose.Pdf Product Family
Viewing all articles
Browse latest Browse all 3131

PdfFileSecurity is losing the "Allow Form Fields" setting resulting in a PDF that can't be filled in.

$
0
0
Aspose.Words: 13.5 Aspose.Pdf.Kit: 4.6 I user Aspose.Words to create a PDF with the setAllowFormFields set to true. The PDF has no security restrictions on it and it is saved for later. None of the form fields are filled in and nothing has opened or touched the PDF. Later I want to view the PDF but the view has some restrictions on it so we use PdfFileSecurity to set the additional restrictions on the file. Even if I set FillIn to true, the resulting PDF can no longer be filled in. It is the same result if FillIn was false or the setAllowFormFields had been set to false. If I comment out the step to set the security and just dish out the PDF as is, it works correctly and has all the fields filled in. I have been searching the API and the forums to find out if there is something I am missing, some additional setting or process to turn the form functionality back on and have had no luck. If someone could tell me how to turn the form fields back on or not get them turned off in the first place when adding security settings I would appreciate it. Thanks.

Viewing all articles
Browse latest Browse all 3131

Trending Articles