wickedplugins

Hi @benbutler12!

Saving the folder name is handled in the ajax_save_folder() and ajax_edit_folder() functions within wicked-folders/lib/class-wicked-folders-ajax.php.

However, the plugin uses the built-in WordPress taxonomy API so, depending on what you want to do, I think you’ll actually want to use an action or filter called from either wp_insert_term() or wp_update_term().

Hope this helps! Let us know if we can answer any other questions.

• This reply was modified 7 years, 12 months ago by wickedplugins.

Hi @dineshsunny9,

We’ve released an update (2.9.1) that should resolve this issue for you. We changed the prefix of the folder taxonomy names to prevent them from exceeding 32 characters.

Let us know if you still have trouble after updating the plugin.

Thanks!

Thanks for the help @sc0ttkclark! Let me know if I can help with anything.

Thanks @dineshsunny9.

I’ve looked into this and I believe the issue has to do with how the Pods plugin registers the custom post types. From looking at the code, it appears that the custom post types are sometimes registered during the WordPress init action but, in other instances, the post types can be registered later in the process.

The Wicked Folders plugin registers the folder taxonomies during the init action. It appears that for whatever reason the Pods plugin may be behaving differently on your server instance and registering the post types after the init action. This prevents our plugin from attaching the folders to the post types (because the code to create the folder taxonomies has already run). This causes the “Invalid taxonomy” error that you are getting.

Unfortunately, the Pods plugin does not appear to expose an action that can be used to register the folders later in the process after Pods has registered the post types.

I will post a message on the Pods support forum to see what they recommend.

Are there any obvious differences you can think of between your local and server environments? E.g. different plugins, different theme, different plugin configuration/settings, etc.?

Thanks for the additional info.

Can you try going to Pods Admin > Settings in your server environment and clicking the “Clear Pods Cache” button to see if that makes a difference?

If not, are there any obvious differences you can think of between the local and server environments? Are the same exact post types registered in both environments or are there some differences? Are you using the name post, user, comment, taxonomy, settings or term for any of your post types?

Hi @dineshsunny9,

Sorry to hear you’re having trouble.

Can you confirm that you’re using the latest version of Wicked Folders?

How are you registering the custom post types? Did you write code to register them or are you using a plugin? Are there any plugins that are installed on the server that aren’t installed in your local environment?

Hi @troymedia,

Where are you seeing this error? In the admin or on the front-end? If you’re seeing it in the admin, what page are you seeing it on?

Does the site happen to communicate with other databases besides just the WordPress database?

Is the $table_prefix variable in the wp-config.php file for the site set to a54fT_6?

• This reply was modified 8 years ago by wickedplugins.
• This reply was modified 8 years ago by wickedplugins.

Hi @benbutler12,

Thanks for catching this. I looked into and it was a problem with the folder cache not properly clearing after a folder is renamed.

We’ve fixed the issue and it should no longer be a problem once you update to version 2.8.4.

Let us know if you still have trouble!