However, this causes a major problem. I was going to purchase the full version so I can schedule popups. But, what good would that do if I have to clear the cache for every scheduled popup?

There needs to be a way to exclude Popup Builder from being cached. If that function is included, I could not find it.

Otherwise, I can’t use this extension.

Thanks for the trial.

Or first process the header (for example, if a user has accessed via google then opens a specific screen, otherwise, it does not)
Thanks

I was struggling with occasional loss of reported traffic due to my pages being cached by WP Super Cache (which is not active for logged in users) but not having SlimStatParams & the slimstat JS-file in it. I tried changing different settings in Slimstat, but the problem still occurred. I was not able to pinpoint the exact root cause, so I ended up using this code snippet to prevent pages being cached by WP Super Cache if they don’t have SlimStatParams in the HTML source:

add_filter('wp_cache_ob_callback_filter','slimstat_checker');
function slimstat_checker($bufferIn) {
  if ( strpos($bufferIn, "SlimStatParams") === false ) {
	define("DONOTCACHEPAGE","no slimstat no cache");
	error_log("no slimstat = no cache");
  }
  return $bufferIn;
}

hope this is useful for someone someday

frank

It works cool, what happens is that my home page is crashing because the plugin wants to cache some widgets, the ‘do not cache this widget’ option is only available in the appearance menu.

Is there any way I can not cache a line of Visual Composer? Put some html / javascript code or shortcode to not perform a certain part in cache of homepage?

I do not want to disable or delete the home page because it showed good performance improvement, I just want to remove some widgets, remember that they are all added via Visual Composer on the homepage, so I need code to not cache.

how can i disable super cache with using “widget logic plugin” for some widgets?

https://www.ads-software.com/plugins/wp-super-cache/

The majority of users that visit our site are more than likely registered and logged in when browsing so I have enabled the ‘Don’t cache pages for logged in users’ option, but I’m having issue with cached content still being served after a user has logged in and the logged in users cache content being served to new visitors.

Here’s a scenario:

– User1 visits the homepage not logged in
– User1 visits page A not logged in
– User1 logs into site and is redirected to the homepage
– User1 appears to not logged in on homepage and page A (served cached content)
– User1 visits page B and can see they are logged in (newly generated cached page)
– User2 (not logged in) visits page B and is served User1’s cached content.

Ive tried this scenario for admins and subscribers so doesn’t appear isolated to a role.

It seems like the ‘Don’t cache pages for logged in users’ option isn’t working. But I’m not sure what other options I can try to rectify the problem, so would be great if anyone had any thoughts.

Thanks

https://www.ads-software.com/plugins/w3-total-cache/

There are two (sweet) checkbox options on the Page Cache settings page within the General Options section that allow for per-user-role caching.

Don’t cache pages for logged in users
Unauthenticated users may view a cached version of the last authenticated user’s view of a given page. Disabling this option is not recommended.

AND

Don’t cache pages for following user roles
Select user roles that should not receive cached pages:

• Administrator
• Author
• Editor
• Custom User Role 1
• Custom User Role 2

The subtext for the first option helpfully explains a possible use problem for operating without the option checked. It indicates that a not-logged-in user might end up receiving a cached page which was generated by an authenticated user and thus reflects the privileged view that say the administrator had when last they viewed that page and triggered a new caching.

As this is a scenario I wish to avoid I will leave this option checked.

My question is, how does the next option (Don’t cache pages for following user roles) affect the the previous one ( Don’t cache pages for logged in users ).

If both options are checked, and let’s say that the user role “Administrator” is checked for cache exemption, will this allow the plugin to smartly avoid producing a static cached page from the administrator’s viewing of a public page?

In other words, does enabling this second option for particular roles essentially avoid the issue explained in the subtext of the first option by never generating the static cache page during a ‘bypassed’ user role’s visit?

https://www.ads-software.com/plugins/w3-total-cache/