Plugin Contributor
Ewout
(@pomegranate)
Hi. I’m sorry to hear it’s not working for you.
A blank page could mean a number of things – this could indicate a plugin conflict, we’re not aware of any breaking bugs with the latest version.
To find out more about the error, you could try to enable debug output in WordPress, this should give you a PHP error which will let us help you find the cause of the issue and resolve it. More about enabling debug loggin in WordPress here: Example wp-config.php for Debugging.
Alternatively, if you have access to your PHP error logs, that may also help you find why the site is crashing. Your host should be able to assist with this too.
Let us know what you find and we’ll do our best to help!
Ewout
Here is what i got, looks like a memory issue!
Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 262144 bytes) in /home/rvpartsexpress/public_html/wp-includes/load.php on line 815
Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 262144 bytes) in /home/rvpartsexpress/public_html/wp-includes/load.php on line 677
Plugin Contributor
Ewout
(@pomegranate)
Indeed. Quite serious too – it appears you’re running out at 256M during quite standard WP processes (when the PDF Invoice plugin is hardly doing anything).
I recommend installing a plugin that measures/shows your memory usage to track down which plugin is using so much memory (if WordPress lets you, of course). Do you have a lot of plugins on this site? Is this on shared hosting?
My memory usage is just fine when I go to cpanel. I am only running 8 common plugins. I can activate any plugin I want without any issue. It is only after I activate your plugin that all the memory is being used.
Everything was working fine until I moved this website from managed wordpress to cPanel. After that I couldn’t activate your plugin without the website going down.
Plugin Contributor
Ewout
(@pomegranate)
Hi! I’m not sure cPanel is a good indication of memory usage on your wordpress site.
The ‘heaviest’ part of this plugin is the PDF generator, dompdf. This is autoloaded, which means that the classes for this are not loaded until they are actually used to create the PDF. Then still the memory footprint is very low and certainly shouldn’t exceed 256M. Only when you create a very big PDF document (multiple pages with tables spanning pages, lots of large images), you may run out of memory. Even then, 256M should take you very far.
I’m a bit stunned by this and do not have an explanation for why simply activating the plugin would give you this memory error. I haven’t had any other reports like this either, which makes it hard to pin down what’s happening here…
