Problem:
Client has a front-end form which uses cred_show_group to conditionally display a group of fields depending on the value of another field, and would like the same on the backend post edit screen.
Solution:
Individual Types fields can be conditionally displayed on post edit screens (which is also inherited in frontend Forms) based upon the value of another field. To conditionally display a group of fields simply apply the same rule to each of the fields.
Problem:
How to create a front-end Form for user's to edit posts?
Solution:
The Form itself is very much like a form to publish posts, and if you already have a form to publish posts you could duplicate it, then edit it and change the first setting that specifies it is to edit content.
The difference between post and edit forms is in how they are displayed.
The post forms can be inserted directly onto a page.
Edit forms need to be "hosted" inside a template, and then that template linked to.
If you are using Layouts, that would be a Template Layout (unassigned to any post type), and if you are not using Layouts, then that would be a Content Template (also unassigned to any post type).
Problem:
The issue here is that the user's redirect password link isn't working correctly.
Solution:
For this user they were working on their localhost and was causing and empty response in their browser. Which would be understandable since localhost sites are not normally public so the reset url they get wouldn't work.
The issue was resolved when the user placed the site on a live server.
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.
