|
Lori Horan
|
November 4, 2014 at 9:17 am
Getting the following in the price column of some registrations after upgrade from 3 to 4.
Fatal error: Call to a member function name() on a non-object in /html/wp-content/plugins/event-espresso-core-reg-2/admin_pages/registrations/EE_Registrations_List_Table.class.php on line 362
Also tickets are missing for some events which I think may be what is causing the error.
|
|
Tony
|
November 4, 2014 at 9:38 am
Hi Peter,
Which version of Event Espresso did you update from?
|
|
Lori Horan
|
November 4, 2014 at 9:45 am
It was the latest version of EE3
|
|
Tony
|
November 4, 2014 at 9:58 am
When you ran the migrations did you run through all the steps for each migration?
|
|
Lori Horan
|
November 4, 2014 at 10:02 am
Yes I did. As far as I know. Is there a way to run them again?
|
|
Tony
|
November 4, 2014 at 10:13 am
The best way is to restore to the database backup made before activating EE4, then when you re-activate EE4 the migrations will start again.
Do you have a backup from before you the migrations?
|
|
Lori Horan
|
November 4, 2014 at 10:25 am
Yes I do. I have done a lot of work setting the system up since the upgrade though. Is there any other way to fix the lost tickets? Through the DB?
|
|
Lorenzo Orlando Caum
|
November 4, 2014 at 10:42 am
Hi,
Generally, if you are seeing errors like this, then the database upgrade did not complete correctly. In this case, restoring from a backup would be the best option since there could be other issues that may have occurred.
Can you get some screenshots (Tinygrab.com or getcloudapp.com are free screenshot services) of the existing information and then try the upgrade again?
—
Lorenzo
|
|
Lori Horan
|
November 4, 2014 at 10:51 am
Here is what the events are saying
http://grab.by/BS5M
And this is the error
http://grab.by/BS62
|
|
Lorenzo Orlando Caum
|
November 4, 2014 at 11:22 am
Hi,
Your events are missing the ticket information. Do you have a backup available?
—
Lorenzo
|
|
Lori Horan
|
November 4, 2014 at 11:37 am
Yes. I have restored the backup and run through the upgrade with the same results. No errors during migration, but the same errors showing in registrations after.
|
|
Lori Horan
|
November 4, 2014 at 12:07 pm
I need to move ahead. Is there any way I can clean this up in the DB? I can create tickets for events where the tickets were not created, but when I view the registrant list, I get that error and it will not show anyone after that.
|
|
Josh
|
November 4, 2014 at 12:43 pm
Hi Peter,
Do you know which version of Event Espresso 3 you were migrating from? Along with that, had anything been customized with the Event Espresso 3?
|
|
Lori Horan
|
November 4, 2014 at 1:20 pm
Version 3.1.36.6.P
Just some template files. Nothing in the DB.
As it turns out, all but one of the problem events have passed. So I’m just trying to figure out how to update user registration to point to the new ticket I’ve created.
|
|
Lori Horan
|
November 4, 2014 at 1:34 pm
It appear that in the db, the registration in _esp_registration of the individuals that this error shows for are pointing to the wrong ticket id. I thin particular case I am looking at, the ticket id is the number of the event ID in the previous version.
|
|
Lori Horan
|
November 4, 2014 at 1:36 pm
Sorry, I was mistaken. The ticket id is set to 0
|
|
Lori Horan
|
November 4, 2014 at 1:40 pm
So I guess my question is, if I update the TKT_ID in _esp_registration, what else would I need to update so that I don’t break anything.
|
|
Tony
|
November 5, 2014 at 4:56 am
Hi Pete,
The problem is that for this to happen, ‘something’ has gone wrong with the migration from EE3 to EE4 and caused this error, so its not really possible for us to answer that question as we currently don’t know what that something is.
Would it be possible for you to send us the database backup from before you upgraded to EE4 so we can investigate the cause?
|
|
Lori Horan
|
November 5, 2014 at 6:07 am
Sure. Do you have an email address I can send a link to?
I have registrations taking place at the moment, so I have had to continue to use the system as is for now. All new events seem okay and the one that was broken that I still need, I was able to create a ticket for and update the registration table to point those registrations to the ticket.
I also updated the TKT_sold column for the new ticket as well as the DTT_sold in the esp_datetime table.
|
|
Tony
|
November 5, 2014 at 8:11 am
Please use support[at]eventespresso.com
We will investigate this and see if we can find the cause.
|
|
Lori Horan
|
November 5, 2014 at 8:42 am
Thanks, sent.
|
