@fssbob You’ll have to add /blog/* and /event/* to exclude urls from caching and click Save changes button.
Then try to purge the cache and check if the blog and event urls are being cached by checking the page source code, Does it at WP-Optimize line at the end of the source code?
Regards,
Harshad
Thread Starter
fssbob
(@fssbob)
Yes, I’ve done exactly that. However, the blog and event url’s continue to be cached.
There is an entry by WP-Optimize at the bottom of each page’s source code.
Thanks.
Bob
@fssbob Could you please share one of the blog or event urls so that we can check?
Thread Starter
fssbob
(@fssbob)
Hi Harshad,
See the email I sent to you at UpdraftPlus Internal Support. It will give you access to a test site where you can observe everything directly.
Thanks!
Bob
Moderator
Jan Dembowski
(@jdembowski)
Forum Moderator and Brute Squad
@fssbob Are you an WP Optimize customer?
It will give you access to a test site where you can observe everything directly.
If @bornforphp accepts that offer and does not come to here and explain that they can’t do that or risk losing forum access here, then they may be banned from the site.
It’s that serious and yes, even for a test site.
Had @bornforphp made that ask then this would be the reply.
While I know you have the best of intentions, it’s forum policy that you not ask users for admin or server access. Users on the forums aren’t your customers, they’re your open source collaborators, and requesting that kind of access can put you and them at high risk.
If they are paying customers (such as people who bought a premium service/product from you) then by all means, direct them to your official customer support system. But in all other cases, you need to help them here on the forums.
Thankfully are other ways to get information you need:
You get the idea.
We know volunteer support is not easy, and this guideline can feel needlessly restrictive. It’s actually there to protect you as much as end users. Should their site be hacked or have any issues after you accessed it, you could be held legally liable for damages. In addition, it’s difficult for end users to know the difference between helpful developers and people with malicious intentions. Because of that, we rely on plugin developers and long-standing volunteers (like you) to help us and uphold this particular guideline.
When you help users here and in public, you also help the next person with the same problem. They’ll be able to read the debugging and solution and educate themselves. That’s how we get the next generation of developers.
Thread Starter
fssbob
(@fssbob)
Sorry @jdembowski, I had no idea I was straying into prohibited territory. I’ll know going forward.
I’ve now figured out that, unlike me, the plugin was doing exactly what it was supposed to. I had thought that posts on the site in question would begin with /blog/–but of course that’s not the way the permalinks are set up. With respect to events, I’ve discovered that I need to include four exclusion entries, after which everything I want excluded is excluded:
/event/
/event/*
/events/
/events/*
I do have one question for Harshad (@bornforphp): With the premium version of the plugin, is it possible to exclude all posts from being cached, either using post-type or category (or something else)?
Thanks, and sorry again about stepping outside of the guidelines.
Bob
@fssbob Sorry excluding posts with post-type or category is not a feature yet.
However, I’ll discuss this with our development team in our next company meeting, if this feature can be implemented in next release.
Thread Starter
fssbob
(@fssbob)
@bornforphp Thanks. It’s really only an issue when I think of preloading a site with hundreds of posts. And the more I think about it, preloading really isn’t that important to me.
-
This reply was modified 4 years, 7 months ago by
fssbob.
