m22878

If that is the case, then hide the 3 posts types from the Elementor settings.

Yes, call them Jeg Header, Jeg Footer, and Jeg Template.

You can do this test yourself. Make sure the 301 SEO Redirect is turned on. Then change the cache buster to just a lowercase L i.e. ?l=1 You can do that in the wp-config file. Then logout of the admin panel which should take you to this URL: domain.com/wp-login.php?loggedout=true&wp_lang=en_US And you will see it causes a “too many redirect” error. Then switch the line I told you I switched and go logout again and you will see no redirect error.

I think it’s due to how strpos vs isset works. I think strpos just looks for the first occurrence of a substring in a string, which is what I said is the problem. If the cache buster is simply a substring in a string then it tries to redirect. That’s why this page domain.com/wp-login.php?loggedout=true&wp_lang=en_US will try to redirect with the 301 SEO Redirect feature turned on, because the lowercase L cache buster is a substring of the string in this URL which is ?loggedout.

• This reply was modified 2 years, 7 months ago by m22878.
• This reply was modified 2 years, 7 months ago by m22878.

Changing this line:

if( !is_user_logged_in() && isset($_SERVER[‘QUERY_STRING’]) && strlen($_SERVER[‘QUERY_STRING’]) > 0 && strpos( $_SERVER[‘QUERY_STRING’], $this->get_cache_buster() ) !== false )

to this line:

if( !is_user_logged_in() && isset($_SERVER[‘QUERY_STRING’]) && strlen($_SERVER[‘QUERY_STRING’]) > 0 && isset($_GET[$this->get_cache_buster()]) )

Fixes the problem I’m talking about. Do you see any reason this change will cause any issues?

Yes, the SEO redirection is what’s causing the problem, but I want to keep it enabled. You still cannot understand what I’m saying? It’s unbelievable. Can someone delete my WordPress account? I don’t want to be on this site anymore. Just delete this account.

Changing the cache buster doesn’t fix the problem. If the cache buster is swcfpc then it will try to redirect pages that have query strings like swcfpcu or swcfpcr7r or swcfpc7rui etc. It can be any query string so long as it contains the cache buster it will redirect it. You don’t think that’s a problem? Or you don’t think it’s something you can fix so that redirects ONLY happen on pages which contain the cache buster and ONLY the cache buster without any additional characters before or after the cache buster?

Worker mode isn’t free and you literally recommend against using it in the plugin settings. I described what caused the issue and it seems like it could cause issues for all sites, because it even causes issues on logout, which has nothing to do with EDD.

If the query string on a URL simply contains the cache buster, even if the query string isn’t an exact match of the cache buster, then it will try to redirect the page. That’s a huge bug in your plugin, because it will cause redirects and break pages and probably screw up site indexing.

You should make it so it only redirects a page if the query strings contains the cache buster and ONLY the cache buster. Right now it can contain characters other than what’s in the cache buster, so long as the entire cache buster appears in the query string.

What about what I said how it says the purge all completes in the middle of the preloading pages? Look at the code in my previous post. This: [2022-03-25 05:23:55] [cache_controller::purge_all] Purged whole Cloudflare cache is always in the middle of the preloading links. Should it be like that? Seems like it would happen before all of the preloading links not in the middle of them.

The 40 second delay is caused by the preloader, it goes away if I turn that off, but I don’t understand how I went so long without noticing this delay since the preloader has been on the whole time, since it’s on by default and I never messed with it.

Anyway, in the logs it shows the cache purged in the middle of the preloading. Is this normal? The cache purge will show at different points in the preloading i.e. after 2 pages are preloaded, after 3, after 4 etc. it seems to change every time I purge, but it always happens in the middle of the preloading pages. Should it do that? I’m talking about this line: [2022-03-25 05:23:55] [cache_controller::purge_all] Purged whole Cloudflare cache you can see there are pages preloaded before it and after it.

[2022-03-25 05:23:25] [cloudflare::start_preloader_for_all_urls] Getting last published posts for post types: Array
(
    [0] => post
    [1] => page
    [2] => e-landing-page
    [4] => portfolio_page
    [5] => product
)

