Posted: November 16, 2012 at 5:38 am
|
Hi, I also cant get the attendees to update with the information in thr data base. |
Hi Nina, The error message you are seeing indicates it can’t find the event_espresso_add_attendees_to_db function, which is declared in /event-espresso/includes/admin-reports/add_attendees_to_db.php. I would suggest downloading a fresh copy of Event Espresso from your account page and uploading that one to the server. Please note that you’ll need to deactivate and remove the version that is installed right now. |
|
|
I removed and deleted all espresso folders prior and reinstalled 28.4 and the espresso members. |
|
I do not see that file (add_attendees_to_db.php) in the admin-reports folder. Can you please check the zip file? |
That was a mistake on my part, it’s in includes/process-registration/ |
|
|
I reverted back to an older version and it is working now except I’m still having the issue of needing to update the database of attendees. |
Hi Nina, Event Espresso 3.1.28.4 fixes a critical bug that would overwrite some attendee data when editing attendee data in the admin. Please see Seth’s post here: There we’re not any changes in includes/process-registration/ between 3.1.28.3 and .4, so one place to look for a difference in that function would be in the custom functions files. The file that has the 3.1.28.4 hotfix is in includes/admin-reports/edit_attendee_record.php |
|
|
In the last instal of todays version that I did this morning, I deleted all files that were espresso related including the custom functions. I then installed the 28.4 and the new members. It still gave me the fatal error and the attendee data is not updated. In php myadmin the attendee data is correct, but that fails to be reflected in the espresso attendees. |
Hi Nina, I’ve seen the attendee data get out of sync when there were files from an older version of Event Espresso in /wp-content/uploads/espresso/templates, and new registrations were added while these old templates were overriding the core templates. So the way forward would be to remove/update any templates in /wp-content/uploads/espresso/templates while updating. A simple way to accomplish this would be to rename that directory. |
|
|
I’m also having this problem and haven’t downgraded to any other version. I’m also having a separate problem of the the CSS templates not “sticking” for some reason. |
|
@Foundry is your error message the same one? What version did you update from and to? Please can you post your separate CSS issue a separate thread? It helps us keep things a little more organised. |
|
Yea, I ended up having to downgrade to 3.1.22.2.P because it was incredibly important for us to have EE running. That was the version from my last backup, which actually reminded me to do a full backup of wp-content. The CSS issue went away, so it’s something to do with that latest update and/or other plugins not playing nice. I didn’t have time to check after I reinstalled WP, the theme and the plugin multiple times. Perhaps something’s off in the SVN? |
Which method did you use to update the plugin from 3.1.22.P? Did you deactivate the plugin before uploading the new version? Also, are there any template files currently in /wp-content/uploads/espresso/templates? |
|
|
I updated from 3.1.22.P and subsequent updates via FTP and then the automatic built-in updater when that became available. This time, I deactivated the latest 28.4 build and uploaded the 22.P via FTP. |
If you don’t have any custom templates then Josh’s original post would apply to you as well. Something is off in the files on the server. Your best bet would be to delete the Event Espresso directory in your /wp-content/plugins/ folder and re-upload a fresh copy. It may also work to just deactivate the plugin and reactivate. However, due to differences between the older versions of Event Espresso and newer versions of Event Espresso and changes made to the database structure, we can’t guarantee that everything will work as intended if you roll back to a previous version of Event Espresso. This is why we (and WordPress) recommend making a database backup before doing any updates to your site. |
|
The support post ‘fatal error (3)’ 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.