Forum Replies Created

Viewing 15 replies - 91 through 105 (of 199 total)
  • A bunch of us fixed that problem a few years back. We had a big discussion on this and added other fixes to the code (it might still be archived here). This plugin now works fine for us. Not sure why none of us released a forked version of this plugin to resolve problems for others though.

    Works perfectly for me. But then i am using a customized one that i patched myself and a few others here did too — look back in the logs in our hefty discussion and fixes. I am using the latest WordPress release and it works well.

    Depending on your settings you can tell if its minified by checking the page source.

    It wouldnt be too hard for the author to do seeing as how only 2 lines of code would need changing.

    chmod the permission

    Some times this plugin can be finiky. I would need more info before i could tell u whats wrong.

    I’d have to play around with the plugins you’ve listed to see what wp-minify is doing to break them. From what i recall though (experience from past issues) it was usually related to this things methods to shrink. It would strip out an important white space under a certain condtion in javascript code or something. Eeeks. I remember way back there was an issue with jQuery and this thing because when we looked we noticed jQuery changed something that made the code more ambigious and hence would break a plugin like wp-minify (it wasnt minifies fault, but jQuery for not using explicit brackets) but i believe a few of us here simply added brackets in our versions and were done with it.

    I will have a look at those plugins when i have time next week and see how they behave. It will always give me time to refresh my memory on this plugin. Last time i worked on it WordPress was at v2.8…but amazingly the plugin has never had an issue since.

    Need more info. Do u have a link to your site to see what is going on? Is it in fact minifying your root domain page when u look at the page source and pagespeed is still complaining?

    After looking at this plugins code i know it doesnt minify as efficiently as one would like which is why a few of us made our own forked version that shrinks the final size even more.

    The biggest mistake the author made is purposely putting in linebreaks due to his own preference (he hates looking at minified pages that dont have CRLF). That to me is quite possibly the dumbest thing i’ve ever seen. For a plugin that brags about shrinking pages why would the author get all emotional and subjectively add CRLF because he doesnt like the visual appearance of the result? Wouldnt that contradict the very purpose of the plugin? We were baffled by this and a few other silliness so we corrected them. But overall, putting these author intentional flaws, the plugin is better than the others i’ve tried..which is why i still use it…my own forked version of it that is.

    Thread Starter Kimberly

    (@kellogg9)

    i fixed it.

    This seems to indicate when you deactivated the plugin it was still thinking it was active. Not sure why it does that except that maybe another plugin was conflicting with it. I’ve tested by deactivating and mine works perfectly.

    As a heads up wp-mminify has its own cache folder located inside the wp-minify/cache folder. When you remove it, it forces itself to recache the css (or js) files. You can safely delete everything inside that folder.

    A test page would help

    You should prolly disable wp minify when it deals with Admin (e.g. u logging in). i most certainly dont have wp-minify applying any of its tricks when i attempt to login…seems like a waste (only useful for visitors of a site not me managing the website).

    You still have the problem. Can u give me the exact error message and what it shows in your error_log file?

    I rebuilt my own WP Minify for a few improvements and bug fixes way back when WP was at 2.x…in fact several of us in here were talking and putting in fixes so there are a few forked working versions we are using which are still working even on the current WP build (3.8). I have never had problems ever with this plugin. I havent used/tested it on mulit-site but for single sites it flawless and i also added a few improvements.

    I checked the code and i just wanted to point out to people here as i did in another related thread in this support area that you can simply make use of the “*” wildcard at the beginning and end of a directory or filename to have it ignored too.

    From the code it indeed is about putting the full file path but it can vary from server to server. There are many ways to get the precise prefix that this plugin is using but i figured for the lazy types “*” is the simplest solution.

    Just an update… @waynem1, you sir are a GENIUS! I decided to goof around to also see if i could pinpoint the problem after reading your post and you are absolutely right that the way to fix it is precisely how you outlined it above: by turning off wp_cron and using a real cron.

    Although it seems no one gives a sh!t what you wrote i thought i’d just say THANK YOU for the great effort and time to post this for future others (like me who popped in) to see. It helped tremendously. I probably would have moved to a different plugin if i didnt see this post 🙂

    Cheers!

    If it helps anyone i looked at the code some time back and you can see that you can use wildcards (*) at the begin and end of your path…otherwise you should include the full path (so that means including your site folder) to the file you want to exclude.

    Baffling why the author didnt mention this but after looking at the php code i saw he was using a specific command that allows for either style.

    The easiest is to just do something like:

    *file_to_exclude*

    Notice the use of “*” at the beginning and end. Doing it this way you dont need to include partial path.

Viewing 15 replies - 91 through 105 (of 199 total)