Conversation
supportWonderful plugin and I’ve been using it without issue for years. I just realized you had a pro version. I updated to the latest version today and my Page Hierarchy is no longer working. It’s just empty. Dynamic folders successfully parses by date and author, but Page Hierarchy is what I use and love. Not seeing any errors or anything until I try to create a folder manually then i get “The response is not a valid JSON response.” with POST https://<website root>/wp-json/wicked-folders/v1/folders?_locale=user 403 (Forbidden) in the console Only update made was this plugin. Tried deleting and reinstalling plugin. Tried disabling cache and all other plugins. No luck, I’m puzzled. WordPress 6.3.3, Server running PHP version: 8.2.16 .
Hi @mconheady , Thanks for using the plugin and for reporting this issue. The new version of the plugin uses a REST API and I’m wondering if perhaps there may be a security plugin blocking the requests. Do you have any security plugins (or a plugin that disabled the WordPress REST API) installed? If so, can you try temporarily deactivating them to see if the issue goes away to help narrow down the issue?
You are wonderful! Turns out it was The WP Cearfy plugin. They used to have a REST blocker as a feature. Then removed it as a feature, apparently not disabling it for those that had it enabled. Disabling that plugin still kept it enabled, which was the source of the puzzlement. I had to purge all their settings to actually get that feature removed. Thank you so much and I’ll be going pro soon!
Great, thanks for the follow-up and glad to hear you were able to resolve it!
Hi @mconheady , Thanks for using the plugin and for reporting this issue. The new version of the plugin uses a REST API and I’m wondering if perhaps there may be a security plugin blocking the requests. Do you have any security plugins (or a plugin that disabled the WordPress REST API) installed? If so, can you try temporarily deactivating them to see if the issue goes away to help narrow down the issue?
You are wonderful! Turns out it was The WP Cearfy plugin. They used to have a REST blocker as a feature. Then removed it as a feature, apparently not disabling it for those that had it enabled. Disabling that plugin still kept it enabled, which was the source of the puzzlement. I had to purge all their settings to actually get that feature removed. Thank you so much and I’ll be going pro soon!
Great, thanks for the follow-up and glad to hear you were able to resolve it!