This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.
Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.
No supporters are available to work today on Toolset forum. Feel free to create tickets and we will handle it as soon as we are online. Thank you for your understanding.
| Sun | Mon | Tue | Wed | Thu | Fri | Sat |
|---|---|---|---|---|---|---|
| 8:00 – 12:00 | 8:00 – 12:00 | 8:00 – 12:00 | 8:00 – 12:00 | 8:00 – 12:00 | - | - |
| 13:00 – 17:00 | 13:00 – 17:00 | 13:00 – 17:00 | 13:00 – 17:00 | 13:00 – 17:00 | - | - |
Supporter timezone: America/New_York (GMT-04:00)
This topic contains 6 replies, has 3 voices.
Last updated by bryan 2 years, 11 months ago.
Assisted by: Christian Cox.
Hi, you are correct in that there is no "form" type custom field in Types, but you can insert a Toolset Form in a WYSIWYG or multiline text custom field using a shortcode, then implement that custom field elsewhere on the site in a dynamic way. Insert a Form by title like so:
[cred_form form="Your Form Title"]
The Forms shortcode documentation has details about the syntax and other implementation variations:
https://toolset.com/documentation/programmer-reference/forms/cred-shortcodes/
If you explain a bit more about what you mean by a context-aware form, I might be able to provide some additional guidance. For example, you can use generic hidden fields in Forms to capture the post ID of the post where the Form is displayed. That's one way Forms can provide access to the context in which the Form was submitted. That contextual information could then be available in an email notification for this Form, or in a Forms API callback for this Form submission, etc. I'd need more information about what exactly you want to accomplish to be able to give you better advice here.
Another way would be to implement a post relationship between the post type created by the Form and the post type of the post or page where the Form is displayed. For example, say the Form is displayed in the template for post type "A" and is configured to create posts in post type "B". If you have a one-to-many (O2M) post relationship set up between CPT A (parent) and CPT B (child), then you can configure the Form to create child posts by automatically linking the new post being created and the post where the Form is displayed, in this O2M relationship. You can enable this automation by either using the "Create child post link" feature, or by applying specific settings in the child post Form. The "Create child post link" is simpler to implement, but the workflow requires you to display the child post Form on a page that is separate from the parent post. This feature is described in the doc here: https://toolset.com/course-lesson/selecting-parent-posts-when-using-forms-to-create-child-items/
In an alternate child post creation workflow, the child post Form is displayed directly in the parent post template. This setup requires a bit of code in the Form's relationship field configurations. Set the default value of this field using a post ID shortcode, pointing at the current page as the source of the post ID. This shortcode will produce the ID of the post where the Form is being displayed, so adding it as the default value of the post relationship field will result in the current page being selected as parent automatically.
[wpv-post-id item="$current_page"]
Screenshot attached here showing this configuration in the Form builder. You can also add some custom CSS in this case if you want to hide the relationship select field for a more intuitive experience. See our documentation about this shortcode and the "item" attribute:
https://toolset.com/documentation/programmer-reference/views/views-shortcodes/#wpv-post-id
https://toolset.com/documentation/programmer-reference/views/views-shortcodes/item-attribute/
Christian,
thanks you explanation made me realise I was taking the long way and so I simply added
[tb-calendar coworker="[wpv-post-author format='meta' meta='ID']
as a single line custom field default value, then added the single field using blocks and an additional kadence tab.
It works well where the Post author = the person being 'booked'.
tb-calendar just an example I use, I imagine any booking plugin which can accept the author ID as a parameter to map the bookable person could use this method.
thanks again
