Hi @fungencio
It is happening for all Pdf documents.
Is this happening for all PDF documents you’ve created, or all PDF documents, including ones created outside your organization? I ask because it’s not happening with any testing we’re doing on PDFs we have.
Troubleshooting PDFs and how they are handled by the TCPDI parser is outside the scope of this free plugin’s volunteer support, since it has to do with things well outside our control. The PDF language is an open specification, meaning anyone can decide to write a PDF creation or display computer application, whether they are qualified or care much or not. This plugin and anything else having to do with PDF, including all PDF files, are part of that realm. It’s a vast realm where one writer might obey the spec and one reader might not, and vice versa. Then come the PDF creators (usually individuals) who might create a PDF in spec then use another application to add to the PDF, taking it outside spec, or vice versa (which is why I mentioned Apple Preview). The parser included in this plugin reads PDFs inside the spec and some outside the spec; however, it is open source so it might not read PDFs inside the newest spec or PDFs just a little outside spec. If you are very serious about your PDFs and don’t want the pain of ensuring that your PDF is in the spec read by a free plugin, then I recommend you upgrade to a plugin like PDF Stamper for WooCommerce, because it parses PDFs just the way they are rather than trying to interpret them, which is what ALL other plugins for PDF manipulation in the WP world do.
Again, we do not handle any PDF troubleshooting for any of our users, except occasionally for paid users to verify, “yes, it is your PDF. Edit your PDF, choose not to watermark it, or upgrade to a different/better PDF parser.”
Thanks for understanding, and for the detail in your post. Appreciated!
