etling

Same here. It does actually seem to work – just takes a VERY long time for the request to go through.

Editing to add: This bug is NOT happening on my local environment, and on local I’m using v 3.1.22 of this plugin. Maybe something changed? Or, maybe it’s something different about my local database or security vs. production.

• This reply was modified 2 years, 2 months ago by etling.
• This reply was modified 2 years, 2 months ago by etling.

Update: this actually seems to be an issue with Nested Pages, NOT this plugin. If I disable the setting “Replace Default [cpt] Menu” in Nested Pages, the menu item for Taxonomy Order appears as expected. Sorry.

+1 here. Fortunately I have uptime monitoring and frantically disabled plugins until I found it to be this one. This is *exactly* the concern I had with auto-update, which I am now disabling across every one of my projects. Ugh.

I just installed the most recent version to replicate what I had seen, and it seems like the conflict is gone. Marking as resolved. Thanks!

@averyethomas – see this Github thread for a solution. You need to include ‘wp-editor’ in the dependencies array now when registering & enqueuing scripts for a Gutenberg plugin.

I started getting this error as well, after upgrading from the Gutenberg plugin to WP 5.0. I’m using create-guten-block to scaffold my blocks. I have not found a solution or explanation yet, I’ll be sure to post here if I do.

Wow, thank you!