|
John Fineberg
|
January 23, 2015 at 9:47 am
Please, I really need immediate help on this one:
I just noticed that, as I go through the EE4 registration process — like I was a visitor to my website, wanting to sign up for a class — that I can no longer sign up for the class of my choice. For instance, I go this page:
http://www.cpr-twincities.com/community/combo
I choose a class and click on “Click Here to Register” (which was called “View Details” before I changed it in Quick Localisation). That brings me to this page:
http://www.cpr-twincities.com/events/adult-pediatric-adult-child-infant-first-aidcpraed-combo
I choose the number of tickets, then click on “Select Quantity, Then Click to Continue” (which was called “Register Now” before I changed it in Quick Localisation). That brings me to this page:
http://www.cpr-twincities.com/register?ee=_register
And that class is N O T the class on the previous two pages. I’ve tried doing this with every single upcoming class. And no matter which class I start with, it brings me to this same class!
I see nothing on the Edit Class List page to be causing this. I seriously need immediate help with this one, folks, as I’m out of business without online registrations.
|
|
John Fineberg
|
January 23, 2015 at 9:53 am
I just reverted back from “Select Quantity, Then Click to Continue” to “Register Now,” in case Quick Localisation was causing the misdirect. But it didn’t have any effect. Hopefully it’s something really simple, but I’m not seeing it.
|
|
Tony
|
January 23, 2015 at 10:12 am
Hi John,
This is due to WP Super Cache that you setup in this thread:
https://eventespresso.com/topic/slow-load-times-with-ee4/
You are using a different page slug from the default.
Add
/register/
To the WP Super Cache do not cache list.
Then purge (delete) the cache.
Currently your register page has cached with an event selected, which is why you see that event.
|
|
John Fineberg
|
January 23, 2015 at 11:27 am
YES YES YES YES YES! That did it, Tony!
I’d asked in a different discussion if this list was complete:
wp-.*\.php
index\.php
/events/
/registration-checkout/
/transactions/
/thank-you/
/registration-cancelled/
Apparently no one caught the missing “/register/” piece. But you did. Kudos, Tony! And thank you so much for jumping right on it!
So was it just my computer that couldn’t reach the correct registration page, or everyone’s?
Is there anything else that you recommend that I change from the default on WP Super Cache to speed up my site?
|
|
Tony
|
January 23, 2015 at 4:42 pm
Because Event Espresso allows you to customise the core page slug to anything you like we use this guide:
https://eventespresso.com/wiki/setup-nocache-exclusion-rules-event-espresso/
Which guides you through finding your own sites page slugs for the core pages.
Those listed above are the default core page slugs if no changes have been made.
So was it just my computer that couldn’t reach the correct registration page, or everyone’s?
It doesn’t matter on the computer used, cached pages are displayed to all non logged-in users, logged in users should not see cached pages.
Is there anything else that you recommend that I change from the default on WP Super Cache to speed up my site?
Caching is the easiest way to speed up your site however it can also cause issues with e-commerce and dynamic pages. Caching basically builds the page from the database, then stores the output for the next person. It is quicker to server a cached page than it is to pull all of the information in from the database and rebuild the page each time.
The only recommendation I can make is to cache static content when you can, dynamic content needs to be excluded (such as EE) however I recommend starting slowly and learning what all the different options do, you can very quickly cause some unexpected problems when caching.
Start by having a read of this guide:
http://www.wpbeginner.com/beginners-guide/how-to-install-and-setup-wp-super-cache-for-beginners/
See which parts of that guide work best for your site, making small changes and monitoring for improvements (or issues) is the best way to work with caching.
|
|
John Fineberg
|
January 26, 2015 at 9:58 am
Thanks again for your support, and for jumping in so quickly, when I really needed it. Looks like I’m good-to-go again. I’ll mark this as resolved.
|
