|
Christian Rogers
|
September 21, 2016 at 11:10 am
Hello,
I recently got word that we had customers who could not register for courses. I went on the site and I got an error that cookies needed to be enabled. I then went and updated EE and the site worked fine. Two days later I got an email saying more customers had contacted us and could not register. I then checked and received the same error myself. I deleted a plugin (wptouch) and it worked again. What could be causing this erratic behavior?
I am using Bluehost as my provider.
Thanks,
Chris
|
|
Seth Shoultes
|
September 22, 2016 at 9:31 am
Hello Christian,
Can you post a link to the event? Also, do you have a cache plugin installed? Such as WP Super Cache or W3 Total Cache.
|
|
Christian Rogers
|
September 22, 2016 at 11:46 am
Hi Seth,
Today the site seems to be working fine. You can see one of our event pages here: https://www.greatseminarsandbooks.com/acute-care-rehabilitation-online-registration/
I did not have a caching plugin but have since installed WP Super Cache.
Thanks
|
|
Josh
|
September 22, 2016 at 5:12 pm
Hi Christian,
If you navigate your browser directly to a registration-checkout page before any other page on your site, your browser won’t have had the cookie test, so you’ll get a message about not having cookies enabled. The message isn’t actually correct though, what actually happened was your browser just hadn’t had the cookie test yet. So after you load another page, the cookie check will have happened and you will not see that error.
|
|
Christian Rogers
|
September 23, 2016 at 11:30 am
Hi Josh,
Registration stopped working again. People will go to a page like this one:
http://www.greatseminarsandbooks.com/acute-care-rehabilitation-online-registration/
They click on Register for one of the courses and they are getting the cookies error. I do have a plugin installed like WP Super Cache. Please help. Thanks!
Chris
|
|
Josh
|
September 23, 2016 at 1:01 pm
If your caching plugin is like WP Super Cache, but not WP Super Cache, then it’s very likely the thing that’s causing the problems on your site. What I can suggest is you go into that plugin’s settings and disable caching.
After you’ve disabled caching, you can safely deactivate the plugin.
You will also need to remove the following code from your theme’s files, it’s breaking things:
https://www.evernote.com/shard/s4/sh/1ec9c273-df2a-4d97-be98-a99dfb671a86/74318b37776810ffc7ec1b3824a22ed9
https://www.evernote.com/shard/s4/sh/2d705383-4d3e-4a53-8d72-eeab72c6e14c/af03caf3d5894e01ffbddb19d5803c41
It may be simpler to switch to a functional WordPress theme. The one you have right now will probably need to be modified quite a bit to allow jQuery scripts to work correctly.
|
|
Christian Rogers
|
September 23, 2016 at 1:36 pm
Hey Josh,
I have switched the javascript so that jquery loads before the slider. We are getting near to having a new theme finished which will hopefully take care of these issues.
As for the plugin , I am using WP Super Cache as the plugin. Should I have caching on or off? I also tried to clear my cache and the registration worked again. I’m not sure if that had anything to do with it but my guess is it did.
Chris
|
|
Josh
|
September 23, 2016 at 1:53 pm
If you suspect that the Super Cache plugin is causing issues on your site, of course you should go to the Super Cache settings and disable caching.
I see another problem that’s related to your WP theme that needs to be fixed:
http://www.greatseminarsandbooks.com/events/
You’ll see a fatal error that says:
Fatal error: Call to undefined function twentytwelve_entry_meta() in /wp-content/themes/gsb/content.php on line 45
That means you need to open up the content.php template in your theme and remove the code that calls a twentytwelve_entry_meta() function.
|
|
Christian Rogers
|
September 23, 2016 at 2:02 pm
Josh,
The reason why I installed the Super Cache plugin was because of the very issue we are discussing. Earlier in the thread that was suggested. The site has been working fine for months and it wasn’t until a few weeks ago that I started receiving these cookies issues. I installed WP Super Cache a few days ago so I don’t believe that is what is causing the issue. Also, I can fix the issue you are mentioning but we don’t use the events page. Can you think of any other reason why customers would be getting this error?
Chris
|
|
Josh
|
September 23, 2016 at 2:19 pm
The reason why I installed the Super Cache plugin was because of the very issue we are discussing. Earlier in the thread that was suggested.
It was never suggested to install WP Super Cache. That would not fix your site.
The site has been working fine for months and it wasn’t until a few weeks ago that I started receiving these cookies issues.
What had been changed on the site a few weeks ago? New plugins, changes to the theme? Server upgrades?
I can fix the issue you are mentioning but we don’t use the events page.
I guess you could just leave that Fatal Error then if you’re not using the event page. I should ask though, how is the event page being disabled then? Was that disabled a few weeks ago? Maybe that’s what’s causing the problems.
Along with that, you still have two copies of the jQuery library. There should only be one.
<script type="text/javascript" src="http://ajax.googleapis.com/ajax/libs/jquery/1.5.2/jquery.min.js"></script>
<script type="text/javascript" src="http://code.jquery.com/jquery-latest.min.js"></script>
In this case you have a very old copy, and the latest. The one you really need is the version that’s bundled with WordPress.
|
|
Christian Rogers
|
September 23, 2016 at 7:37 pm
Hey Josh, Thanks for all the help. I dug around the internet a little more and found out that since I use Bluehost I needed to disable Varnish for the issue of caching.
Thanks!
Chris
|
|
Lorenzo Orlando Caum
|
September 24, 2016 at 8:24 am
Hi Chris,
Thanks for sharing a solution on how you resolved the issue by turning off Varnish caching.
Could you confirm that registration checkout is working as expected?
And are there any other questions that you would like feedback on?
—
Lorenzo
|
|
Christian Rogers
|
September 29, 2016 at 7:53 am
Hi Lorenzo,
Registration was working fine (no caching error issues).
I did have another option come up the past two days. I noticed our customers were getting double charged. I found out this morning (when I did some testing it was due to them not thinking their transaction went through. They are getting this error (see screenshot).
http://www.greatseminarsandbooks.com/images/error.png
I have already had some issues with transactional emails in the past. See this thread for details:
https://eventespresso.com/topic/transactional-emails/
I am using SendInBlue. What is strange is that I did receive the “Payment Received” and Registration emails for registering (both as the administrator and as a customer) when I made the test transaction. And it would seem emails are going through. But customers are seeing this error message regardless.
Thanks
|
|
Josh
|
September 29, 2016 at 8:29 am
Since the error message says the “from” address used was “Great Seminars & Books”, and that’s not a valid email address, you should change the From fields in your message templates to use the
[CO_EMAIL] short code instead of using the [CO_FORMATTED_EMAIL] short code.
|
|
Christian Rogers
|
September 29, 2016 at 8:41 am
Hey Josh,
What is strange is that the FROM field does not have “Great Seminars & Books” in it. It has an actual email address. Here is a screenshot:
http://www.greatseminarsandbooks.com/images/message.png
What is also strange is that as the registrant and as the administrator, I am receiving all of the emails, but the error is still saying that I’m not going to receive an email as the registrant. So its’ saying one thing and doing another.
I went ahead and switched the FROM field to the short code [CO_EMAIL] and I am still receive the same error. Any help is appreciated. Thanks
|
|
Josh
|
September 29, 2016 at 9:52 am
Your screenshot is from the editor for the Primary Registrant recipient context. If you switch the editor to the Registrant recipient, what’s in the From: field for that one?
|
|
Christian Rogers
|
September 29, 2016 at 10:17 am
Hey Josh,
I went to the Registrant recipient, removed the short code and put the actual email address in. It seems to be working now. I then conducted a test transaction. It seems to be working now. Thanks!
|
|
Josh
|
September 29, 2016 at 10:34 am
Did that field have the [CO_FORMATTED_EMAIL] short code in it?
|
|
Christian Rogers
|
September 29, 2016 at 1:07 pm
It did, so I changed it with the actual email address we use. Thanks!
|
