Issue 3.0.0

Hi @shirtguy72,

Thanks for reporting this issue and sorry to hear you’re having this problem. The folders have been changed to buttons so it’s expected that a URL won’t appear in the lower left corner. That’s strange though that they’re not clickable.

Would it be possible for you to try some things?

1. Open the WordPress admin in a new browser window using incognito/private browsing mode to see if that changes anything
2. If not, would it be possible to temporarily deactivate all other plugins to see if the issue goes away?

Yes of course, but before I begin, get caught up, find the time… Now reading your changelog mentioning new REST API and floating Icon, I see no Icon floating…

Would the developer mind testing compatibility with two Jeff Starr plugins I am currently running? (I have really high traffic right now and cannot risk letting these visitors catching me with some/most plugins disabled)

Disable Gutenberg and Disable WP REST API

Thanks @shirtguy72. I tried both of those plugins and can’t seem to reproduce the issue so it doesn’t appear to be a conflict with one of those plugins.

Given that you’re not seeing the floating folder icon, I’m wondering if perhaps it’s a caching issue with some of the plugin’s scripts/CSS. You may want to try doing a hard refresh while on the admin/edit.php page to see if that changes anything.

The conflict is actually with another Jeff Starr plugin, [BBQ Firewall] I am using the Pro version, for which I have disabled it’s “Custom Rules” AKA my own set / added firewall rules, but still conflicts….Both his free and paid versions are based on his 7G and 8G firewalls. — With the firewall disabled, folders are clickable and I do see the floating icon.

Now, I’ll beg the developer to kindly see if you can see and or determine if there is a conflict with the free version of BBQ on the repository.

https:// wordpress. org/plugins/block-bad-queries/

@specialk , hope you could also take a look and possibly work along with @wickedplugins to remedy? [Advanced Rules are enabled in BBQP]

@shirtguy72 Glad to help, just need the basic steps to repeat the issue on default WordPress install.

Sure @specialk, thanks.

Well, I guess you would have to install Wicked Folders, have a few dummy posts, add a few folders, assign one of each post to a folder, and try viewing the list view of posts assigned to a certain folder by clicking the Folders themselves, with BBQ Pro Basic and Advanced enabled, Wicked version 3.0.0 will not allow these links/folders clickable, rolling back Wicked to previous version 2.18.19 and the issue goes away. Hope that helps, not sure else how to explain it.

Oh, in addition: latest version of wicked does not let wp display url of these folders on hover, as in where wp shows us posts ID’s

https://prnt.sc/Zfoc6rnxkQm_

@shirtguy72 So this is for the pro version of BBQ, correct?

• This reply was modified 9 months ago by Jeff Starr.

Correct, Pro

Okay thanks. The forum rules here prohibit any discussion/support of pro plugins (it’s for free versions only). I am still glad to help but you’ll need to reach me via email.

Understood, didn’t think of that.

@specialk, I’ve done some troubleshooting and believe I’ve found the exact query string pattern blocking Wicked, this pattern may also be part of BBQ Free, thus within the rules? Kindly see screen capture … https://prnt.sc/iaLjIyVRFSg2

[RESOLVED] — I can simply whitelist my own IP Address in BBQ when I need to use the Folders functionality of Wicked Folders. For when my screen capture self destructs, as it will, I’m including the query string pattern that impedes the folders being clickable hopefully that can help anyone else who may be running into any firewall issues with any other security plugin….

This Query String Pattern—-> \

Glad you got it sorted @shirtguy72, thanks for reporting.

Glad you got it resolved @shirtguy72. Makes sense that it was getting blocked due to the “\” as it makes requests like edit.php?post_type=page&wicked_page_folder_filter=43&paged=1&folder_type=Wicked_Folders\Term_Folder.

Thanks for your help also @specialk!