Support » Plugin: Fast Velocity Minify » Overrides themes CSS files permanently – danger!

  • I have no idea what kind of coder you are and whether this plugin actually does anything good – but what it did for me is emptied my child themes style.css file with my recent work – that I had not backed up, I was about to – thought would go and try another CSS compiler plugin, other than w3total cache, as I find it a little too heavy – and what a surprise??? Why, can you explain, why do you need to do that?
    This is all about WordPress and WordPress API.
    You can alter all CSS files before output with PHP filters – so WHY WHY WHY coding and not reading WordPress API – deleting my file? GOD – haven’t slept for 2 days, now I will have to spend 2 hours getting all back…and it happened to be I’ve used notepad ++ instead of Netbeans ad it god closed and file refreshed and it’s empty…
    Will code my own CSS compiler and cleaner for the community – don’t promise people what you cannot deliver and use filters in WordPress development – never delete or empty others files – bad coder who don’t read the docs and writes more code, because can’t read the docs, bad practice, means bad code, means very bad plugin.
    Pissed OFF

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Raul P.

    (@alignak)

    @sergedirect I think you have reviewed the wrong plugin… there is absolutely no way, this plugin touches any original css or js file.

    If you say otherwise, prove it, by quoting which part of this plugin code is doing it, or where we are not using filters!!!

    Of course we use filters, and of course we would never overwrite any original files.

    I woild say that you either used some other plugin, or you, yourself have made a mistake and overwritten your css files some other way that NOT via this plugin.

    This plugin copies your css and js files to the uploads/fvm directory and then, uses those copies to generate new, merged and minified files. It doesn’t optimize individual css or js files.. it merges a copy of them into another, and then optimizes the new file.

    All files will be on wp-content/uploads/fvm AND they are all enqued using filters, while the original ones are also dequeued with filters.

    Obviously, deactivating FVM will mean that the plugin stops showing the optimized newly generated files and it will go back to how it was exactly as before, because it doesn’t touch any original file.

    If you say it does, please prove it how and where, by referencing which part of the code did it!

    Plugin Author Raul P.

    (@alignak)

    Or… you probably have “updated” your child theme without noticing (there are manual and automatic updates https://codex.wordpress.org/Configuring_Automatic_Background_Updates ). That would definitely reset your css file, as with any theme that gets updated and has modifications on it.

    Either way, FVM does not overwrite original css or js files.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Overrides themes CSS files permanently – danger!’ is closed to new replies.