|
Brett Stallings
|
January 23, 2017 at 12:43 pm
I am using multi event registration on statscamp.org when you add an item to the cart, then remove it. Everything looks as though it removed. However if you go back to event OR add another event which loads the cart the contents stay there and can never be deleted. I can only empty the cart if I proceed to registration and hit the cancel registration button. Please advise.
|
|
Garth
|
January 23, 2017 at 12:59 pm
Hi Brett,
What version of Event Espresso and Multiple Event Registration are you using? I’m not able to produce this myself.
Do you have any caching enabled? It appears you’re on Godaddy hosting, so you might see this document for fixing GoDaddy caching for WordPress ecommerce.
|
|
Brett Stallings
|
January 23, 2017 at 3:49 pm
I am using EE4 4.9.26.p and MER 2.0.11.p with WP3 Total Cache version 0.9.5.1 and you are correct about GoDaddy. I will check that link, let me know if you have any other ideas. Thanks!
|
|
Brett Stallings
|
January 23, 2017 at 3:53 pm
We are not on GoDaddy managed just regular hosting and I do not see the object-cache.php file in the wp-content/ folder.
|
|
Brett Stallings
|
January 23, 2017 at 3:57 pm
For me if anything is in the event cart and I update the cart or delete I get the following message. “The specified item could not be found in the cart, therefore the quantity could not be adjusted. Please refresh the page and try again.”
|
|
Tony
|
January 23, 2017 at 4:27 pm
Hi Brett,
Can you link us to an event we can use to test this please?
|
|
Josh
|
January 23, 2017 at 4:30 pm
Hi Brett,
Since it appears that your site is running the W3 Total Cache plugin, you will need to make sure that that cart pages aren’t being cached. This includes object caching and database caching.
|
|
Brett Stallings
|
January 23, 2017 at 4:31 pm
https://www.statscamp.org/euro-camp/applied-latent-class-analysis
or any course from the home page list of them all are the same at statscamp.org
|
|
Brett Stallings
|
January 23, 2017 at 4:32 pm
Thanks guys! Is this the proper support article on the process for W3 total?
https://eventespresso.com/wiki/setup-nocache-exclusion-rules-event-espresso/
|
|
Josh
|
January 23, 2017 at 4:37 pm
Yes, here’s a direct link to the W3 total cache section of that article:
https://eventespresso.com/wiki/setup-nocache-exclusion-rules-event-espresso/#w3totalcache
|
|
Brett Stallings
|
January 23, 2017 at 4:38 pm
Awesome! Thanks Josh!
|
|
Brett Stallings
|
January 23, 2017 at 5:24 pm
I followed the instruction and still seem to have the same issue. I am viewing the page in a private firefox window, have flushed all caches after the W3 total cache exclusion. I am also using wordfence but I do not have the performance tab. Did not see any other plugins which are caching.
I also have Autoptimize All in one wp security, hearrbeat control, SEO ultimate, SSL insecure content fixer, any of those have any effect?
|
|
Brett Stallings
|
January 23, 2017 at 5:43 pm
I disabled the page cache option all together in W3 and then saved settings & purged caches. Still seem to have the same issue.
|
|
Josh
|
January 23, 2017 at 5:43 pm
HeartBeat Control could cause some issues because the later part of the checkout does use the HeartBeat API.
Also, any security plugin that disallows access to wp-admin/admin-ajax.php to logged out users will need to be set to allow ajax access on the front end of the website.
|
|
Brett Stallings
|
January 23, 2017 at 5:54 pm
I dsabled heartbeat and no change, I scanned through Wordfence and see the wp-admin/admin-ajax.php file listed a few times under the “Firewall” tab only. It is there several times under the “Whitelist URL” section. Not sure what I am looking for here. Any thoughts?
|
|
Josh
|
January 23, 2017 at 6:11 pm
I’m not familiar enough with WordFence to know. Here’s a few related threads from elsewhere:
https://forum.ait-pro.com/forums/topic/wordfence-admin-ajax-php-authentication-required/
https://wordpress.org/support/topic/exception-wp-adminadmin-ajaxphp/
https://www.wordfence.com/blog/2014/05/please-stop-password-protecting-your-wp-admin-folder-because-it-breaks-public-ajax-for-wordpress/
|
|
Brett Stallings
|
January 23, 2017 at 6:24 pm
I also have All in one WP security running. Any known issues there?
|
|
Brett Stallings
|
January 23, 2017 at 6:26 pm
In the security settings the wp-admin/ folder is set to 755…
|
|
Brett Stallings
|
January 23, 2017 at 6:30 pm
Fully disabled W3 Total cache plugin now. Still cant empty the event cart.
|
|
Brett Stallings
|
January 23, 2017 at 6:43 pm
I do not feel this is related to the admin-ajax.php as when you go to http://statscamp.org/wp-admin/admin-ajax.php it returns 0 and not 404
|
|
Brett Stallings
|
January 23, 2017 at 6:51 pm
Is it safe/needed to delete the autoptimize plugin cache?
|
|
Josh
|
January 23, 2017 at 7:00 pm
Hi Brett,
I have no knowledge of how the autoptimize plugin works, but it does seem like one of the non-EE plugins may be causing a conflict on your site. Can you try disabling the other plugins one-by-one, then test the cart again? The cart also has issues with adding more quantities of tickets too. For example, you click on the + button in the cart, you’ll get an error, then you refresh and the cart shows what it had before.
I think if you can systematically disable each of the plugins one-by-one you may just find the culprit.
|
|
Josh
|
January 23, 2017 at 7:25 pm
Update:
After spending some more time looking at the site with one of the developers, we can see that the cart works a-OK if the page is https. Things don’t work if the page is http. So if you have a plugin that’s forcing the front end pages to be http, you should stop using that.
Even better, you can install the Really Simple SSL plugin and it will set the whole site to use https. You can drop that insecure content fixer plugin too.
https://wordpress.org/plugins/really-simple-ssl/
|
|
Brett Stallings
|
January 23, 2017 at 7:32 pm
BOOM! Yes sir. I already had those plugins installed but on the registration-checkout page I did not have it set to force and I had one non https link which I fixed to resolve the https on that page. So simple but it was beyond me. I am very thankful for your time in helping me resolve this issue. (high five)
|
