|
Tammy Hornek
|
September 10, 2014 at 1:44 pm
I used the url http://www.FunNightArt.com as the url while setting up my site. Once it was ready, we updated the url to my actual business website address of http://www.FunNiteArt.com. I made that change yesterday. Everything was working fine. I sent out a huge promo for the new site and was just polishing up my event listings. I tried to add a new event late this morning and received the following error: Warning: Invalid argument supplied for foreach() in /home4/bnpstv/public_html/clients/funnightart.com/wp-content/plugins/event-espresso-core-reg/caffeinated/admin/extend/messages/espresso_events_Messages_Hooks_Extend.class.php on line 97
I realized my Event Espresso key was registered to the old URL. So I paid for a key reset. After the reset, I continue to receive errors as follows:
I tried to update another event and received this error: Warning: Cannot modify header information – headers already sent by (output started at /home4/bnpstv/public_html/clients/funnightart.com/wp-content/plugins/event-espresso-core-reg/caffeinated/admin/extend/messages/espresso_events_Messages_Hooks_Extend.class.php:97) in /home4/bnpstv/public_html/clients/funnightart.com/wp-includes/pluggable.php on line 1173
My customers are also getting errors when trying to register. The first error I got was: This is the error my guests get when they try to register The following errors have occurred:
No Attendee object was found when attempting to save your registration information.
EED_Single_Page_Checkout – _save_all_registration_information – 1470
A recursive loop was detected and the registration process was halted.
EED_Single_Page_Checkout – go_to_next_step – 1800
I have been looking around trying to find where the plugin is referencing my old url and tried to buy another ticket. I received this error: Fatal error: Call to a member function get() on a non-object in /home4/bnpstv/public_html/clients/funnightart.com/wp-content/plugins/event-espresso-core-reg/core/libraries/messages/EE_message_type.lib.php on line 599
In short, this is devastating! I have customers messaging me, emailing and calling because they can’t register. I sent an email blast and promoted this new site on social media and I REALLY NEED HELP!
Please advise!
Thank you!
|
|
Garth
|
September 10, 2014 at 1:54 pm
Hi Tammy,
How are you today?
Changing the license key assignment has nothing to do with how the plugin functions. Can you test your development site and see if the error occurs there too?
Can you tell us if any custom development was done on your site because either there is bad code in what was changed or some sort of conflict with a plugin.
The Messages errors are related to EE4, but the EDD errors are from Easy Digital Downloads.
|
|
Tammy Hornek
|
September 10, 2014 at 2:05 pm
Hi Garth!
It’s a good day here in Virginia! Fall weather is back and I love it! How are you?
I only made two changes that were font color changes. Other than that, no changes to the development site.
Now I can’t even log in. Oh boy. Here’s the error I get when visiting my site (www.FunNiteArt.com): Warning: Invalid argument supplied for foreach() in /home4/bnpstv/public_html/clients/funnightart.com/wp-content/plugins/event-espresso-core-reg/core/EE_Config.core.php on line 190
Warning: Cannot modify header information – headers already sent by (output started at /home4/bnpstv/public_html/clients/funnightart.com/wp-content/plugins/event-espresso-core-reg/core/EE_Config.core.php:190) in /home4/bnpstv/public_html/clients/funnightart.com/wp-includes/pluggable.php on line 1173
|
|
Josh
|
September 10, 2014 at 2:45 pm
Hi Tammy,
The error messages indicate that it’s trying to use files installed on funnightart.com, but your site is now on funniteart.com.
I think the trouble here may be caused by how the site was changed over. Was the site moved over from one domain to the other? If so how? Was the database migrated using a plugin like WP Migrate DB?
|
|
Tammy Hornek
|
September 10, 2014 at 3:11 pm
Hey guys. So my IT guy (Jason) moved the site over. He did the updates himself. He just sent me this message:
I need you to research references to “_transient_ee_ssn_” in the wp_options table in WordPress to see if they can be deleted and reset. I keep changing the values in those tables and they keep getting changed back somehow.
|
|
Josh
|
September 10, 2014 at 3:22 pm
Hi Tammy,
Does Jason know how to properly move a WordPress site? If not, I can recommend he follow this guide:
http://codex.wordpress.org/Moving_WordPress
The transient records are used in the registration process. They should not be changed. They get automatically deleted after they expire, so deleting them should not be necessary. If they are get deleted or changed before they expire, that may be why your customers are not able to register.
|
|
Tammy Hornek
|
September 10, 2014 at 3:35 pm
Jason is quite an excellent programmer and does know how to migrate a site over.
The only reason he began looking at this reference is because the plugin stopped working.
Can you please offer some assistance here? This was WORKING THIS MORNING… there was NOTHING done to suddenly cause the system to stop working… so I require some serious assistance! While your focusing your energy on whether my guy knows how to update a site, I am losing money every minute it is not working!
Please offer a suggestion for a solution!
|
|
Josh
|
September 10, 2014 at 4:14 pm
Hi Tammy,
I’m sorry to hear about this. Does Jason know why it’s throwing error messages pointing to the old site? If the site was properly migrated over, why is it pointing to error messages on the old site? Is the DNS still propagating?
With the little I know on how this site was migrated my suggestion to follow the guide in the WordPress codex is the only suggestion I can come up with for now. If we can get more information about how this site was migrated we can follow up with more suggestions.
|
|
Tammy Hornek
|
September 10, 2014 at 4:39 pm
The website all works great. No problems with anything EXCEPT EE. When I try to update an event, I get the following error:
Warning: Invalid argument supplied for foreach() in /home4/bnpstv/public_html/clients/funnightart.com/wp-content/plugins/event-espresso-core-reg/caffeinated/admin/extend/messages/espresso_events_Messages_Hooks_Extend.class.php on line 97
Warning: Cannot modify header information – headers already sent by (output started at /home4/bnpstv/public_html/clients/funnightart.com/wp-content/plugins/event-espresso-core-reg/caffeinated/admin/extend/messages/espresso_events_Messages_Hooks_Extend.class.php:97) in /home4/bnpstv/public_html/clients/funnightart.com/wp-includes/pluggable.php on line 1173
|
|
Lorenzo Orlando Caum
|
September 10, 2014 at 5:45 pm
Hi there Tammy,
We aren’t questioning your developer’s skills. Rather, we are trying to provide recommendations based on the information that you have shared.
This is your current website URL:
funniteart.com
However, the PHP warnings that you shared are referring to your old URL:
funnightart.com
http://cl.ly/image/0i3G390C1J2L
That is why we are asking how the site was migrated. Can you pass this information on to your developer?
Also, your calendar page and event list page doesn’t appear to be working so again it would be helpful to know how the site was migrated.
—
Lorenzo
|
|
Tammy Hornek
|
September 10, 2014 at 10:44 pm
[This is Jason – the IT guy] Hey everyone! Thanks for working with Tammy (and myself) to help resolve this problem.
The site was originally installed as a dev copy on another variation of the domain she had and into a directory that I labeled “funnightart.com” on the server. Once Tammy was ready to go live, we redirected the domain and updated all the references to the old domain in the standard locations within the database using the same method I’ve used numerous times in the past to migrate sites over.
As Tammy stated, the site was working fine for awhile with no issues and then she started noticing problems as people were working to register and/or edit events in the EE system.
The references to the directory path using “funnightart.com” are accurate as that’s the name of the directory the files are in, but the actual domain name that’s been redirected is now http://www.funniteart.com.
I’ve gone through the MySQL database and looked for any references to “funnightart.com” and where it’s NOT been referencing the actual file directory path I’ve updated the reference to reflect the correct domain. If I changed the file directory path, then that would cause an issue I’m sure.
What I need help to understand from within the confines of the EE system is if the disconnect from the two domains would have gotten garbled up in any of the process in the migration in a way I’m not used to seeing, and haven’t seen, in any of the previous migrations I’ve done in this same way.
I was hoping a potential solution would be to initially deactivate the EE plugins and reactivating them hoping that would clear out and flush the older references and refresh it with the new domain settings, but that didn’t seem to help.
We need help to determine the fastest method to get Tammy’s site functional again with minimal loss in data.
In one of the comments Tammy posted earlier, I noticed that I would change domain references in the “wp_options” table with identifiers that started with “_transient_ee_ssn_”, save the changes but they would keep coming back with the old references. That lead me to believe there was another data point somewhere in the relationship that the EE plugin was using to rewrite/reset those values the next time they were loaded. Is/Could that be true? If so, where should I be looking for that value?
Interested in hearing ideas.
|
|
Tony
|
September 11, 2014 at 2:27 am
Hi Jason/Tammy,
Can you go to Event Espresso -> Messages.
Do you see a list of Message templates within the Default Templates tab, like this – http://take.ms/dnvGP
If not go to the Settings Tab (within Messages) de-activate the messages system and then re-activate – http://take.ms/YaBQu
Do you now see a list of Default Templates?
|
|
Tammy Hornek
|
September 11, 2014 at 11:41 am
[This is Jason] Those message templates didn’t show up so I did as you suggested. Tammy is testing now.
|
|
Tammy Hornek
|
September 11, 2014 at 11:46 am
[This is Jason] Tony, that appears to have worked I believe. Thank you SO MUCH for taking the time to look through the error messages and suggest some other items that we needed to review, confirm and check. I (and Tammy) really appreciate your effort. Wish we could have had your eyes on it earlier yesterday.
|
|
Tammy Hornek
|
September 11, 2014 at 11:48 am
THe message templates indeed are missing. I (Tammy) executed your fix and it worked.
NOW: After having lost 24 CRITICAL HOURS of BUSINESS when this setting was out of whack (and I never touched it)… I am seriously ticked off, guys! Why wasn’t a solution offered to me in the FIRST PLACE!???? This was a 5 minute fix that you guys took ALL DAY to offer to me… because your focus was more on trying to blame on Jason migrating our system over than on identifying the source of the error!
I do not appreciate the immediate jump to the assumption that this error wasn’t an EE issue. (Especially since the error CLEARLY stated EE all through it)
So, I get to pay my developer for the time he spent trying to help me resolve an issue with YOUR plug in.
#NotHappyGuys
Tammy
|
|
Tammy Hornek
|
September 11, 2014 at 11:50 am
/rant over. 🙂
Yes, Thank you very much, Tony!
At least I can get moving, now!
Have a blessed day.
|
|
Tony
|
September 11, 2014 at 12:12 pm
Hi Tammy,
Whilst I understand your frustration please understand, we come into these situations completely blind and can only base our advice on the information provided. Had I have been around yesterday, based on the information from before Jason’s reply. I would have suggested the same, a bad migration.
My check on the Messages system was again to help narrow down the issue further (even if it was incorrect it would have ruled that out) whilst other team members discussed this issue with our developers.
We see it all too often when a site is migrated incorrectly and it causes some very weird and wonderful issues that we need to pick apart, turn upside down and put back together again. Which is why we often ask so many questions, even now we still do not know which method Jason uses to migrate the site, just his ‘usual method’. This could have been manually using a search & replace script a migration plugin or even manually running a search and replace on the database (the wrong way)
A usual method all to often can be the wrong method and just because it has worked on other sites, does not mean it will work the same on a plugin as complex as Event Espresso (who’s core code rivals that of WP core).
I’m glad I could help and that you are now up and running again, please do let us know if you have any further issues.
|
|
Tammy Hornek
|
September 11, 2014 at 12:40 pm
Tony,
I am sure you do see all kinds of questions and confusion coming from different users. I do understand that. I think my frustration is that historically when going to IT support for almost any reason, there is always an assumption that the user is the problem. While I understand that the majority of the time that is the case. Perhaps in an event such as this one, it would have been helpful to inquire about the migration methods and offer a solution, as well.
It was clear that my site was causing me a loss of business… in that case, I was TRYING to ask for suggestions of actions I could take within the plug-in settings that MIGHT solve the problem.
I feel that none of you really decided to do that until Jason sent a long explanation of his processes.
Perhaps a good rule of thumb would be to ask questions and offer suggestions that may make an impact on the situation.
What about the error message made you identify it was a problem with the messages setting after Jasons message that wouldn’t have suggested the same issue before his message?
I would suggest nothing…except the willingness to look.
I do appreciate you guys. I hope you can see that I am offering you thoughtful feedback that perhaps should be taken into consideration. 🙂
Be well
Tammy
|
|
Tony
|
September 12, 2014 at 2:14 am
Thank you Tammy, we really do appreciate your feedback on this.
We are always striving to improve our customer service so your feedback is important to us.
|
