|
Chris Stambaugh
|
March 3, 2014 at 3:56 pm
Hi,
Since upgrading to 4.1.8.reg I have noticed I’ve had no registrations.
Tried to do one myself today and after entering in the registrants name and clicking Proceed to Payments Options, an error pops up that says:
An error has occurred:
Your form data could not be applied to any valid registrations.
SNGPGCHC-DSNGPGCHC-PROATTINF-1271
Need help ASAP. They is costing me a lot of money! To the best of knowledge, nothing else has changed except upgrading from 4.1.7 to 4.1.8 last Friday.
Thanks,
Paul
|
|
Chris Stambaugh
|
March 3, 2014 at 4:19 pm
An example registration page that is not working is here…
https://www.bsop.ca/dslr-videography-shooting-video-creating-stories/dslr-videography-class-6-27-2014/
You guys desperately need telephone support options for your clients, IMHO.
|
|
Chris Stambaugh
|
March 3, 2014 at 4:32 pm
I’ll also mention that there is different behavior depending on the browser.
In Chrome, I get the error detailed above.
In IE 11, I don’t get the error, but when I try to pay via PayPal Pro (the graphic links for PayPal Pro and PayPal are broken FYI), the transaction never goes through and the spinning wheel stays there forever.
Help!
Paul
|
|
Brent Christensen
|
March 3, 2014 at 5:55 pm
When I look at your site, the footer scripts are loading INSIDE of the following link:
\< a rel="publisher" href="https://plus.google.com/{103113815230767562059/103113815230767562059}"
// scripts here
there is probably a missing closing tag for the link.
this **could** potentially be causing problems, and would explain why there is inconsistent behaviour between browsers.
|
|
Josh
|
March 3, 2014 at 6:04 pm
Hi Paul,
I checked on this and registered for an event with Chrome on your site and it didn’t throw any errors and the payment buttons look to be working as expected. I’m not sure why you’re seeing breakage after updating to 4.1.8. The one thing I saw that didn’t seem right was the Google+ link in an a tag that comes right before Event Espresso loads its scripts.
Was that something that was added recently?
|
|
Chris Stambaugh
|
March 3, 2014 at 8:38 pm
I solved this issue myself. And I apologize to Josh and Brent because I had this update written, but never clicked the submit button. Then I saw the replies and couldn’t figure out why you were trying to solve what I’d already to solve and came back and found the message unsent. Sorry. I don’t like to create unnecessary work for people.
The problem was that after upgrading to version 4.1.8.reg, and I don’t know what happened, but EE4 ended up in a folder called eventespresso.tmp. I don’t know if the upgrade didn’t complete correctly or what. But regardless, the plugin reactivated and seemingly ran fine.
To solve the issue, I renamed the folder to event-espresso-core-reg and it all seems to be working now.
I am wondering if there is a way that the developers could check the install/upgrade code to help indicate if things don’t complete correctly. And, would it be prudent to not assume what folder the plugin is in?
Thanks again.
Paul
|
|
Dean
|
March 4, 2014 at 1:14 am
Thanks for the feedback Paul, I’ll pass that on, and thanks for posting your solution. I’ll mark this thread as resolved.
|
|
Josh
|
March 4, 2014 at 1:35 pm
Hi Paul,
It doesn’t assume which folder the plugin is in. You can try it out yourself if you’d like by deactivating Event Espresso, renaming the Event Espresso folder, then re-activating. The only difference you’ll find is that image paths to things like payment buttons will also have to be changed to the new folder name, because those are user-configurable options stored in the database.
We do verify that the 1-click updates work after we publish a new version. In this case, because it ended up with a .tmp directory, it’s likely that something interrupted the update so it didn’t complete.
|
|
Chris Stambaugh
|
March 4, 2014 at 1:50 pm
Josh,
The only thing that changed to get the transactions to start working was renaming the folder.
That tells me that somewhere, some place, it must have been expecting things to be in a different folder.
Just sayin.
Paul
|
|
Josh
|
March 4, 2014 at 2:53 pm
That’s correct, there are file paths that are stored in the database that point to the location of assets (like your images that display for the payment option buttons, those can load from anywhere). So if a folder name gets changed, the file paths in those settings need to be updated.
|
