|
ambrose
|
April 23, 2013 at 11:43 pm
I just upgraded to v3.1.30 and my event registration no longer works. Apparently the attendee data is not getting passed in the form. I get the following error:
An error occured while attempting to update the attendee meta.
An error occured. No Attendee was received.
I’m a PHP developer — could you please point me to the part of the code where I can debug? Where should I check for the attendee id being passed in? Or is there a patch or a newer version I am missing?
|
|
Dean
|
April 24, 2013 at 6:05 am
Hello,
Please update to the latest version of Event Espresso – 3.1.31.1.
Advise us if the issue still occurs after the update.
|
|
ambrose
|
April 24, 2013 at 8:37 am
Correction: I am indeed using 3.1.31.1, just double checked. The problem is still happening. Furthermore, my client now gets a blank xls file when he tries to download attendee lists.
Please advise on the registration issue, though. This is the most pressing. Why is the attendee data missing?
|
|
Josh
|
April 24, 2013 at 10:25 am
Hi there,
I checked and it looks like you updated from 3.1.25.P. The update between 3.1.25.P to 3.1.31.P needs to run some data migration scripts. These may not have run on the update as they should have. Can you try deactivating Event Espresso, then reactivating?
|
|
ambrose
|
April 24, 2013 at 12:06 pm
Thanks for getting back to me. I have tried that already. Is there a way to to run the migration scripts manually?
|
|
ambrose
|
April 24, 2013 at 12:52 pm
Now I’ve tried deactivating, deleting plugin files, uploading new versions of the plugin files, and reactivating — still the same error. How is this happening?
|
|
steven polley
|
April 24, 2013 at 12:56 pm
I’m having the same issue. it will not send a confirmation and nothing happens..
|
|
Josh
|
April 24, 2013 at 1:28 pm
Hi there,
We will need to look at the database of the sites affected to investigate into why this is happening. If you can take a backup of the database with a plugin like wp-db-backup and email them to support @ eventespresso.com we can take a look.
|
|
ambrose
|
April 24, 2013 at 1:47 pm
Can you tell me which table/s to look at to change/reset settings that might affect this? I’d prefer to investigate it myself first.
|
|
Josh
|
April 24, 2013 at 2:17 pm
In wp_options there is an option_name with the value: espresso_data_migrations
You’ll want to check to see if that option_name exists and if so find the value. If you can find it, please let us know what the value is.
|
|
ambrose
|
April 24, 2013 at 4:11 pm
Thanks for the info. I will send you the value of that row.
|
|
ambrose
|
April 25, 2013 at 9:48 am
Hello. I emailed you the info yesterday. Would you like me to post it here instead. Look for an email from our web developer with the subject “attendee data issue from support forum”. Thank you.
|
|
ambrose
|
April 25, 2013 at 10:23 am
Looking through the code and the database, I found something that might be important: it appears that my events_attendee table is missing the column is_primary, which looks to be a column that was added in the new version. Wonder if that caused attendee-related queries to fail?
|
|
Josh
|
April 25, 2013 at 11:44 am
Hi there,
That would cause it to fail. You could check the PHP error logs at the time when you activated the new version of Event Espresso to find clues on what went wrong. The is_primary column gets added when the event_espresso_run_install function runs at line 414 of database_install.php.
|
|
Josh
|
April 25, 2013 at 1:43 pm
Hi Robyn,
One of the developers on the team spent some time with the database copy you sent and put in an their test server running the current version of Event Espresso with the 2012 theme. The registrations worked as expected when they tested it. They did notice that both the Espresso https and WordPress HTTPS plugins were set to be active, which isn’t recommended since their essentially the same plugin. The WordPress HTTPS plugin would be recommended since it’s actively maintained.
You may need to check to see if there are any custom functions that were set up when you were running 3.1.25.P that alter the registration process. These could be anywhere in /wp-content/uploads/espresso/, /wp-content/uploads/espresso/templates, a custom functionality plugin, or the active theme’s function file.
|
|
ambrose
|
April 25, 2013 at 2:48 pm
Thanks for the advice on the HTTPS plugins. I will fix that and see how it goes. I believe I did test it with all other plugins turned off, though, and still got the attendee error.
In 3.1.25, I made a few (mostly cosmetic) customizations to EE, but when I ran into trouble with 3.1.31, I did a clean install without any of my changes. So the EE files themselves are fresh. I don’t think anything I did would have changed any settings on the database end, but is there a table/field/value I should check?
Regarding the is_primary column, if the update does not add it to the table, what would you recommend to make it work?
|
|
Josh
|
April 25, 2013 at 2:52 pm
The is_primary column may have been there after you updated, but was removed when you reverted back to .25. You could do what our dev did and set up your database copy on a test server, then run the update to the latest version of Event Espresso and check to see if the is_primary column gets added.
|
|
ambrose
|
April 25, 2013 at 3:59 pm
Hi Josh,
I tried running on a dev server and it did seem to work. That’s good, but how do I get it working on the live server?
One error that I am still getting on the dev server and the live server, though: creating the PDF isn’t working. I get a 500 error on the following URL: http://legaldigestevents.com/?invoice_type=&download_invoice=true&attendee_id=3922&r_id=14-5179a5ec0547a
|
|
ambrose
|
April 25, 2013 at 4:02 pm
Correction: let me get back to you on that. My local server was still linking to pages on the live server so I need to re-test.
|
|
ambrose
|
April 25, 2013 at 6:43 pm
Ok, yes, it’s working locally (including PDF generation). What do you suggest for getting it to work on the live site? As you saw, we have thousands of records, so starting from scratch is going to be tricky.
|
|
Josh
|
April 26, 2013 at 7:39 am
Hi Robyn,
I suggest comparing what’s on the live site that’s preventing things from working. It may help to copy over plugins, theme files, and server settings from the live site to the local site to narrow down the issue.
|
|
ambrose
|
April 29, 2013 at 5:46 pm
Gee, I wish you’d mentioned that you released a new update THE SAME DAY of my original request. Installing the new version seemed to correct the problems; it would’ve been great if you’d mentioned it.
|
|
Josh
|
April 30, 2013 at 9:14 am
Hi Robyn,
I believe Dean did just so:
https://eventespresso.com/topic/attendee-data-not-received-from-registration/#post-43245
|
