?
avatar N6REJ
N6REJ
27 Feb 2016

Steps to reproduce the issue

Currently if your using a repeatable formfield there is an entire fieldset that is hidden unless the
formfield meets its condition. So its easily possible to turn and repeatable completely on/off based on user inputs.

Expected result

It would be useful if there was a "conditional" formfield where much like the repeatable your able to hide an entire fieldset. This could also have a "modal" param much like showon where if it was active would display this sub-fieldset in a modal and where if not would just display it like normal.

Actual result

Currently not possible

System information (as much as possible)

Additional comments

This would be useful where there is a large group of parameters that don't make sense to display unless some other condition has been met.

avatar N6REJ N6REJ - open - 27 Feb 2016
avatar brianteeman brianteeman - change - 29 Feb 2016
Labels Added: ?
avatar brianteeman brianteeman - change - 10 Mar 2016
Category Fields
avatar brianteeman
brianteeman - comment - 8 May 2016

I would say that if you want this as a modal then you can already use the repeatable field or the newly proposed subform and if you want them to be displayed as a group in the main body then you can already do this with the showon as can be seen in global configuration and most component options now.


This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/9236.

avatar brianteeman brianteeman - close - 8 May 2016
avatar brianteeman brianteeman - change - 8 May 2016
Status New Closed
Closed_Date 0000-00-00 00:00:00 2016-05-08 13:17:47
Closed_By brianteeman
avatar brianteeman brianteeman - close - 8 May 2016
avatar N6REJ
N6REJ - comment - 12 May 2016

neither of those will let you simply turn on / off entire fieldsets.. showon doesn't work for fieldsets, and repeatable creates a view therefore it's its own fieldset.

avatar Bakual
Bakual - comment - 12 May 2016

showon doesn't work for fieldsets

It works for fieldsets in the component config: #9668
If it's in the extension itself, you need to adjust the extension code to support it.

Add a Comment

Login with GitHub to post a comment