wicked_folders_toggle

Hey @imincognito,

Sorry to hear you’re having trouble. This sounds like it could potentially be due to a conflict with another plugin. I’d recommend testing for a plugin conflict by temporarily deactivating all other plugins to see if the issue goes away (i.e. the folder toggle starts working). If it does, re-activate the plugins one-at-a-time until the issue returns to isolate which plugin is causing the conflict.

If it turns out to be a conflict, let us know which plugin and I can look into it further to see if there’s anything we can do on our end to work-around the issue.

Sorry I haven’t responded to your suggestion.

I may be the outlier here, but there is sth seriously wrong with the idea that every time there is a problem with a plugin or a pagebuilder or whatever, the std protocol is to disable all other plugins to identify potential conflicts.

This is not a complaint about your plugin – it happens with all plugins. And it’s a huge waste of time.

I almost never have this problem with Node – and the reason is that npm has an exhaustive dependency tree that generally manages conflicts for you. In the last 6 months, I’ve had exactly one conflict – and npm alerted me to that fact before plugins started failing.

I’m not that far along with my foldeer hierarchies – it’s actually faster to completely re-install it and rebuild my hierarchies from scratch.

Ridiculous.

Hey @imincognito,

I completely agree with you and if you know of a better way, let me know.

BTW, something I do when this happens is, instead of disabling all plugins, I’ll disable half and see if the issue goes away. If it doesn’t, I’ll then disable half of the remaining active plugins and so on until I find the conflicting plugin. Still a pain but it does help speed up the process.

This is the legacy of an evolutionary migration from blogging software to a CMS platform. Progress went thru a similar challenge with Sitefinity and, to their credit, they bit the bullet and did a major rewrite several years ago.

Regardless of the disabling technique you describe, WP plugins should be sufficiently silo’d that this exercise isn’t even necessary. I spend far too much time chasing down conflicts.

On a separate note – I use Admin Menu Editor to org my plugins. When Wicked Folders Toggle is in the root menu, it works. But if I move it to a sub-menu (i.e. Category Management Tools), I get an error 404. Since this is the only plugin where I have this issue, could I ask you to test your plugin with Admin Menu Editor?

Troubleshooting so far:
– reinstalled the site
– deleted all refs to WF in Admin Menu Editor (because it doesn’t do garbage cleanup for missing plugins)
– de-activated / deleted WF
– reinstalled WF
– tested WF Toggle in the root menu – worked
– moved WF Toggle to a sub-menu
– WF Toggle throws a 404

thx