404 Errors

Support response to above:

While I totally trust him when he says this is pointless, this method exists in their code and is available to run so it was created for a reason otherwise we couldn’t have removed that cache. If AO is doing all the work automatically, then such a function would be obsolete and without purpose / shouldn’t exist.

Is the following true? Does clearing the AO cache not clear the css/js?

Again, this function doesn’t clear your css/js files generated by AO, probably just the cached pages.

The sole purpose of this function is to clear the css/js files generated by AO.

The sole purpose of this function is to clear the css/js files generated by AO.

Does clearing the css/js always result in new filenames? Or can you explain under what conditions new filenames are generated?

The support member seems to think the AO cache is not being cleared, as he still sees the same filenames after cache clearance.

The support member is wrong, files _are_ being cleared from cache. Depending on the circumstances new filenames will or will not be created. Also; immediately after clearing AO will automatically warm it’s own cache, and that is what probably leads our support member friend into believing the CSS/JS cache is not cleared. But believe me when I say the support member is wrong ??

(real stubborn guy, that support member, the only thing he _really_ should do, instead of questioning all of this, is just tell the devs to remove that autoptimizeCache::clearall()-call because the AO-developer says they should not call that function upon every post publish/update because it’s hurting performance significantly!)

Support has agreed to pass it on to developers. Hopefully they will remove the function!

Thanks for your help ??