|
Alexander Vesnenok
|
November 14, 2014 at 4:26 am
Hello,
I once was advised that form version 4.4.5 EE supports non-latin characters in PDF but it looks like it is not. Is that true or I have to change something in my settings?
https://dl.dropboxusercontent.com/u/27611752/%D0%AD%D0%BA%D1%81%D0%BA%D1%83%D1%80%D1%81%D0%B8%D0%B8_%D0%BF%D0%BE_%D0%93%D0%BE%D0%BB%D0%BB%D0%B0%D0%BD%D0%B4%D0%B8%D0%B8_Invoice_%232-4-1-aa36a4-0_for_Alexander_Vesnenok.pdf
Thank you.
|
|
Lorenzo Orlando Caum
|
November 14, 2014 at 9:14 am
Hi Alexander, this is in 4.5. Could you join our pre-release channel here:
https://eventespresso.com/wiki/pre-release-channel-guide/
Then this link will work for you:
https://eventespresso.com/users/alexvesna/#pre-release-downloads
1) Backup your WordPress
2) Deactivate and remove Event Espresso 4.4.x via WordPress Plugins
3) Upload, install, and activate Event Espresso 4.5 prerelease
4) Allow it to migrate
5) Go to Event Espresso –> Messages –> Invoice. If you do not see it, then it may be on the second page due to pagination. Click on Screen Options and raise the pagination to a higher value than 10 and save.
6) Click on the Invoice message type. This will take you to the messages editor. Along the right side, you’ll see a widget for template settings. Set that to Simple UTF8 and save.
—
Lorenzo
|
|
Alexander Vesnenok
|
November 14, 2014 at 10:06 am
Thank you, Lorenzo.
I’ve installed EE4.5. It works fine for me but I am not able to check PDF file encoding. Every time I try to download it the server gives me 500 error.
What would you recommend to do in this case?
Thank you.
|
|
Josh
|
November 17, 2014 at 5:38 pm
Hi Alexander,
Does your server allow fopen? Can you check your server’s error logs for the time the 500 error was thrown?
|
|
Alexander Vesnenok
|
November 25, 2014 at 11:02 am
I haven’t got this information yet from my provider yet but I hope I can get it soon.
Thank you for your help.
|
|
Lorenzo Orlando Caum
|
November 25, 2014 at 12:21 pm
Hi Alexander, you should be able to send an email from the WP dashboard to open a support ticket.
Let us know what you find out.
—
Lorenzo
|
|
Alexander Vesnenok
|
December 3, 2014 at 2:00 pm
Hi Lorenzo,
Here is what i got from my provider:
This looks to be occurring as a result of this fatal error in event espresso:
[03-Dec-2014 20:35:03 UTC] PHP Fatal error: Uncaught exception ‘DOMPDF_Exception’ with message ‘No block-level parent found. Not good.’ in /htdocs/wp-content/plugins/event-espresso-core-pr/core/third_party_libs/dompdf/include/inline_positioner.cls.php:38
You may need to contact the developers, especially since the version of this plugin your site is running on is a beta version.
If you give them the Fatal error above, they will be able to help you see if a newer releases patches this.
I hope this will help to solve my issue.
Thank you.
|
|
Josh
|
December 3, 2014 at 3:19 pm
Hi Alexander,
It’s likely that your WordPress theme is causing the Fatal Error. Before you click the Download PDF button, if you view the source of the html invoice, you’ll probably see a link to a stylesheet that’s from your WordPress theme.
Can you let me know what the name of the theme is and where it can be purchased from?
|
|
Alexander Vesnenok
|
December 3, 2014 at 3:37 pm
Hi Josh,
http://themeforest.net/item/tour-package-wordpress-traveltour-theme/5360508
This is the theme I use.
thank you
|
|
Josh
|
December 4, 2014 at 2:50 pm
Hi Alexander,
If you temporarily switch to a theme like twentyfourteen, does the fatal error go away? If so, the fix for this will be in the final release of Event Espresso 4.5.
Since you’re using the new UTF-8 invoice capability in EE4.5 beta, you’ll want to be sure to keep an eye out for the UTF-8 invoice template pack that will be released as a separate download when 4.5 is ready. We’ll have more information when 4.5 is released.
|
|
Alexander Vesnenok
|
December 4, 2014 at 3:38 pm
I just updated to the last version. I can download PDF now.
|
|
Alexander Vesnenok
|
December 4, 2014 at 3:40 pm
but encoding is broken, unfortunately (
|
|
Josh
|
December 4, 2014 at 3:57 pm
Hi Alexander,
This is because the UTF-8 template pack was moved into an add-on. We’ll have the add-on released soon.
|
