Problem: What will happen if I change the slug of a custom post type?
Solution:
1. The posts you have already created in this post type will not be lost. They will be migrated into the new post type automatically.
2. Any hard-coded links that were already created using the old slug must be updated.
3. Any post relationships for posts in this post type will be saved in the database, but you must to update any related post types in Toolset > Post Types to restore those relationships.
4. Any shortcodes you have placed that implement your post type slug must be updated. This includes Filter Controls, Loop Output contents, shortcodes placed in post content, conditionals, etc. These will not be automatically migrated for you.
5. Any custom code you have added to a functions.php file must be updated to use the new slug.
6. Any ancestor references using the "$slug" operator must be updated to use the new slug.
7. Any View or WordPress Archive that included the old post type must be resaved, since the old post type no longer exists. You must check the post type again.
8. Related taxonomies and custom fields must be resaved to point to the new slug.
...these are the top things that come to mind. You should always make a backup of your site before attempting this kind of change.
Problem: Will a future release of CRED allow me to edit parent and child posts in a single form?
Solution: Yes, the plan is to update CRED to allow editing child posts while editing their parent post, in a single form. This feature is under development, and you can follow our blog to get the most timely updates about this CRED update.
Problem:
How can I make sure that only the Author of a post can edit that post with the CRED Form I created for this purpose?
Solution:
This is done by setting the correct capability in Access > CRED forms > Edit Posts with (CRED Form)
You will set the capability for "Edit Own your_post_type with CRED Form "your_form"
This setting allows only the selected Roles to edit their own (and only their own) Posts with CRED.
We document known issues and their solutions in Toolset errata. Save time by checking there first and seeing if what you are facing is a known issue. This list is kept short. We do our best to resolve all known issues with every release of Toolset plugins.
Support Policy
Toolset staff will help you use the Toolset plugins correctly, provide any information you need, help troubleshoot problems and advice on best-practices.
Please make sure to issue only one topic per each support ticket.
