Help Desk

"405 Not Allowed Openresty" after editing ticket

  • Posts: 1 Topics: 1
    | Permalink

    Hi! We’ve integrated Event Ticket Plus, but it keep on bugging. We’re able to create and save a ticket in a post. A product is generated automatically. So far so good. But when we try to EDIT a (saved) ticket, of ADD a ticket to a post that’s been saved before, we can’t save the changes. The system seems to be stuck in a loop and after a minute or two there’s a “405 Not Allowed Openresty” mention.

    One time, when I forced the endless saving process to stop, the system had created 6000 (!) products of the same product…

    Any idea? We’ve been struggling with the plugin for nearly two months now.

    Best, Koen

    Posts: 1 Topics: 1
    | Permalink

    This is what the error log read after trying to edit a post with integrated ticket:

    upstream timed out (110: Connection timed out) while reading response header from upstream, referrer: “https://staging.oor.nl/wp-admin/post.php?post=807441&action=edit”

    After editing and unsuccesfully saving the post the ticket within the post is gone. Even a ticket that was created and saved succesfully before editing the post or ticket.

    Posts: 5927
    | Permalink

    Thanks so much for reaching out!

    As a first step, let’s try to rule out if there is some type of conflict at play.
    This is usually because of:

    1.    A conflict with another plugin

    2.    A conflict with your WordPress theme

    3.    A template customization for the Events Calendar that requires updating

    When it comes to that type of issue, it is preferable to troubleshoot in a staging environment if you have one.

    A first quick test is to simply temporarily revert back to a default WordPress theme such as twenty-sixteen to see if the issue persists.

    The next step would be to go through our testing for conflicts procedure and let us know what you find out.

    Basically the goal here is to revert back to a bare WordPress installation to see if the problem persists. It also allows us to pinpoint what the cause of the issue is.

    But, before you do that, there are 2 things I would advise:

    1.    Make a backup of your database

    2.    Consider activating a “Maintenance Page” plugin if you are doing this on your live site (to minimize impact on your visitors)

    Also, before running through this, please make sure all of your Events Calendar related plugins and WooCommerce version are up to date.

    Let me know how that goes!

     

    Thanks,

    Jaime

    Posts: 65
    | Permalink

    Hey there! This thread has been pretty quiet for the last three weeks, so we’re going to go ahead and close it to avoid confusion with other topics. If you’re still looking for help with this, please do open a new thread, reference this one and we’d be more than happy to continue the conversation over there.

    Thanks so much!
    The Events Calendar Support Team

    | Permalink