Problem: I would like to get the parent post Course of the current post Product using the new Post Relationships API, but it doesn't seem to be working. I have tried both of these syntaxes:
Solution: In this case, the relationships were created in the new system, so toolset_get_parent_post_by_type is not appropriate. The toolset_get_parent_post_by_type API is intended for use with legacy relationships, or relationships that were migrated from the legacy system. When specifying the relationship to query, the array syntax is intended for legacy relationships as well. The best approach in this case is to use the toolset_get_related_posts API, and the relationship slug instead of the post type slug array:
Problem: I'm having a couple of problems in CRED:
- Placeholder text is not shown
- The select_text attribute does not work
Solution: The select_text attribute is a known issue and will be resolved in CRED 2.0. Placeholders should be added to CRED form fields using the placeholder attribute.
Problem:
Client is using the cred_success_redirect API hook for a custom redirect on certain forms, but it is breaking the redirect on all other forms.
Solution:
There was an error in the client code shown below. A filter must always return the first argument.
The issue here is that the user is unable to submit their edit post form because of a required image field. Even though the image is already in that field.
How can I make sure that users who submit my Toolset Forms really submit the required data?
I see no way to stop the form from submitting if not all data is completed.
Solution
You can make each field required when you set them up or edit them in Toolset > Custom Fields
As well generic Toolset form Fields can be set as required.
When this is set, a little asterisk will appear next to its label and the form cannot be submitted without any value in them.
The issue here is that the user created an additional post but that new post was not showing up in his view that was created.
Solution:
In this case it was caused by caching. If your website is caching the information then you may need to clear the cache for the new post to start displaying on the frontend in views.
Problem:
Can I disable or hide the Submit button in a CRED form by conditions?
Solution:
Yes, you use CRED Conditional Fields.
Let me put a code example below with 2 fields.
If none is filled, you cannot submit the form and a message will tell you what is wrong.
If at least one field is filled, you may submit the form.
[cred_show_group if="($(first-field) eq '' ) AND ($(second-field) eq '' )" mode='fade-slide']
You need to fill at least... xy fileds... to submit the form
[/cred_show_group]
[cred_show_group if="($(first-field) ne '' ) OR ($(second-field) ne '' )" mode='fade-slide']
[cred_field field='form_submit' value='Submit' urlparam='' class='btn btn-primary btn-lg' output='bootstrap']
[/cred_show_group]
With this, if no field is filled, the Form cannot be submitted and a message is displayed.
If at least one field is filled, you can submit the form and the message disappears.
And, the best is, this all happens before the user even needs to submit the form.
En Toolset erratas, documentamos problemas conocidos y sus soluciones. Ahorre tiempo consultando allí primero y viendo si el suyo es un problema conocido. Mantenemos la lista corta. Hacemos lo mejor que podemos para resolver todos los problemas conocidos con cada lanzamiento de los plugines de Toolset.
Política de soporte
Nuestro personal le ayudará a usar los plugines de Toolset correctamente, le proporcionará la información que necesite, le ayudará a resolver problemas y lo asesorará con respecto a las mejores prácticas.
Sírvase asegurarse de incluir solamente un tema en cada solicitud de soporte.
