nhrz

@sasiddiqui Hi, yes without the filter it works but it acts very weirdly. I will send you a video via email
I’ve also sent you the screenshots
Sometimes it works, sometimes it doesn’t, but the special characters never work. I’ll send more info via email
Thank you!

Do you have an email I can send the settings to? Thank you again!

Hi @sasiddiqui
Purely english characters doesn’t work either. Can’t seem to change the permalink at all, on any page
Old posts work with accent characters but as soon as I update any of the posts, the permalinks are reverted to the original and we can’t change them anymore
I’ve DM’d screenshots of both
Thank you again!

Hello
Added it to our theme’s functions.php file but it still isn’t working

We actually debugged the issue further and we can’t seem to change the permalinks at all? It doesn’t seem to be exclusive to accent characters but when we change a post’s permalink and then hit save, it reverts back to the default permalink. We can’t seem to change it at all?
Thank you again!

Hey guys! Thank you so much for the fast replies! @mlwilkerson yes it fixed the issue
Thank you!

Just want to say I finally figured out what the issue was, after an entire year of passively having this issue. Discovered the solution by accident.
WP Super Cache and Autoptimize don’t play well together. Tried deactivating Autoptimize before but it didn’t do much. Might’ve been another plugin as well back then, but deactivating it now seems to have fixed it. Major relief. Thank you again!

• This reply was modified 3 years, 5 months ago by nhrz.

Can it have something to do with the backend? Such as the server’s suhosin-values or perhaps max_execution_time or similar? Anything that could cause WP Super Cache to freeze on various pages for hours and hours? Takes literally days to preload my website right now and it keeps getting stuck on various pages. Haven’t had this issue before and I haven’t done anything that I can see could have caused this. Wondering if perhaps the webhost’s done something that could cause this behavior?
Thank you again Donncha!
Johan

What could make it stuck and not successfully cache a particular page for hours? Is there something I can look for in particular in the debug logs? Thank you!

This keeps happening. 6 hours after being stuck at 72 it finally resumed, got to 180 and was stuck again for another several hours. In the morning I saw that it had gotten to 184 but was again stuck. Left for work and 4 hours later, it now did all the pages (400), but it seems to keep getting stuk like this at various places during the preload

No idea what the issue could be or how to debug this to know what is going on? I have debugging turned on but no idea what to look for in the logs?
Thank you again!
Johan

Just got stuck at page 72 again…. Preloading working fine until page 72 and then stop. Now I can’t cancel it or anything at all
Johan

Awesome, thank you!

Why not add it as an option of the current plugin?

Fixed. Finally. The issue was with the “Update preload cache files” setting under “Preload”. This needs to be set to 0, so it never updates them. Otherwise you get the above issue. This should be a clearer as it’s not at all clear there’s a correlation Thank you

My pages are static and don’t change unless I change them so I’m fine with having to clear the cache when I want the page to update

I’ve set “Cache Timeout” to 0 under “Advanced”. “Timer” among those same settings is at 600, fwiw. “Update preload cached files” under “Preload” is at 600. Not sure if any of these settings matter. But I just tried it now — an hour after I posted my earlier comment, and the cache is already “outdated”. I visited a page that was cached just an hour ago, and it now took a few seconds to load, as if it wasn’t cached at all. All subsequent refreshes are now instant.

The cache-message still doesn’t appear in the source.

So I’ve disabled the plugin deleting old cache files, from what I can see. And I’ve enabled preload mode, and preload mode updates every 600 minutes. This effect is still present and I can’t get the cache files to be served for longer than an hour or so

• This reply was modified 5 years, 8 months ago by nhrz.
• This reply was modified 5 years, 8 months ago by nhrz.

I have to take things back. It indeed still seems to be on-going. I can’t get the cache to work.

I started everything over now, from scratch, for debugging purposes. I cleared all the previous cache. Went into “Debug” and activated cache message and then started the pre-fetch process.

The whole page is now cached. Any browser I visit the page from is blazingly fast. Debug shows no issues — cache is being loaded properly. However, when I open the source of any cached page, the cache message isn’t there. And I’m suspecting my previous issue will persist. In a few hours, when the cache is a few hours old, when I visit any of the previously cached pages, they will take a while to load once again. And then they will, once again, be cached.

I have no idea why the cache expires like this, when all settings should make it not expire at all. And maybe the lack of cache message in the source has got something to do with this?

I’m clueless. Everything works now. In a few hours, however, when visiting the page, it’ll be as if it’s not even cached, once again

@kayacanakin I solved the issue by activating pre-loading cache and manually starting it as well. I saw that no pages were being cached and so turning pre-load on ensures they are actually being cached, and I now get served the cached page all the time