We're sorry Aspose doesn't work properply without JavaScript enabled.

Free Support Forum - aspose.com

Generated PDF - [Summarize Comments] disabled

With the generated PDF file, users cannot print their sticky notes that they added to the PDF file because the [Summarize Comments] button (in the print dialog, see attached image) is disabled.

We inherited this .NET application from someone who created this app but no longer works here. We were told there is a way to enable the [Summarize Comments] button but don’t know how…

Please help if you know how to resolve this issue, thanks!!!

Bruce

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

Thank you for considering Aspose.Pdf.

Well, I generated the PDF file using Aspose.Pdf for .NET with comments and opening the file in Adobe X for printing does not disable the “Summarized Comments” option. Please share your sample code and your generated PDF file which is causing the problem. We will check it and get back to you soon.

Sorry for the inconvenience,

It's here:

In the [if] block, the PDF file is secured (no modification allowed but no [Summarize Comments] button either)

In the [else] block, the PDF file is not secured at all - one can modify the PDF file, and the [Sumarize Comments] button is enabled.

We;re testing each of the properties in the [priviledge] to see which one disables the [Summarize Comments].

Thanks!!!

-------------------------------------------------------
if (LockGeneratedContractAmendment)
{
/******* SECURE PDF ***********/
//Set security on the document itself.
DocumentPrivilege privilege = DocumentPrivilege.ForbidAll;
privilege.AllowModifyContents = false;
privilege.AllowScreenReaders = true;
privilege.AllowPrint = true;
privilege.AllowCopy = true;
privilege.CopyAllowLevel = 1;
privilege.AllowModifyAnnotations = true;

MemoryStream secureStream = new MemoryStream();
PdfFileSecurity pSecurity = new PdfFileSecurity(outStream, secureStream);
pSecurity.SetPrivilege(privilege);

byte[] outBuf_Secure = secureStream.GetBuffer();

//response to user's web.
Response.Clear();
Response.ClearHeaders();
Response.ClearContent();
Response.Charset = "UTF-8";
Response.AddHeader("Content-Length", secureStream.Length.ToString());
Response.AddHeader("content-disposition", "inline;filename=" + "eContract.pdf");
Response.ContentType = "application/pdf";
Response.BinaryWrite(outBuf_Secure);
Response.End();
}
else
{
/***** NON SECURE PDF ***********/
byte[] outBuf_NonSecure = outStream.GetBuffer();

//response to user's web.
Response.Clear();
Response.ClearHeaders();
Response.ClearContent();
Response.Charset = "UTF-8";
Response.AddHeader("Content-Length", outStream.Length.ToString());
Response.AddHeader("content-disposition", "inline;filename=" + "eContract.pdf");
Response.ContentType = "application/pdf";
Response.BinaryWrite(outBuf_NonSecure);
Response.End();
}

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

Thank you for sharing the sample code.

I am able to replicate your mentioned issue at my end and I have logged the issue for investigation in our issue tracking system as PDFNEWNET-34480 for our development team to further look into it. Once I get a feedback from them, I will update you via this forum thread.

Sorry for the inconvenience,

Hi Bruce,


Thanks for your patience. You may try following code snippet to enable [Summarize Comments] option in the print dialog (when using Adobe X) while applying security.

DocumentPrivilege privilege = DocumentPrivilege.ForbidAll;<o:p></o:p>

privilege.AllowModifyContents = false;

privilege.AllowScreenReaders = true;

privilege.AllowPrint = true;

privilege.AllowCopy = true;

privilege.PrintAllowLevel = 2;

privilege.CopyAllowLevel = 2;

privilege.AllowModifyAnnotations = true;

PdfFileSecurity pSecurity = new PdfFileSecurity(myDir + "Note.pdf", myDir + "Note_Secure.pdf");

pSecurity.SetPrivilege(privilege);

Please feel free to contact us for any further assistance.


Best Regards,

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

Blog post for this release can be viewed over this link


This message was posted using Notification2Forum from Downloads module by Aspose Notifier.