Problem with Google Cache

  • Resolved Kazekaii

    (@kazekaii)


    6 years ago

    Hello.

    I think the plugin has a potential problem. If you do a change in the CSS (even if it is a minimum change) you have to press FVM Purge. The problem is that the plugin create another minify CSS with another name, so all the pages that Google have in his own cache have an old CSS that it doesn’t exist any more.
    Is there a possibility to keep the old files and not remove it?

    When Google is doing the updates of their algorithms they are analysing their own cache files. So at this moment Google is doing an análisis of pages with a CSS that is not existing. There is a possibility that google check if all the files in the HTML are online and, of course, if you go to a cached page in Google you cannot see the website correctly.

    A solution can be a button to create the new CSS and purge WP Super Cache but not purge the old cache files or an option to decide witch old cache files you want to purge.

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Author Raul P.

    (@alignak)

    Hello,

    The purpose of “cache purging” is to purge all caches, so the files get deleted and new ones are generated.

    Any cache plugin, reverse proxy or other caches have to be cleared after FVM, so that a new cache is generated and inserted properly on the html.

    You should not do development with FVM on.
    You should have a copy of your site somewhere else, do all the changes and then “deploy” those changes at once to your live site.

    From what I understand, you are concerned about the “cached” version on google search, right?

    Well, if you hit purge you are deleting those files, but when google cached that page, they should have also probably cache your css and js files… if not, see if your robots.txt is not preventing it.

    Currently there is no easy way to preserve the old cached files like you suggest, although I may look at it in the near future.

    The problem lies, some people have dynamic css files that change in every page view and because they forget to add those to the ignore list, the cache grows indefinitely.
    Also people expect the cache purge to actually delete those files.

    I’ll consider an option to preserve them in the future.
    In the meanwhile, perhaps using a CDN will solve your issue temporarily, since purging them on wordpress doesn’t do that on the cdn.

    You could also try to inline the css for now.

    Thanks for the message, I have taken note of this as a feature request.

    Thread Starter Kazekaii

    (@kazekaii)

    Yes the problem it with Google cache, and we don’t have CDN (too expensive).

    Thank you so much for your answer.

    From my point of view there are 2 solutions:

    – One button to create the new CSS and purge WP Super Cache but not purge the old cache files. And another button to purge everything as you have now.
    – The other solution (more elegant probably) is to add a check option in the /options-general.php?page=fastvelocity-min&tab=settings to decide if you want to keep old CSS.

    Thank you so much again

    Thread Starter Kazekaii

    (@kazekaii)

    Hello again.

    In version 2.3.6 you added the following:
    – added option to reload the cache, while preserving the old static files.

    This solved our problem with the google cache.
    But now it seems that this option has disappeared. Or maybe I don’t see it.

    We have problems with the google cache again and would appreciate being able to keep the old css files. I need it.

    It’s possible?

    Thank you.

    Plugin Author Raul P.

    (@alignak)

    @kazekaii That option is already default on 2.6.0 onwards, but the cache directory has changed.

    What cache problem are you facing?
    The old cache files should still be there.

    Thread Starter Kazekaii

    (@kazekaii)

    If it is by default, why when I press “FVM Purge”, the contents of wp-content/cache/fvm (the new cache directory if I’m not mistaken) and /wp-content/fvm/out is completely removed? This causes that the file that was before the purge no longer exists.

    Do I have to activate something? Am I doing something wrong? Where are the old css? :\

    – What cache problem are you facing?

    The problem is that if google saves our page in his cache and I purge, the css link that Google has saved does not exist. This affects that when someone push “In cache” in their results, the page is seen without css.

    Thanks for reply!

    Plugin Author Raul P.

    (@alignak)

    @kazekaii are you sure you are running the latest 2.6.0 version?

    The structure is wp-content/cache/fvm/timestamp/out/(hash).(css|js)

    When you purge the cache, it increments the timestamp and generates a new directory with the new files. The previous one is preserved.

    Inside wp-content/cache/fvm there will be multiple directories. One for each time you purge the cache. After 3 months, a cronjob will then automatically delete the ones that are 3 months old.

    So if you log in via sftp, you should be able to see that the old files are still there, inside each out directory.

    Are you using a custom path for the cache?
    You can post a screenshot of all the settings please.
    Also ensure you are using the latest version, 2.6.0.

    This is how it should look inside the wp-content/cache/fvm directory if you purge caches multiple times. https://prntscr.com/my65bu

    • This reply was modified 5 years, 8 months ago by Raul P..
    Thread Starter Kazekaii

    (@kazekaii)

    I have latest 2.6.0 version.
    https://prnt.sc/n0ws10

    When I purge the cache (FVM Purge from the admin bar), the timestamp directory that was in wp-content/cache/fvm disappears, and instead a different one appears with another timestamp.
    Before: https://prnt.sc/n0wsb0
    After: https://prnt.sc/n0wsjj

    About custom path for cache, I use the default.

    Screenshots of settings:
    https://prnt.sc/n0wxa0
    https://prnt.sc/n0wxsu
    https://prnt.sc/n0x09o

    Thanks!

    Thread Starter Kazekaii

    (@kazekaii)

    Hello.

    I changed the cache path and it seems that now it saves all the timestamp directories.
    Cache path: https://prnt.sc/n3oxvy
    Result: https://prnt.sc/n3oytg

    You say that after 3 months, a cronjob will automatically delete the ones that are 3 months old.
    Is it possible to modify these 3 months for another amount of time or disable the cron?
    I’m interested in not delete anything, or to take much longer to delete.

    Thanks!

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Problem with Google Cache’ is closed to new replies.