Apply conditions in Toolset Forms

Dieser Thread wurde gelöst. Hier ist eine Beschreibung des Problems und der Lösung.

Problem:
How can we apply conditionals in a Toolset Form so to hide single form fields depending on other fields values (in the form)?

Solution:
You can wrap any field in Forms into so called "Conditional Groups".
They will allow you to listen to particular other fields present in the form, inclusive generic fields
To edit such conditions or their content more advanced you need to turn on "Expert Mode" for the editor.

Relevant Documentation:
https://toolset.com/documentation/user-guides/conditional-display-for-form-inputs/

This support ticket is created vor 5 Jahren, 10 Monaten. There's a good chance that you are reading advice that it now obsolete.

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.

Dieses Thema wurde abgetrennt von https://toolset.com/de/forums/topic/permission-denied-for-editing-forms/

Sun	Mon	Tue	Wed	Thu	Fri	Sat
-	-	14:00 – 20:00	14:00 – 20:00	14:00 – 20:00	14:00 – 20:00	14:00 – 20:00
-	-	-	-	-	-	-

Supporter timezone: Asia/Ho_Chi_Minh (GMT+07:00)

Tags: Access plugin, Controlling access to content editing

Dieses Thema enthält 4 Antworten, hat 2 Stimmen.

Zuletzt aktualisiert von FelipeP5703 vor 5 Jahren, 10 Monaten.

Assistiert von: Beda.

Author

Artikel

März 28, 2019 at 7:42 am #1222210

FelipeP5703

I set a conditional display which is not working. On the editing form I put a conditional output to show or hide the feature image and the extra photos the client wants to change IF the field for allowing the client to change the pictures would be yes. (See images). The field to allow/disallowed is in the dashboard and not in the form. I want to allow some users to change their pictures and other to not change it, how do I do that?

März 28, 2019 at 7:48 am #1222211

Beda

Forms conditionals do not listen to the Post but only to the Form
You could for example (on an edit form) include the Field that saves 1 or 2 (yes or no) but hide it with CSS for example.
Then the condition will have something to listen to.

However, you will need to enable Advanced Mode in the Form builder to hide the field as there is no way to add CSS or ID's to the single fields and hide them. This, if you cannot address the field with Custom CSS in the CSS editor (which should work, as the Field already will have an ID generated by Forms, but it lets you less customization options in particular)

Please submit a suggestion here to allow full control of the HTML (ID, Class) of fields int he DnD (Drag and Drop) editor:
https://toolset.com/home/contact-us/suggest-a-new-feature-for-toolset/
This then would allow to edit these aspects even without advanced/expert mode of the Form

März 28, 2019 at 2:09 pm #1222446

FelipeP5703

That worked! Thank you!

Btw, so I'm doing it correctly. I actually need a page for the editing form correct?

My confusion is this. If I don't have a page for the editing form, will the client be able to edit their Ad (custom post) by just clicking the editing button on My Account (Minha Conta) page?

Or the editing form page is needed for that?

März 29, 2019 at 8:05 am #1222896

Beda

The editing Form usually is in the Post it edits, but of course, an Edit Form can also edit *any* post, as long you pass that post to the Form (by ShortCode attribute or by directing to it from a given page with an edit link)

So, for example, you can have a list of "edit links" leading to the Post to be edited.
Or you can have a Page, with one form that edits the posts as set in the URL parameter.

If you need more assistance with this, please open a new topic so we can focus on it.

Thanks!

März 29, 2019 at 2:50 pm #1223092

FelipeP5703

My issue is resolved now. Thank you!