• Resolved frogbuttt

    (@frogbuttt)


    Latest version 6.0.1 error with Redis Object Cache

    If Redis Object Cache is active and you update to The Events Calendar Version 6.0.1 you can no longer access the events edit page in gutenburg only classic editor

Viewing 15 replies - 1 through 15 (of 17 total)
  • Same issue here, didn’t know it was because of Redis Object Cache being active during update.

    How to solve it? Switching of/on Gutenberg in settings doesn’t help.

    Plugin Support Chad McCullough

    (@cmccullough1967)

    Hello to both of you,

    Thank you for bringing this to our attention. I’ve reached out to the developers to see if this is a known issue. As soon as I hear something, I will get right back to you.

    Thank you so much,
    Chad

    I can confirm that even with today’s release the only way to use the block editor on events is to disable Redis Object Cache.

    Plugin Support Abz

    (@abzlevelup)

    Hi @7thcircle, sorry to hear about this issue, the object cache is not yet resolved with the latest release. We’d recommend disabling Object Cache while we’re working on a fix. Or you could also test this workaround — and see if this does the trick. You can try adding this snippet to your wp-config.php file:

    define('WP_REDIS_CONFIG', [
      'compression' => 'none',
    ]);
    define('WP_REDIS_CONFIG', [
      'serializer' => 'php',
    ]);

    For more information on this topic, please see the following Redis links on compression and serializer.

    To be safe, we’d recommend conducting these tests on a Staging Server. Also, please keep a working backup of your website.

    If you do have other concerns or issues you need help with, please create another ticket, as it helps us track different issues.

    Again, thank you for your patience. Hang in there.

    Best,
    Abz
    ________________________

    Internal Bug Ticket Reference:
    TEC-4348

    The code does not solve anything, and the idea that I should disable the cache is not helpful across multiple production sites.

    I would ask if submitting a ticket under my license would help, but based on the responses I have seen in the forum those tickets are not getting any higher priority.

    Plugin Support Abz

    (@abzlevelup)

    Hi @7thcircle, apologies for the inconvenience, the workaround worked for other users, and thanks for confirming that’s not the case for you. For now, I would suggest deactivating the object cache, while we are still working on a fix.

    I would ask if submitting a ticket under my license would help, but based on the responses I have seen in the forum those tickets are not getting any higher priority.

    Since you have an active license and for us to help you better, I would still suggest you open a Support Ticket on our Help Desk. Also, for us to follow WordPress Forum Guidelines in regard to premium users and for us to track down issues more efficiently as well.

    Hang in there.

    Best,
    Abz
    ________________________

    Internal Bug Ticket Reference:
    TEC-4348

    Plugin Support Gladys

    (@greventscalendar)

    Hi there,

    With our latest release of The Events Calendar 6.0.4, we resolved the issue between the Events Calendar and Object Cache. Please be sure to review our full Release Notes for more details and update your plugin whenever you get a chance.

    As always, we suggest testing updates on a staging site first and having a recent backup, but it should all be smooth sailing. If you implemented any workarounds, you can remove them after updating the plugins.

    If you still have issues after updating to the latest releases, please open a new support thread and include any specific details and screenshots if possible.

    Have a great day,
    Gladys

    The issue is not resolved. If Redis Object Cache is enabled at the server level the block editor is not available for The Events Calendar free or Pro.

    FYI, why create a new ticket for the same issue when nothing has been resolved. All that does is make it harder for users and support to see what is being done to resolve the issue.

    • This reply was modified 1 year, 5 months ago by 7thcircle.
    Thread Starter frogbuttt

    (@frogbuttt)

    Yeap same issue after updating this was not fixed in 6.0.4

    Plugin Support Abz

    (@abzlevelup)

    Hi @frogbuttt @7thcircle, sorry to hear about this. I’m curious about why it still occurs on your end. Since you have an active license for us to help you better and learn more about this, please open a Support Ticket on our Help Desk. Also, for us to follow WordPress Forum Guidelines in regard to premium users.

    We look forward to helping you out with this one.

    Best,
    Abz

    See ticket 388212 opened Oct 25. I have even provided a staging environment for you to test in.

    It has been over a year that you have had issues with Redis, but previously it was just with the listing in the dashboard when I was looking at all events.

    Plugin Support Abz

    (@abzlevelup)

    Hi @7thcircle, it seems like one of my colleagues is already responding to your queries. They’d be notifying you whenever there are updates.

    Appreciate your time and patience here.

    Best,
    Abz
    ________________________

    Internal Bug Ticket Reference:
    TEC-4348

    Plugin Support Abz

    (@abzlevelup)

    Hi @frogbuttt @7thcircle, I am curious if the latest updates fix the issue. Worth to test and trying out the new updates. To be safe, we’d recommend conducting tests and updates on a Staging Server. Also, please keep a working backup of your website.

    Please keep me posted.


    Bug Ticket Reference:
    TEC-4348

    No, the only way to use the plugin is to disable Redis completely.

    Plugin Support Darian

    (@d0153)

    @frogbuttt @7thcircle @imc67

    Our engineers are still working on the solution, though there are some complexities, and it will take some time to craft and validate before release.

    I have added your case to our internal ticket. While we don’t have an ETA at the moment, you’ll get notified once there is an update and fix.


    Bug Ticket Reference:
    TEC-4613

Viewing 15 replies - 1 through 15 (of 17 total)
  • The topic ‘Latest version 6.0.1 error with Redis Object Cache’ is closed to new replies.