Admin redirect bug in the latest version?

I’m having the same issue. When installing plugins, it redirects and either doesn’t go to the screen to activate the plugin, or in some cases, doesn’t install the plugin at all. I deactivated CPT UI and was able to successfully install and activate it.

I’m not using Astra/Elementor.

Checking on this item you two.

Likely related to Updated: Redirect user to the “add” tab if deleting the last post type or taxonomy created. but I am not yet sure why it’s getting to that point in some situations that it shouldn’t be.

@klaro @jodzeee can either of you provide some specific actions you’re seeing this behavior with? I’m looking at the changed spots with 1.7.0 but things are pretty “guarded” so I’m trying to determine where the proverbial holes are.

I know and see that jodzeee was doing plugin installation/activation. Any other spots for you?

@tw2113 for example go to Appearance > Menus > [no changes needed] > click Save Menu > menu is saved yet I land on:

/wp-admin/admin.php?page=cptui_manage_taxonomies

I just tried using WordPress Importer to import an XML file and it did the same thing.

Installing plugins from the repo seems to be okay, it’s just if I upload one that it happens.

Can both of you give this version a try? It has a couple spots updated that I hope address this issue.

https://www.dropbox.com/s/tevta00heb5npry/custom-post-type-ui.zip?dl=0

That seems to have done the trick, not being redirected anymore.

Works for me as well. I was able to upload a plugin and import an XML file successfully. Thanks for your quick response!

Thanks for reporting the findings and being willing to help test things out.

In the meantime i stumbled on a different new bug so that’ll be bundled in with a 1.7.1 release as well. Yay releases!

Marking as resolved for the time being.

And released the bugfixes to everyone.

FYI, you cannot update (via WP update plugin GUI) to 1.7.1 – because it still takes you to /wp-admin/admin.php?page=cptui_manage_taxonomies

Had to rename the plugin directory via SFTP first; then upgrade works.

Yeah, that’s going to be a side effect for those who already moved to 1.7.0, depending on how they attempt the new upgrade. Anyone who gets to go from 1.6.2 -> 1.7.1 will have fewer issues.

Wish this wouldn’t be the case, but…

On the brighter side, it’s not the most tumultuous release I’ve had either ?? That would be what turned into 1.0.0 in the end. That was a long week.

@wwwcre8r and anyone else, you should also be able to get things updated if you deactivate it first, temporarily.