This sounds like you used a property to fake-hide an input field.
IMHO this rather should be a new input type like 'hidden', or: if the input type also is related to value validation rather an additional attribute property named "hidden".

Yes, I used the only way that I know to hide the attribute. It was suggested by Louis. It is definitely sub-optimal as the parent divs and sibling labels are still rendered.

If there is better way I would be happy to test. Documentation is extremely limited.

I would love to see a "hidden" attribute property.

...also, a method to hide entire categories would be cool. For example, I often use multiple-numerics without sliders or to render my own custom sliders so would like to hide the entire "Slider" category.

So what you want, tpartner, is to apply custom CSS to the question editor for a certain question theme?

Maybe we should add a feature to include custom JS that is loaded when a question theme is loaded in question editor? Then you could change the appearance anyhow you want.

So what you want, tpartner, is to apply custom CSS to the question editor for a certain question theme?

Not oinly CSS : just don't send HTML

See

It is definitely sub-optimal as the parent divs and sibling labels are still rendered.

Yes, loading custom JS and CSS when viewing/editing the custom question theme would do the trick, providing we could still set defaults for any attributes hidden with that JS/CSS.

In my opinion :

1. Need a core way to hide (mean not render and didn't update keep value)
2. Need a solution to add custom css and js

With custom css and js : you can hack, but still an hack. To hide other label :

('#general-setting-help-other_replace_text").closest('.form-row').hide()… and in 4.5.0 : it don't work …

Good point, Denis. Using element id is not stable long-term. A new XML tag, then, maybe? For <show>1</show>

<attribute>
  bla bla bla
  <show>1</show>
</attribute>

?

Good lord, Mantis is stupid with HTML tags...

A new XML tag, then, maybe? For <show>1</show>

Yes! :)

...and JS and CSS so I can hide entire group elements?

Let's create a new ticker for JS/CSS support. I'm not sure how to apply CSS dynamically. JS is no problem.

Thanks Olle.

• https://bugs.limesurvey.org/view.php?id=17006

@tpartner : this mantis issue have a parent ?
We already discuss some month/year ago on the way to hide specific attribute , no ?

@tpartner : this mantis issue have a parent ?
We already discuss some month/year ago on the way to hide specific attribute , no ?

Yeah, we did discuss it - https://bugs.limesurvey.org/view.php?id=14185

In my opinion, it was never resolved satisfactorily, or if it was, I can't find any documentation.

In my opinion, it was never resolved satisfactorily, or if it was, I can't find any documentation.

Did you try in <visible>0</visible> in QuestionTheme config ?

Didn't work in 3.25.8 add input in a "model"

Updated version of autoComplete …

The visible property seems to work in 3.x but when using it in Version 4.4.0-RC4, the default property still does not work.

Just to sum it up:

The property "visible" is used to hide attributes in the UI, but you want still use the property itself with a default value.

This works in 3.x (hide + default value)

In LS4 the default value does not work.

Correct?

3.x:

• Using <inputtype></inputtype>, the attribute is hidden in the back end and the default value is respected in the front end.

4.x:

• Using <inputtype></inputtype> , the attribute is hidden in the back end but the default value is not respected in the front end.
• Using <visible>0</visible> has no effect.

16124_3.png (17,774 bytes)   

16124_3.png (17,774 bytes)   

16124_2.png (37,208 bytes)   

16124_2.png (37,208 bytes)   

16124_1.png (33,767 bytes)   

16124_1.png (33,767 bytes)   

Thank you for the clarification.