When deactivating plugin, 500 internal server error is caused

  • Resolved adamjames128

    (@adamjames128)


    7 years ago

    Hi there,

    I recently posted an issue whereby the “convert to blocks” function in Gutenberg would use ThirstyAffiliates image blocks instead of regular image blocks when the plugin is enabled.

    The recommendation was to de-activate ThirstyAffiliates while converting to blocks – this isn’t ideal but I tried it.

    The result was a 500 internal server error as soon as hitting “deactivate.”

    Normally, if the issue was activating a theme/plugin, I could just deactivate by renaming them via FTP. But I have no idea how I’m going to fix this.

    Looks like I won’t be launching my new site today.

    To solve this I’ve tried manually deactivating my theme & all plugins but I’ll explore other options – I was hoping not to have to mess around with my htaccess file etc.

    Note: Here’s a link to my original support thread: https://ww.wp.xz.cn/support/topic/when-converting-to-blocks-ta-image-block-is-used-instead-of-regular-image-block/

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter adamjames128

    (@adamjames128)

    7 years ago

    Update: looks like upon deactivation, my htaccess file was corrupted. A fresh htaccess solved the problem.

    It would be great if the original issue involving convert to blocks could be fixed – kind of surprised that my last post was marked as resolved when the fix hasn’t been rolled out.

    – Adam

    Ray Abella

    (@supportray)

    7 years ago

    Hi Adam,

    I’m glad to hear that you’ve found the issue that’s causing the 500 internal server error.

    Please be aware that the convert to blocks related issue has been raised to our developers and have our attention. We are still working on the fix for this issue but I’m afraid that we can’t provide an official ETA of its release.

    Rest assured that we’ll get in touch with you again once the fix update is available!

    I’m sorry for any inconvenience and thanks again for your patience.

    Best regards,

    Thread Starter adamjames128

    (@adamjames128)

    7 years ago

    Hi Ray

    It seems like ThirstyAffiliates corrupted my htaccess upon deactivation.

    Can this be investigated from your side please? It’s a serious issue to break a site upon deactivation.

    While it’s “resolved” for me, it’s still a possible issue for others.

    – Adam

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

The topic ‘When deactivating plugin, 500 internal server error is caused’ is closed to new replies.