Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114 Ticketing: update DOMPDF 0.5.1 to 0.6.0 | Event Espresso - Staging Server
Busy with designing some HTML-tickets for the ticketing plugin, I noticed that the version of DOMPDF used is quite outdated: 0.5.1, which is an early alpha of the 0.6.0 currently in bèta testing. This last version should support the use of fonts not available on the users computer, much like CSS3 allows webdesigners to do. Simply replacing the DOMPDF folder (0.5.1) by the newer version doesn’t work (not very suprisingly). I am not sure if you have already looked at updating this part of the EventEspresso plugin, but do you have any idea where the compatibility issue lies?
I was a little quick. Apparently, there was another folder included in the installation path causing it to break down with the Internal Server Error.
Having removed this extra folder still gives some errors (currently “PHP-font-lib must either be installed via composer or copied to lib/php-font-lib”), but does not cause DOMpdf to completely break down. I’ll try to fix it, and share the solution when I’ve found it!
Hopefully this can be included in a future version of EE.
Viewing 4 reply threads
The support post ‘Ticketing: update DOMPDF 0.5.1 to 0.6.0’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.