• Resolved btreece84

    (@btreece84)


    This plugin always works great for me, even after setting up Redis caching on my site a couple of months ago, then today it starts having problems.

    I use the automatic update feature for the plugin, so 4.9.6.1 came in and I got the typical notice on the admin about the update. I dismissed the notice, reset my dashboard analytics view to today (I use this for current data), and then went about my business. Came back to the dashboard a little later, update notice was back and it was showing me 30 days again (which doesn’t include today).

    Dismissed the notice and refreshed several times, same issue every time. Cleared Redis cache and it went away.

    So, it seems an undocumented change broke this plugin’s compatibility with Redis Object Cache (https://www.ads-software.com/plugins/redis-cache/).

    Fix?

Viewing 3 replies - 1 through 3 (of 3 total)
  • The only change was made on the tracking component, switching from anonymization for each hit to all hits, for details see https://developers.google.com/analytics/devguides/collection/analyticsjs/ip-anonymization.

    So, IMHO, it’s unrelated to the issue you’re facing. Please note that the default report is stored in a cookie, on your computer. So switching the computer, clearing the browser cache or using a browser extension that somehow blocks cookies, it will have the same result, the report displayed will be 30 days. Since is cookie based I doubt a Redis conflict has anything to do with this.

    • This reply was modified 8 years, 1 month ago by Alin Marcu.
    Thread Starter btreece84

    (@btreece84)

    I am aware of how it’s stored. This also isn’t the first update to your plugin since I’ve been using Redis, in case you’re thinking object caching in general is causing the issue after an update. Not sure what it is; just reporting what happened.

    Love the plugin. At least a year using it so far and always does what it should.

    Thank you for the feedback, I really appreciate it! Please keep an eye on it and if you see it repeating let me know and will try to figure out what could be the culprit.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘4.9.6.1 Introduces Error with Redis Object Caching’ is closed to new replies.