w3tc minify problematic (9 posts)

  1. rushza
    Posted 4 years ago #


    totally awesome plugin by the way.

    small issues though and I really appreciate any help you can offer.

    I am using plesk on a dedicated centos server using apache as a backend and nginx as a proxy.

    yesterday the minify was working fine and there was a minified css file inside wp-content/w3tc/min/xxxx/

    it then disappeared after a yum upgrade

    I tried to uninstall and reinstall and reconfiguring everything

    it only works if I turn off Rewrite URL structure

    the minute I turn it back on, it stops

    i tried caching the minify cache method between disk, memcached and apc and noticed that when i using the disk method, a folder is created by apache inside /min/ but no contents

    I tried to set 777 on the folder and rerun everything to create the minified file and what I get is that the folders and .htaccess is chowned by apache:apache and not myuser:psacln

    I tried to chown everything back to user:psacln and try again, that didnt work so I tried running php as a fast cgi app and that doesnt work, so I went back to apache mod with safe mode off, what then happpens is I get a file created in the folder called

    the contents of the folder is this string 1350314430

    nothing else.

    can you please point me in the right direction?


  2. rushza
    Posted 4 years ago #

    anyone? :(

  3. Boyevul
    Posted 4 years ago #

    I don't use the plugin, but I am commenting on your time frame between asking the question and "expecting" a response. I've seen threads go months without answers, but more often times than not, weeks.

    Have you tried Googling for an answer? That would probably be a lot faster.

  4. rushza
    Posted 4 years ago #

    Thanks boyevul,

    The only reponses from googgle i can find point to similar unresolved issues here on these forums.

    no so much an expectation rather than a request for assistance.

  5. Frederick Townes
    Posted 4 years ago #

    Are there errors in your error log? The problem persists with later releases?

  6. rushza
    Posted 4 years ago #

    sorted thank you

  7. Frederick Townes
    Posted 4 years ago #

    Ok, great.

  8. scottdaris
    Posted 4 years ago #

    I don't know if this applies, but see my post about automatic minifying errors:
    (btw, I meant to say *Important* parsing error found with automatic minify)
    In the minifying process, incorrect .js code was generated. You'll see what I mean in my post. Good luck!

  9. Frederick Townes
    Posted 3 years ago #

    @scottdaris, thanks will check it out.

Topic Closed

This topic has been closed to new replies.

About this Topic