• Resolved neoswf

    (@neoswf)


    I have installed Autoptimize together with W3 Total Cache, in order to get the Above The Fold optimization.
    After seen that too many features of Autoptimize are equal or conflict with W3TC, I have decided to uninstall it. Problem is that the moment I done that, W3TC minification stopped working and started generating errors.

    So I uninstalled W3TC completely from the blog, made sure the .htaccess files returned to there default, and installed again W3tc, but the problem maintained.

    Seems like the Autoptimize left something behind him after it have been uninstalled.

    My questions are:
    1. Do you guys aware of this problem and can give me directions on how to resolve it?
    2. What exactly Autoptimize modify in order to apply its customizations? I looked into the .htaccess file and have not found any code of yours.

    Thanks in advanced!

    The page I need help with: [log in to see the link]

Viewing 12 replies - 1 through 12 (of 12 total)
  • Plugin Author Optimizing Matters

    (@optimizingmatters)

    Have never seen this before I’m afraid NeoSwf. Upon deletion AO does clean up after itself, but maybe something went wrong (although I don’t see how that would cause those HTTP 400 errors), so check if:

    * there is no autoptimize directory in wp-content/cache/ any more
    * there is no autoptimize directory in wp-content/plugins/ any more

    if both are gone, then there is nothing of AO left.

    hope this helps,
    frank

    Thread Starter neoswf

    (@neoswf)

    Thank you Frank for your fast answer! Appreciate it! I’ll update more when i’ll solve the problem.

    Thread Starter neoswf

    (@neoswf)

    Hey Frank. I have discovered a AO folder inside the /Cache folder. Have deleted it and yet, nothing been improved…

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    well, if the 2 folders are gone, then there is no trace of AO on your system any more I’m afraid, so it logically can’t be AO.

    the error is of the “minify” component that is part of W3TC, do you have any info in your php errorlog that might be relevant? does switching minifiers in W3TC (if I remember correctly you can choose which minifier to use) change anything?

    Thread Starter neoswf

    (@neoswf)

    Man, you are amazing. It’s not your plugin, and yet, you are helping me. It’s impressive!
    I must admit that I never modified/played with the compressors. It gives more options and its damn nice, but unfortunately the server has yet been able to deliver the files.
    I’ll check the server error logs, and also Minify google groups. You manage to find many topics when you search for 400 keyword.

    Thanks again. You are the best!!!

    Thread Starter neoswf

    (@neoswf)

    Ok. I have found an article speaking about a known bug of Minify, from 2011. The bug solution is to change minify mode from auto to manual, and it solved the problem! Why it stopped working? No idea, but at least I found the solution.

    Thank you man. You are the best!!! You give exceptional support for your users. Its not that common these days.

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    good job fixing it NeoSwf! now if you ever want to swap W3TC’s (ancient) minify for a more modern & flexible solution; you know where to find Autoptimize 😉

    have a nice weekend!
    frank

    Thread Starter neoswf

    (@neoswf)

    Hey frank. I appreciate a lot all your attention. The reason I prefer working with W3TC is that it gives me total control on the configuration. I am a geek and I love to know what I’m doing. Also expire headers never worked for me out of the box with AO. No idea why. I have installed now it again, and again the expire headers do not obey and do not appear…

    Thread Starter neoswf

    (@neoswf)

    BTW, I discovered the real cause for my issue. Minify doesn’t like Symlinks. I had one configured on my blog (assets folder). It broke him.
    https://github.com/OddOneOut/bwp-minify/issues/17#issuecomment-44542238

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    re. expires-headers; AO has expiry directives in wp-content/cache/autoptimize/.htaccess but that obviously only works when you’re on Apache and when your Apache config allows the .htaccess (and the rules in there) to be honored.

    if not on apache you should either configure your webserver to add the expirey headers (cache-control and expires) OR you can untick the “serve as static files” option in which case the optimized CSS/ JS will be served by PHP-code with the correct HTTP response headers (which is what Mr Clay’s minify does as well).

    hope this clarifies 🙂

    and if you like geeking out; AO’s config is one thing, but there are _a lot_ of filters you can hook into to tweak the functionality even more. I bet you could have fun with those :-p

    Thread Starter neoswf

    (@neoswf)

    Hey Frank, and thanks again.
    Can you share with me a link for the documentation of the filters you have mentioned?

    Thank you!

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    no documentation, there’s only code I’m afraid;

    
    grep -r apply_filters wp-content/plugins/autoptimize/* | less

    there are 116 filters in the codebase of what will become AO 2.4 (more info on AO 2.4 here) and 3 actions.

Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘Autoptimize uninstallation problems’ is closed to new replies.