Gutenberg issues with module activated

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Contributor jarnovos

    (@jarnovos)

    Hi @onepack,

    I wouldn’t initially expect Complianz to cause a “405 Method Not Allowed” error. This seems like a potential server-side restriction. Perhaps you have some rule in your .htaccess or nginx.conf file that restricts certain HTTP request types, such as GET/ POST, which throws a 405 Method Not Allowed method when using Gutenberg as a result.

    I’ve additionally tried reproducing this on an environment with only Complianz and Gutenberg activated, but am currently unable recreate the described behavior.

    Kind regards,
    Jarno

    Thread Starter onepack

    (@onepack)

    Thanks.

    I might have been to quick to judge.
    The system now keeps on giving me the errors even with all Plugins deactivated and swapping back to the parent twenty-twenty-two theme.

    So that indeed rules out the option that this module is responsible for this.

    .htaccess is the default so I’m not sure what else could be causing this.

    Greetings

    Thread Starter onepack

    (@onepack)

    Bingo!

    The OPTIONS method seemed to not be configured on the server!
    I added this, rewrote confs and this fixed things.

    Maybe this helps others experiencing the same issue.

    Plugin Contributor jarnovos

    (@jarnovos)

    Hi @onepack,

    Thank you for confirming that Complianz turned out to be unrelated to this, and for sharing your solution with the community!

    Kind regards,
    Jarno

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Gutenberg issues with module activated’ is closed to new replies.