Sorry to hear you’re having this issue. Just to confirm, have you tried it with the latest version (3.0.4) of the plugin?
If so, would it be possible for you to open your browser’s developer tools (normally F12), click on the “Console” tab, refresh the page, and take a screenshot of any errors in the Console tab?
I have tried the latest version (saw the note about it being a fix), plus dev tools and debug mode, but neither show anything useful. I have it running on a clone site and the folder does not appear even when Wicked Folders is the only active Plugin.
This reply was modified 5 months, 1 week ago by DigTek.
This reply was modified 5 months, 1 week ago by DigTek.
Hmmm, normally this issue is caused by a JavaScript error so I’m surprised to hear there isn’t anything in the dev tools. I assume this is happening on the Pages screen? Does it work with other post types (such as Posts)?
Would it be possible to get a screenshot anyways with the console tab just so I can see what you’re seeing?
I would agree, usually I can see why something did not work pretty easily, here is a screen, I am not sure what the DOM error is from, but it is there even will all plugins disabled, so is not due to Wicked Folders.
Thanks. I didn’t realize what ClassicPress was and just looked into it and now see what the issue is. It appears that ClassicPress doesn’t ship with many of the core scripts that are included in WordPress (which our plugin rely on).
So I’m afraid version 3 and higher of Wicked Folders won’t work with ClassicPress; however, you should be able to continue using an earlier version.
Sorry I don’t have a better answer for you but unfortunately ClassicPress is too different in this case for the plugin to work.
Thanks for taking the time to look into it, sometimes a fix is pretty easy, and sometimes not. In certain cases the missing scripts can be patched back in, but it is a double edged sword at best. V2 works great, so for the short term at least, that is an option.