Hi @manujks,
Are you maybe using a custom PDF template? If so, try to switch temporarily to the default “Simple” template, and try again.
You’ll find the template switcher in WooCommerce > PDF Invoices > General > Choose a template.
Thx for quick reply Yordan.
I tried it with Simple template too, but it comes back with same page. that’s why i asked how to remove plugin and its data completely so that i can reinstall a fresh copy.
thanks in anticipation
hi Yordan, waiting for the solution.
thx
Thank you for your patience, @manujks!
Could you please write us at support@wpovernight.com so I can provide you high priority help there?
This is normally reserved for paid customers, but I’d like to help you faster, as you have been waiting for almost a week. Please include the URL to this topic in your email!
After finding the reason why it was failing, I will leave here a brief explanation of the case and/or the solution so that other users can benefit from it 😉
Thanks Yordan for your kind gesture.
sent a mail to support@wpovernight.com from my registered email mkser11@gmail.com.
Please look into the issue, thanks
For those following this topic or encountering the same issue, please note that it may be caused by invalid or improperly injected HTML markup.
In this specific case, I identified that <body> and <head> tags were being injected inside table elements. Because the document already contains these structural tags at the root level, inserting them again, especially in the middle of the existing HTML structure, results in invalid markup and triggers rendering errors. Additionally, there were unclosed tags and custom CSS rules added in the “Shop additional details” and “Footer” settings, within WooCommerce > PDF Invoices > General tab. These fields only support plain text and basic HTML, so inserting advanced markup or full structural elements will cause issues.
Please keep in mind that the PDF engine we use, Dompdf, is particularly strict when parsing HTML. Even minor markup errors, such as mismatched tags, duplicate structural elements, or unsupported CSS, can prevent the document from rendering entirely.
If you need to apply custom styling via CSS, you should use either:
For implementation details, please refer to the documentation section: Using custom styles.