I can confirm this error. Seems $full_path variable is not set correctly for function output_to_buffer in plugin’s code. This bug breaks plugin functionality completely.
Reported this 2 weeks ago, no reply whatsoever.
Still running an old version on several sites.
Funny, was thinking to buy the plugin for pro support. I think I’ll be looking for another plugin instead.
Sorry guys long time ago. Had no idea this bug has not been resolved yet. Will reopen every related topic immediately and resolve it once and for all!
Apologies for the inconveniance.
Somebody got this error again after updating? I can’t replicate the error.
I’ve updated plugin from 2.4.11 to 2.4.12, but no errors. Are you using a custom template? I’ve tested by generating invoice in admin and by making an order onf front facing website. Both no problems.
Sorry, moved on long ago after going without an answer for so long. There are plenty of alternative plugins that do the same, so thats what I went with.
But out of the top of my head, I’m thinking it has something to do with having custom email themes. If that’s the case, it needs better debugging messages because it only shows an error in one of the core files. Some kind of validation on the theme should be pretty much mandatory.
Thanks for your quick reply!
Why custom email theme? That doesn’t make sense to me to be honest. A custom email theme has nothing to do with the path not found error of the (custom) template files.
Did you use a custom invoice template at the time?
-
This reply was modified 8 years, 5 months ago by
Bas Elbers.
-
This reply was modified 8 years, 5 months ago by Bas Elbers.
You’re the developer 😛 I don’t know either, but it would make sense why you could not reproduce it, but then again, the error is quite straightforward (missing/cant find file).
You should imagine that most of us already had a working version of the plugin installed, added custom themes and settings and then it broke after an update. Simply running the latest version on a clean wordpress might not be enough to reproduce it (especially if it DOES find the header in your case, maybe something breaks during updating or something.
Debugged/stepped-through code and did not catch something unusual. Updating plugin did not break anything. Will need more (technical) info..
If someone is getting this error please let me know below info to reproduce error:
– WordPress version,
– WooCommerce version,
– Plugin version,
– Which settings enabled/disabled,
– Using custom template?
Created a workitem, so will close this topic.
