|
ipallen
|
July 23, 2017 at 11:05 am
Original Thread: https://eventespresso.com/topic/fatal-error-function-name-must-be-a-string-in/
I also have this exact issue when editing an event.
For your information: changes made to the event text in the large textarea will persist but ticketing and date changes, and everything else will not. Even though the event text will change the error will always occur.
A white screen of death to …/wp-admin/post.php appears after pressing the update button on the Edit Event page. The line 1029 error message only showed for me with the following additions to my wp-config.php file:
error_reporting(E_ALL); ini_set(‘display_errors’, 1);
define( ‘WP_DEBUG’, true);
Environment:
WordPress 4.8
Event Espresso 4.9.44.p
Event Espresso – Ticketing (EE 4+) 1.0.5.p
Apache hosted server
Please help as I do have some tight deadlines for this event, as I’m sure most of your customers have for theirs. Please contact me if I can help you resolve this issue in any way.
Regards,
Ian.
|
|
Josh
|
July 24, 2017 at 7:35 am
Hi Ian,
You’ll need to upgrade your server from PHP 5.3.29 (or contact your host and ask them to do the upgrade). The error you’re seeing is a result from using an unsupported version of PHP.
The supported versions of PHP are listed here:
http://php.net/supported-versions.php
|
|
ipallen
|
July 26, 2017 at 11:45 am
Thanks Josh,
I will try a later version.
Which version of PHP do you recommend for Event Espresso and the ticketing add-on?
Ian.
|
|
ipallen
|
July 26, 2017 at 12:25 pm
I have updated the site to PHP 5.6.30 and it appears to have fixed the issue.
Thanks for that. Should I update to PHP 7?
Ian.
|
|
Tony
|
July 26, 2017 at 12:34 pm
Hi there,
5.6.xx now only receives security fixes and will soon be EOL in Jan 2019, personally, I would look into switching over to PHP 7.
Note that a jump to PHP 7 may highlight issues with plugins (or the theme) doing things wrong or using what are now considered deprecated functions and so on.
I’d recommend creating a development site (a copy of the surrent site on a subdomain for example), switching to PHP 7 there and testing that all of your plugins are compatible before doing so on the live site.
|
|
ipallen
|
July 27, 2017 at 7:06 am
Thanks for the advice.
Ian.
|
|
Tony
|
July 27, 2017 at 7:21 am
You’re most welcome.
Any further problems please od let us know.
|
|
ipallen
|
July 27, 2017 at 9:22 am
As you offered…
I’m using PayPal express checkout and on the thank-you page the “loading transaction and payment information…” box is never being populated.
I read about the issue about the WP heartbeat and I don’t believe that is the problem. I loaded the Heartbeat Control plugin and setting that to “allow only on Post Edit pages” actually removes the spinning cog activity indicator.
So leaving the heartbeat on its default settings and watching the page using Firefox developer tools shows that admin-ajax.php is being repeatedly requested with the wrong URL causing a stream of 404s.
This is probably caused by the strange way I have the wordpress site hosted in a subfolder of public_html (lets call the subfolder ‘x’).
So the URL being requested is:
http://www.example.com/x/wp-admin/admin-ajax.php
when it needs to be (I believe):
http://www.example.com/wp-admin/admin-ajax.php
Is there a way to control this issue or do I need a custom change to the code.
Thanks,
Ian.
|
|
Josh
|
July 27, 2017 at 10:24 am
Hi Ian,
It’s OK to install WordPress in a subdirectory, but you need to follow the steps from this guide closely and not skip any steps:
https://codex.wordpress.org/Giving_WordPress_Its_Own_Directory
|
|
ipallen
|
July 28, 2017 at 2:06 am
Hello again,
I’m still trying to work out the problem given the instructions that you kindly gave me yesterday.
This morning I noticed that there was an update for Espresso 4.9.45.p so I selected update now from the plugin list itself. After a wait of a minute or so there was an error displayed which I have not captured unfortunately (never again!) and the site went to maintenance mode for a good few minutes and then returned. The Espresso plugin is no longer listed but the Ticketing add-on is still listed. event-espresso-core-reg files are still present in the plugins directory. Should I restore a backup of the database and site or is there a simpler way to reload the espresso plugin? Any ideas why the plugin would disappear after a minor update?
Thanks,
Ian.
|
|
Josh
|
July 28, 2017 at 6:35 am
Hi Ian,
When the plugin isn’t listed on the WP Plugins page that’s an indication there are missing files within the plugin folder. The database is quite likely OK.
Here’s how to fix:
1) FTP in and remove the event-espresso-core-reg files that are still present in the plugins directory
2) Download a fresh copy of Event Espresso 4 from your account page
3) Go to your site’s WP Plugins page, click Add New, and upload the zip file you just downloaded
4) Activate
|
|
ipallen
|
July 28, 2017 at 10:28 am
Thanks, Josh.
It is working again now.
I was not able to use the “Add New” feature as the plugin just would not install after the “Unpacking the package…” message. I tried many times without success.
What worked for me in the end was to unzip the plugin myself, FTP the files into the plugins folder and then activate the plugin from my WordPress site.
It would be good to have some sort of understanding about the plugin install and updating issues that I have – I guess that they are not Event Espresso related but rather more general than that. I have web hosting with a large provider that should be good enough but the response times can be a little slow.
Thanks for your help (again!),
Ian.
|
|
Josh
|
July 28, 2017 at 10:52 am
Usually when plugins don’t update or install via the WP dashboard it’s a filesystem permissions issue where WP isn’t allowed work with the server’s filesystem. Sometimes adding the WordPress Upgrade Constants to your site’s wp-config.php file will help. There’s more information about those in the WordPress codex:
https://codex.wordpress.org/Editing_wp-config.php#WordPress_Upgrade_Constants
|
