|
jouterleys
|
February 6, 2018 at 8:09 pm
Hello,
I have similar error as this post: downloading receipt results in HTTP 500 error.
Checked my log and I have a fatal error that reads:
PHP Fatal error: Cannot declare class HTML5_Data, because the name is already in use in /var/www/vhosts/~/httpdocs/wp-content/plugins/event-espresso-core-reg/core/third_party_libs/dompdf/lib/html5lib/Data.php on line 5
Also have this:
PHP Deprecated: Non-static method EED_WP_Users_SPCO::_can_attach_user_to_attendee() should not be called statically in /var/www/vhosts/~/httpdocs/wp-content/plugins/eea-wp-user-integration/EED_WP_Users_SPCO.module.php on line 698
PHP version 7.0.27
ee_version 4.9.56.p
WP Version 4.9.4
Any help would be greatly appreciated.
J
|
|
Tony
|
February 7, 2018 at 3:26 am
Hi there,
That error usually means another plugin is loading DOMPDF when it shouldn’t not be, so when EE loads it on its own route for generating the PDF it’s already loaded and throws the above.
Are you using the ‘WooCommerce PDF Invoices’ plugin?
We have another user report the same error with the above plugin a while back: https://eventespresso.com/topic/dompdf-error-when-downloading-invoice/
The depreciated notice is not related but will be fixed in the next version of the EE4 Users integration add-on.
|
|
jouterleys
|
February 7, 2018 at 6:00 am
Thanks Tony,
I am not using Woo. I suspect it is a timetable plugin that I am using. If I were to find the plug-in that is calling DOMPDF, should I then be going back to that developer and ask them to fix this error?
Thanks,
J
|
|
Tony
|
February 7, 2018 at 8:24 am
The route that is used to generate the EE PDF’s is unique to EE and should be the only place we load DOMPDF. If another plugin is loading it on that route (ie everywhere) it should be fixed in that plugin to only load the assets it needs at the times it needs them.
If you disable whichever plugin is causing it and try to download the PDF it should work, then re-enable the plugin and try downloading a PDF again. If it once again stops working you’ve found the plugin causing it.
|
|
jouterleys
|
February 7, 2018 at 8:43 am
That’s the plan!
Thanks Tony.
J
|
|
Tony
|
February 7, 2018 at 8:52 am
You’re most welcome.
Please do let me know how you get on with this.
|
