Posted: May 24, 2014 at 4:12 pm
|
Hi, Recently, I started receiving PHP Warnings like this one: PHP Warning: mysql_real_escape_string(): A link to the server could not be established It seems to be related to the changes described in this post: http://make.wordpress.org/core/2014/04/07/mysql-in-wordpress-3-9/ What are the side-effects? When can we get a fix for it? P.S.: I have a renewed developer license, however I can only post to 4 forums (ticketing, translations, EE lite, pre-sales). |
Hi Cristi, Your user account should now be able to access the other forums. The latest version of EE3 does work with WordPress 3.9.1 but you’ll see those PHP warnings. We’ll get those warnings fixed in an upcoming release of EE3 (being tested internally). Cheers — |
|
|
It seems to be an issue. For example, for the seating chart, I have downloaded sample.xls and tried uploading it, but it doesn’t succeed. Can you try it too, please (on your servers)? P.S.: The forum access is fixed. |
Hello, Lets take a look at the new issue in your other post here: https://eventespresso.com/topic/seating-chart-add-on-not-working-on-wordpress-3-9/ — |
|
|
Hi, The other issue is resolved now, but the problem with uploading sample.xls still occurs. Php logs the following: PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 72 bytes) in /var/www/bilete/htdocs/stuff/plugins/espresso-seating/lib/class/oleread.inc on line 136 How much memory does it need, to succeed? Is this normal behavior? Thank you. |
|
I have read some articles which state a bug on 64 bit architecture. It was instantly solved once I have copied the latest reader php class content from https://php-excel-reader.googlecode.com/files/php-excel-reader-2.21.zip. |
|
Added a developer ticket to update the library file in the next version of the EE3 seating chart. |
The support post ‘Plugin incompatible with WordPress 3.9’ 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.