Examine having inter field dependencies (hiding fields) (this can be combined with the existing cascade feature)

[ldoliv]

Hello,
In a fieldgroup I have a dropdown select "Option A" and "Option B".
I also have other fields, example: title and subtitle.

Would it be possible and easy to implment the functionality?
When choosing "Option A" show both title and subtitle fields.
When choosing "Option B" only show the title field.

The subtitle field could still be saved when article form submit, that depends on how you would implement this.
To me important is to hide "subtitle" field when selecting "Option B" from the dropdown.

[ggppdk]

• for questions or discussing new features, please use our forums first

the idea you suggest would be done by adding this feature to 6 fields:
select(multiple), radio(image), checkbox(image)

• which already have "cascading" feature

Because this is similar and related to cascade feature

will need

• the JS code for item form to handle form changing events
  (similar to what we have now)
• plus the initialization on item form load (PHP) to parse the show-hide configuration,
  (this should be a configuration that is flexible enough ...)
• just unlike cascade feature, we do not need to do AJAX server calls and have server task

In order to be complete, it should be as above,
this may have to wait to be done properly and not do a quick hack

• for your case you can simple add some JS code to your form that will attach to fields' onchange event and hide show the container of the desirable fields, so you do not have wait for this to be implemented

[ldoliv]

Ok, I will add the js to the form. Thank you for considering this feature. Good work!

[ggppdk]

e.g. see this:
http://stackoverflow.com/questions/31407977/hide-element-based-on-value-of-other-elements

• the needed JS code should be small, and our fields have unique id in their top level containers (item form)
  e.g. container_fcfield_27

[ggppdk]

Also we have parameters for JS code inside the backend type form, that will be added only when the particular type is being edited

[ldoliv]

I'll see how it goes and report back. :)

[ldoliv]

I managed to do it, I would like to send you my code, can I send to your email ?

[ggppdk]

hello,

you don't need to send, basic code do this is trivial

• and we are doing it already in parameters dependencies, in much more complex way (see the date scope in universal module) and in other places
• to do this with proper and handle all cases is more work, e.g. it will be multi-level

will do this in proper time

[ldoliv]

ok, thanks anyway.

[ggppdk]

Your feature request is quite useful,

• and a large number of users will find this useful, and will use it, if available
• this has been asked / suggested by others too

that is why it has 3.1.0 milestone

• just for general usage, it needs to be done properly
  because once we add a feature it is difficult to change it / improve it without breaking existing installations