[2022-03-25 05:23:25] [cache_controller::start_cache_preloader_for_specific_urls] Adding 19 URLs to preloader queue
[2022-03-25 05:23:26] [preloader::task] Preloading URL https://www.domain.com/product/bundle-kit/
[2022-03-25 05:23:31] [preloader::task] Preloading URL https://www.domain.com/my-account/
[2022-03-25 05:23:34] [preloader::task] Preloading URL https://www.domain.com/checkout/
[2022-03-25 05:23:38] [preloader::task] Preloading URL https://www.domain.com/cart/
[2022-03-25 05:23:42] [preloader::task] Preloading URL https://www.domain.com/shop/
[2022-03-25 05:23:45] [preloader::task] Preloading URL https://www.domain.com/checkout__trashed/purchase-history/
[2022-03-25 05:23:49] [preloader::task] Preloading URL https://www.domain.com/checkout__trashed/transaction-failed/
[2022-03-25 05:23:52] [preloader::task] Preloading URL https://www.domain.com/checkout__trashed/purchase-confirmation/
[2022-03-25 05:23:55] [cache_controller::purge_all] Purged whole Cloudflare cache
[2022-03-25 05:23:55] [preloader::task] Preloading URL https://www.domain.com/slide-anything-popup-preview/

• This reply was modified 2 years, 8 months ago by m22878.

On this option: Prevent the following URIs to be cached which is the ONLY option that says URIs on it so how you don’t know what I’m talking about seems literally impossible, it has these two lines:

/checkout/*
/cart/*

Should it have those? Because one site has them and one site doesn’t. If I delete the plugin from each site, check database, all wp_options removed, then reinstall the same exact plugin on both sites, one site has the /checkout/* /cart/* in the “Prevent the following URIs to be cached” upon installation and one doesn’t have them. I don’t even know how it’s possible. Version 4.5.8 of the plugin. Should it have these two lines upon initial installation of the plugin or no?

Some more info on the purge issue. It’s super weird and buggy. Okay, if all I do is open an Elementor page to edit it and just remove a character or word from a title then save it. The page will never auto purge no matter how long you wait. But then after doing that, let’s say I add a character or word to the same title. Then it auto purges but shows the version where I removed a character or word, instead of showing the latest version where I added the new character or word. I have repeated this numerous times. If the first edit I make is to add text to the title then it will auto purge. It’s only if I do nothing but remove a character or word from the title that it never purges, and then does the bizarre behavior where if I add something after that it auto purges but shows the version where I removed something instead of showing the most recent version where I added something after I have removed something. Very strange.

Can you explain how it’s intended to be used, then? Is it to be used in addition to the built-in responsive images? So, you would continue to let the default responsive sizes be made when you upload an image and then let this plugin make the additional sizes you specify for the images on the fly?

So if only the static files are cached by Cloudflare then there is never a reason to purge the CF cache?

It was caused by the databased connection parameter being the same on both sites. I changed it to 1 on the cloned site. But how is this URL redirect stored in browser cache? It will not go away unless you clear browser cache, but users won’t know that and will continue to get redirected to the cloned site. Is there a way I can set this URL to the cloned site to expire from the main site so the main site stop redirecting to the cloned site? I removed it by flushing the redis cache and changing the database number on the cloned site, but as I said, if users went to the site before I fixed it then the URL redirect is stuck in their browser cache. How can I set it to expire? I tried setting site Browser Cache TTL to a few minutes but it won’t clear in the browser cache as I have one browser with it still stored and it’s still redirecting.

I verified it’s working with Query monitor, but can auth be set to anything? I just left it as 12345. But I get this warning in Query monitor. WP Redis: ERR AUTH called without any password configured for the default user. Are you sure your configuration is correct?

Is that okay? Also, what should the hit rate be? The last Object Cache plugin I used showed 99% hit rate, but open starting this one up it says hit rate around 92%. Is that bad?

• This reply was modified 2 years, 10 months ago by m22878.