|
Ashley Lewis
|
October 25, 2013 at 1:42 pm
WordPress 3.6.1
Event Espresso 3.1.22.2.P
Event Espresso – Calendar Version 2.0.B.
Event Espresso – Social Media Version 1.1
Not a recent installation, not recently upgraded.
http://mediumsandiego.org/registration/
I am working on this for a client. They get this error on the registration page:
Warning: Missing argument 2 for wpdb::prepare(), called in /home/content/77/9266877/html/wp-content/plugins/event-espresso.3.1.22.2.P/includes/process-registration/add_attendees_to_db.php on line 104 and defined in /home/content/77/9266877/html/wp-includes/wp-db.php on line 992
From reading the forums, it sounds like they need to upgrade EE.
Do I update just the one plugin or all?
What do I need to watch out for?
How can I tell if the previous developer did any changes to core files?
Thanks,
Eric
|
|
Josh
|
October 25, 2013 at 2:20 pm
Hi Eric,
You’ll need to update all of the Event Espresso plugins in order to be compatible with WP 3.6 and up.
We outline what to watch out for when you update in this guide:
https://eventespresso.com/wiki/updating-event-espresso/
In a nutshell you will want to backup the database and check for any old files in /wp-content/uploads/espresso/templates or /wp-content/uploads/espresso/gateways. Any files in those two locations will need to be removed or updated when you update as they override their corresponding files in the core Event Espresso plugin.
One way to check for any core files modifications is when you’re FTP’ed in you can check to see if any files were modified at a later date. Most FTP clients will display the date the file was last modified. Also, before you update you can backup the old plugin files locally so in case there were modifications made you won’t lose any of the files.
|
|
Ashley Lewis
|
October 25, 2013 at 3:22 pm
i”ll take a look at that link. Thanks.
Do you think using Duplicator plugin would be good enough for backing up? I don’t have phpMyAdmin access currently.
|
|
Ashley Lewis
|
October 25, 2013 at 3:57 pm
Actually, I decided to use the UpdraftPlus plugin to backup, since I had problems with a Duplicator backup last time I tried it.
|
|
Josh
|
October 25, 2013 at 6:04 pm
I’m not familiar with either of those, but I like to use WPDBBackup or even WPMigrateDB. The nice thing about WPMigrateDB is it has an option to do a find and replace on URLs and file paths so you can move everything over to a local site and run the updates on the local site first.
This is a link to a good go-to backup guide:
http://www.prelovac.com/vladimir/how-to-do-a-full-wordpress-backup
|
|
Ashley Lewis
|
October 25, 2013 at 6:20 pm
That gives me an idea: I could make a local copy and test the update there, so there’s less risk of downtime potential for the live site (which people are actively registering at).
I use DesktopServer Pro to create local .dev WP sites, and it used the Duplicator plugin to copy the site. http://serverpress.com/products/desktopserver/
I’m not sure I understand your comment about “..find and replace on URLs and file paths so you can move everything over…”?
|
|
Josh
|
October 26, 2013 at 6:57 am
The file paths and URLs stored in the live site’s database need to be changed to point to the new site’s file paths and URLs when the data is migrated so images, settings, and options will work in the new location. See also:
http://interconnectit.com/products/search-and-replace-for-wordpress-databases/
The video in this post shows how to change the file paths and URLs when migrating the WP database:
http://wp.tutsplus.com/tutorials/plugins/migrating-your-wordpress-database-wp-migrate-db-production-to-development/
|
