Incompatibility with Cachify (NextGen v2)?

  • Herbert

    (@hneugebauer)


    12 years, 9 months ago

    Hi,

    due to some plugin changes, the load increased (migrating from qtranslate to WPML). So I hoped to overcome some of the impact by using Cachify, a light-weight caching plugin. First it looked good.

    … until today. I wanted to test the upgrade of Nextgen-Gallery from the last “stable” version 1.9.13 to the newest release 2.0.17… And here the problems start. I took me about one hour to sort out some very strange behaviour… to find the conflict, which is Cachify.

    The behaviour is strange. I clear the browser cache, then clean the cachify cache and load a page that contains a picture gallery. This looks good so far.
    Then I hit the browser refresh button… and now the pages does not show correctly anymore. It looks like a css is not loaded when the pages comes out of the cache.

    Interestingly, this problems does not happen with nextgen-gallery 1.9.13, only after the upgrade to 2.0.17.
    Also the problem goes aways when disabling cachify. So it is clearly a conflict between these two.

    Is anyone experiencing a similar issue?

    Thanks, Herbert

    PS: I also posted to the Cachify Forum… unclear where the problem lies.

    http://ww.wp.xz.cn/plugins/nextgen-gallery/

Viewing 7 replies - 1 through 7 (of 7 total)
  • tgrziwa

    (@tgrziwa)

    12 years, 9 months ago

    Hi Herbert,

    yes, I do use cachify as well. When activated, my NGG-galleries only show the first image. Next/Previous-buttons don’t work. This behavior starts with NGG 2.xx up to 2.0.17. When I deactivate Cachify, things went normal. Very strange: after updating NGG and emptying cache and browser-cache, the NGG-Gallery seems to work fine – but only for the first run; when I tried to show the galleries a second time, the old failure…

    I use OSX 10.8.4 an Safari 6.0.5

    Best greetings
    Thomas

    Plugin Contributor photocrati

    (@photocrati)

    12 years, 9 months ago

    We are starting to see a few reports of “cachify” creating a conflict; our developers have been made aware of this issue and will be working on it as soon as they can.

    If you would like to submit a bug report here: http://www.nextgen-gallery.com/report-bug/ to help us further review this issue it would be appreciated. We may also need log in credentials for your WordPress installation so our support team / developers can further review this.

    Thanks!

    – Cais.

    nico900

    (@nico900)

    12 years, 6 months ago

    Hi!
    The problem with the plugin “cachify” is still not solved. Do you know when a bugfix will be released?
    Thanks a lot!

    nico

    Thread Starter Herbert

    (@hneugebauer)

    12 years, 6 months ago

    Short comment from me, as I posted this originally.
    I just recently tested this again on my test-installation on my local laptop, and the problem is still there. However I also noticed that there were incompatibilities of other plugins with Cachify as well, not only with NGG.
    I switched to another plugin (Hypercache). There are several caching plugins available, and everybody has to do his private tests. I finally had to test 4 different caching plugins. Two of them did have compatibility issues, two of them worked OK and I chose Hypercache as the simplest / most lightweight one.

    I still think there is something that NGG does, that does not work well with caching, so I consider this topic as not resolved, but I found my solution / workaround.

    nico900

    (@nico900)

    12 years, 6 months ago

    Hej Hebert!
    Thank’s for your response! I will try Hypercache, too. Perhaps it is a usefull alternative for me, too.

    nico

    tizz

    (@tizz)

    12 years, 6 months ago

    Hi, I don’t know if W3TC plugin is lightweight, but it works very well and I have never seen any conflict with Nextgen.

    nico900

    (@nico900)

    12 years, 6 months ago

    So, I have tryed the plugin Hyper Cache. It works… Now, I am happy… 😀

Viewing 7 replies - 1 through 7 (of 7 total)

The topic ‘Incompatibility with Cachify (NextGen v2)?’ is closed to new replies.