Plugin conflicts

  • Hello Emre.

    Congrats for the plugin: is easy and it definitely helped me rise on my Google PageSpeed Insights test.

    It seems that the minify is working quite well, but the caching isn’t happening.

    I checked if it was a plugin conflict and I found that it is indeed, with this one:

    WordPress Calls To Action (https://www.ads-software.com/plugins/cta/ version 1.3.1, since the 2.0+ don’t work with my server config)

    When I turn it down, it works perfectly except for the CSS, which is missing (therefore, just text), and only works again and makes the plugin work great if I deactivate this other plugin: https://www.ads-software.com/plugins/modal-dialog/ vesion 3.0 (latest)

    I use and need these two plugins, with which Fastest Cache conflicts with, for increasing my Facebook fan count, so I can’t turn them down. I report this here in case it helps with the future development of the plugin (that I will still use for its gzip, minify, etc).

    If you want to check out my site and see it with firebug or the alike, it is https://www.biginfinland.com

    Best,
    –Santiago.

    https://www.ads-software.com/plugins/wp-fastest-cache/

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author Emre Vona

    (@emrevona)

    are there conflitcs with 2 plugins below?

    https://www.ads-software.com/plugins/cta/
    https://www.ads-software.com/plugins/modal-dialog/

    Thread Starter SantiagoH

    (@santiagoh)

    Yes, correct.

    If I don’t disable CTA, Fastest cache won’t work.

    Once CTA is disabled, the cached pages lack CSS, so they appear as just text on a white background.

    If I disable Modal Dialog, then the Fastest cache works perfectly.
    –Santiago.

    Thread Starter SantiagoH

    (@santiagoh)

    Hi Emre,

    After updating to the newest version of the plugin, I can see on the bottom of every page the following message (before updating it didn’t appear anything)

    <!– DONOTCACHEPAGE is defined as TRUE –>

    Is there a setting I can touch somewhere to activate the cache? It is enabled on the configuration panel (the only configurations I didn’t tick were “Don’t show to logged in users” and “Don’t show to Mobile users”

    Thank you,
    –Santiago.

    Plugin Author Emre Vona

    (@emrevona)

    Hi SantiagoH, DONOTCACHEPAGE is a constant in wordpress. Sometimes the theme or any plugin can set it as a true. If it is set as a true, the fastest cache does not create cache.

    https://www.ads-software.com/support/topic/donotcachepage-constant-is-defined-what-should-i-do?replies=1

    Thread Starter SantiagoH

    (@santiagoh)

    I worked around the problem.

    I have another website with another caching plugin, that didn’t have any conflicts with the plugins I mentioned. The key was using another version of the CTA plugin.

    I used the CTA’S plugin version 1.3.3 and now it doesn’t conflict with Fastest Cache.

    Not only that! My website now scores higher than ever on Google Speed Insights! This plugin works so well and easily, and it beats the speed score of Wp-Supercache by far. I am extremely happy!

    Now it only has one minor problem: it conflicts with this plugin:

    https://www.ads-software.com/plugins/random-post-link/

    This plugin generates a link to a random post on my website, since it has lots of content. This is the random link in my website: https://biginfinland.com/?random (you can see it on the right sidebar, clicking on “Leer un artículo al azar). Is there a way to make it work with Fastest Cache?

    If not, I will happily delete the Random post link.

    Thank you for your support, Emre. I will make sure to rate this plugin pretty high.

    –Santiago.

    Plugin Author Emre Vona

    (@emrevona)

    your welcome ?? If you vote me, it makes me so happy.

    Now it only has one minor problem: it conflicts with this plugin:

    https://www.ads-software.com/plugins/random-post-link/

    That’s expected confliction because this plugin does nor use ajax.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Plugin conflicts’ is closed to new replies.