Not writing/clearing files to cache

  • Resolved noahj-champion

    (@noahj-champion)


    9 years, 5 months ago

    Hi,

    Great plugin! I’m having an issue though. It is not working for me.

    Note: I know how to use your plugin, even though it is really my first time doing so. I’m not a newbie to such settings and understanding what Better WordPress Minify is doing, but I’m still having a basic issue. The files are not writing to the cache.

    Do you know of any thing that might be causing this issue?

    I thought at first there might be an issue with my .htaccess, but I cleared all values out of that and still have the issue. I’ve been testing for about an hour, other things as well, but I’m not finding any fix yet.

    I’ve also made sure the directories are writable.

    Oddly though at one point, still running the same setup, the files were writing to the cache.

    (note: this is in localdev)

    https://www.ads-software.com/plugins/bwp-minify/

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author Khang Minh

    (@oddoneout)

    So minification is working correctly but you don’t see any cached files, or nothing is working?

    Do you happen to turn on the debug mode, i.e. BWP Minify > General Options > Minify Library Settings > enable debug? Also I’m assuming that you’re using the friendly minify url feature?

    Thread Starter noahj-champion

    (@noahj-champion)

    Hi,

    I appreciate your response! I got it when you first posted it and have been troubleshooting pretty much since then. I was writing out a detailed response while still troubleshooting and had to change my response.

    I will report back, but I have narrowed this down to Google Chrome or probably one of its extensions.

    In short, I ended up disabling every plugin on my test site, leaving only BWP and Twenty Twelve and still the files weren’t writing to the cache, with a clean .htaccess and no snippet functions, etc.

    But, I will suggest this as this had me perplexed!

    If we flush the cache and there are no files to flush we get a notice message like…

    “Notice: Could not delete any cached files. Please manually flush the cache directory.”

    It was the “Could not delete” & “Manually flush the cache” that was helping me to think that BWP was having a problem writing to the cache all together, whether creating the minified files or flushing them.

    But when I tried Safari everything works perfectly, the writing of files to the cache and the cache flushing.

    I think a more suitable notice, as this one had me mislead a little bit, would be something like…

    “Notice: There were no cached files to flush”

    Or

    “Notice: Your cache is already flushed! There were no cached files to flush” etc.

    I will test this out further and report back!

    Thanks!

    Thread Starter noahj-champion

    (@noahj-champion)

    Hi,

    My brain must of tweaked out on this trying to find the issue, but I found it.

    I found the issue when trying another plugin and coming back to your plugin.

    I made the same super simple mistake again, but caught it this time, lol.

    I simply pasted my custom cache directory into the WordPress root directory. ??

    Which of course through everything off.

    Everything works fine and great now!

    Thanks Khang!

    Plugin Author Khang Minh

    (@oddoneout)

    Glad that you’ve got it working. What is your custom cache directory?

    Thread Starter noahj-champion

    (@noahj-champion)

    Hi,

    Thanks! Yep!

    My custom cache directory is…

    /data/content/public/compressed-elements/

    Plugin Author Khang Minh

    (@oddoneout)

    I guess that your WordPress root is: /data/content/public/ ? So previously you set the cache directory to /data/content/public/compressed-elements/ but did not create the compressed-elements folder there?

    Thread Starter noahj-champion

    (@noahj-champion)

    Ha, no. My WordPress root was my local machine path…

    I pasted my custom cache directory into the WordPress root field which wasn’t realistic. Whatever the out come of a non existent, wrong root path lead to this issue.

    When I took my custom cache path and pasted it into the right field, the one for the custom cache path everything worked correctly.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Not writing/clearing files to cache’ is closed to new replies.