Something weird is happening, and I’m not sure if it’s a conflict with the caching I have in place, but…
https://preachnet.com/freeindeed/ is a woocommerce store used in conjunction with Groups, Groups for WooCommerce and Subscriptions.
https://preachnet.com/freeindeed/sermons is set in the dashboard as the home page of the site. It is also the woocommerce shop page.
Logged out users see an orange button at the top of this page to Sign In. They also see a Log In button in the top menu.
Logged in users see different content at the top of this page (depending on their Group), and they see a different top menu, with no Log In button, but instead links to Home, My Downloads, My Account, Log Out and Contact Us.
This works fine on all pages except the home page.
So once a user is logged in, https://preachnet.com/freeindeed/ shows like no one is logged in, but https://preachnet.com/freeindeed/sermons (which is what shows at https://preachnet.com/freeindeed/ since it’s set as the site’s home page) shows normally for logged in users, as all other pages do.
So somehow, when the url is https://preachnet.com/freeindeed, the site acts like the logged in user is not logged in.
I don’t recall this always happening, so I’m wondering if something I added recently is breaking Groups for Woocommerce’s functionality.
I have recently been working on the speed alot. I moved the site to SiteGround for hosting. I’m using their SuperCacher plugin, along with W3 Total Cache, and I have added code in functions.php to Remove Query String from Static Resources and to Defer parsign of javascript. So I’m not sure if the browser or server is caching the url https://preachnet.com/freeindeed with content as a logged out user or what, but something very strange is happening.
I can work around it by changing all link to / (home page) throughout the site to /sermons , but that doesn’t tell me what the problem is.
Can you please help.
Once signed, in other content
Thanks again. You can close this ticket.
Antonio……you are a genius….or at least you know a lot more about caching than I do.
There was a setting in the Database Cache section of W3TC that says:
Don’t cache queries for logged in users
Enabling this option is recommended to maintain default WordPress behavior.
I disabled this and that solved the problem.
Interesting though because in the general settings, Database Caching is deactivated because the host handles that, and leaving it on within W3TC can cause problems. But even though it was off, the caching of queries for logged in users was still on, and that was causing the problem.
All seems to be fixed now. Thanks so much!!! 5 STARS!!!
Perfect, I’m glad it worked.
Kind Regards
Antonio,
Upon further testing I have confirmed that it is indeed the W3 Total Cache plugin that is causing this issue. When I disabled it, the problem went away.
I will contact the dev of that plugin, but have you heard of any conflict like this between a caching plugin and Groups content locking function?
Maybe you can provide some direction that I can provide the plugin’s dev to have this matter resolved.
I’m sure I’m not the only person that is using Group on a site with W3 Total Cache.
Thanks,
Rob
Hi,
you could try to disable cache for logged in users, and/or disable the database cache of W3 cache.
Kind Regards,
Antonio B.
Hi Robert,
really I don’t know what is the problem, but it seems related to cache. You can try to disable your cache plugins and test if the problem persist or not.
Maybe the cache plugins are working different with the homepage, maybe they are any option about this.
Kind Regards,
Antonio B.