Support » Plugin: Fast Velocity Minify » CSS Options break my site

  • Resolved polymathy



    I have installed the plugin on a development site. There everything works just fine, with these CSS settings:

    • Preserve the order of CSS files
    • Disable the “Print” related stylesheets
    • Inline CSS in the footer

    I then moved the whole site to a different location using the “All in One Migration” plugin. On that different location there was another WordPress site installed before. I made sure to purge everything, however.

    At the new location the layout completely breaks. Only when I disable CSS processing it works. I tried deactivating and deleting the plugin and then reinstalling it again, but that didn’t solve it. The problem only occurs, when I’m not logged in. I don’t have any other caching plugin installed.

    Can you imagine a reason for this?

    Edit: Is it possible that when deleting the plugin, not everything is deleted? I noticed that after reinstalling, some of my options where still there. How can I make sure everything gets deleted when reinstalling?

    • This topic was modified 2 months, 2 weeks ago by  polymathy.
Viewing 1 replies (of 1 total)
  • Plugin Author Raul P.



    You probably need to use the ignore list.

    When you enable the fix page editors option (on by default), optimizations only show up on the frontend for anonymous users.
    I suggest opening a new browser window in incognito mode (Google Chrome) on your dev site, to check if things are as they should.
    If something is broken, you need to tweak the settings and adjust as needed.

    Migrating to the new hosting should work exactly the same.
    Just remember to purge FVM once migrated, as well as any server cache.

    If you are sure to be logged out on both versions and one looks different than the other, then purge your browser cache as well as any server cache.

    If settings are exactly the same and they are still different, I’m sure something is

    a) wrong on the wp_options database (probably domain, file paths, etc).
    b) you have some .ini file on the root of the site changing something
    c) your server is running windows, or some other configuration different from your dev

Viewing 1 replies (of 1 total)
  • You must be logged in to reply to this topic.