When cache purged, the minify files are removed and do not get re-created

  • Resolved wrip

    (@wrip)


    3 years, 5 months ago

    I’ve recently moved a staging website (subdomain) to a new server. I then pointed the IP address of the subdomain to the new server in Cloudflare. This is all fine. I then headed over to the dashboard and when I purge W3TC cache or press the “Save & purge cache” button, everything except the .htaccess from the /wp-content/cache/minify/ folder is removed. After a while, I see another folder such as “e7bbc” is created and it contains a single file called “default.include.css.id”. However the other minify files are not re-created inside the /wp-content/cache/minify/ folder.

    I also tried uninstalling and reinstalling the plugin by following the steps as mentioned on this post: https://www.ads-software.com/support/topic/no-minify-files-generated-but-w3tc-tries-to-link-to-them/. Nothing seemed to re-create the minify files. Not sure if I am doing anything wrong. I am not using any other caching plugin. The new server has Nginx caching but I’ve disabled that as well from the cPanel > Cache Manager.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @wrip

    Thank you for reaching out.
    It’s hard to identify the issue if I cannot see the website.
    Can you please share if you are using Manual Minify and if so, can you please share the screenshot of the Performance>Minify page?
    Also which Minify Cache method you are using?
    Thanks!

    Thread Starter wrip

    (@wrip)

    Hi @vmarko

    I think this has now been fixed. It looks like there was some conflict with the Nginx server-side caching. Like I mentioned earlier, I had disabled caching from the cPanel > Cache Manager for my staging site, which still did not help in rebuilding the minified file.

    So I completely stopped the Nginx service:
    service nginx stop

    After doing that, on the Performance > Minify page, I clicked on “empty cache” button and also pressed the “Save all settings” button. This time it created the “e7bbc” folder, as before, with the “default.include.css.id” file. After 2 minutes, it created another file called “single.include.css.id” within this folder and also created a minified css, css_gzip, css_gzip_meta and css_meta files inside the /wp-content/cache/minify/ folder as expected.

    Is there a way to make this work with the Nginx caching or do I need a different set of settings for this?

    To answer your other questions, yes I am using manual minify.

    Here are the settings in my Performance > Minify page:

    General
--------
Rewrite URL structure (ticked)
Disable minify for logged in users (not ticked)

HTML & XML
----------
HTML minify settings: Enabled
Inline CSS minification (ticked)
Inline JS minification (ticked)

Ignored comment stems:
google_ad_
RSPEAK_

JS
--
Not enabled
HTTP/2 push not enabled

CSS
---
CSS minify settings enabled
Minify method: Combine & Minify
Minify engine settings: Line break removal (ticked)
@import handling: Process
CSS file management: Theme: Child theme selected
Then, 25 files added...

HTTP/2 push not enabled

Advanced
--------
Update external files every: 86400 seconds
Garbage collection interval: 86400 seconds
Never minify the following pages: /members/
    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @wrip

    Thank you for the information.
    Glad to know the issue is resolved.
    The most likely cause of this is once the migration was completed, the rewrite rules did not apply so the nginx service needed a restart.
    Thanks!

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘When cache purged, the minify files are removed and do not get re-created’ is closed to new replies.

Tags