|
Kent Rayhill
|
December 17, 2012 at 7:33 pm
I just changed the price of an event and now I get this error all over my EE admin page and on the second page of the registration process. Using WP 3.5. PLEASE HELP RIGHT AWAY!
Warning: Missing argument 2 for wpdb::prepare(), called in /home/rayhill/public_html/wp-content/plugins/event-espresso.3.1.23.P/includes/process-registration/add_attendees_to_db.php on line 104 and defined in /home/rayhill/public_html/wp-includes/wp-db.php on line 990
|
|
Dean
|
December 18, 2012 at 1:13 am
Hello Kent,
You are using WordPress 3.5 but with Event Espresso 3.1.23.P. Event Espresso is now on 3.1.29.1.P and your version will not work with WP 3.5.
WP 3.5 changed a lot of things, and these have affected a lot of different plugins and themes
Have a look at this blog post https://eventespresso.com/2012/12/what-you-need-to-know-about-upgrading-wordpress-and-event-espresso/, specifically the section titled
If you’re upgrading to WordPress 3.5, you need to upgrade Event Espresso
Some extra info
https://eventespresso.com/wiki/how-to-back-up-your-site/
https://eventespresso.com/wiki/updating-event-espresso/
|
|
Kent Rayhill
|
December 18, 2012 at 1:19 am
Thank you for the info. Will I be in any danger of losing any customization when I upgrade EE?
|
|
Dean
|
December 18, 2012 at 2:18 am
Hi,
Potentially, If you have customised files and placed them in the wp-content/uploads/espresso folder, then the customisations wont be over written but they wont work with the latest version. You will need to get a copy of the latest templates and port your customisations over to those templates and put the new ones in the uploads/espresso directory again.
If you changed the template files in the default templates or gateways directory, you can copy them across but as above will need to port the changes over.
If you changed core files (ones which are not in the template or gateways folders) then you need to make sure you back them up as they will definitely be overwritten on update. No core files should be amended really.
Database wise you will be fine, but as you are updating by several versions you especially need to make sure you backup the database in case something goes wrong.
|
|
Kent Rayhill
|
December 18, 2012 at 2:55 am
Out of curiosity, why doesn’t your plugin upgrade with one click like all other WP plugins? At the very least, it would be helpful to receive some sort of notification that an upgrade is available/needed.
|
|
Dean
|
December 18, 2012 at 3:00 am
Hi Kent,
Yes we realised the same thing, a few versions after yours we implemented the one click upgrade system, so long as there is a valid licence key in the settings.
So once you have updated to the latest and greatest, you will get the one click updates from there on.
|
|
Kent Rayhill
|
December 18, 2012 at 11:46 am
Wait, I have to pay to make my plugin work again? Is that correct?
|
|
Kent Rayhill
|
December 18, 2012 at 3:58 pm
Really need to get this fixed ASAP. Do I actually have to renew to get this thing working again?
|
|
Josh
|
December 18, 2012 at 4:27 pm
Hi Kent,
That is one option, we don’t provide WordPress compatibility support for older versions of Event Espresso in that, if core WordPress functions change (as they did in WordPress 3.5) then Event Espresso needs to be updated to be compatible with the new version of WordPress. Event Espresso 3.1.29 has been updated and tested to work with WordPress 3.5.
Your other options include reverting to the older version of WordPress (you’ll need to restore the database from a backup in that case).
Or you may be able to continue using Event Espresso with the newer version of WordPress and set error display to off. The warning messages that you are seeing are likely because error_display is set to ON in the PHP.ini file on your server. Typically, error_display is set to ON for a server that is set up for development, with the understanding that when the site goes live, error_display will be disabled.
It’s not recommended or secure to display errors on a live site. Otherwise server info will display on public facing pages if any errors get thrown. So it’s recommend to log errors on a live site, not display them.
It may be possible to override the error display setting in php.ini by adding this line to the wp-config.php file above any require_once or include commands:
@ini_set(‘display_errors’,’Off’);
http://codex.wordpress.org/Editing_wp-config.php#Configure_Error_Log
|
