https://github.com/LimeSurvey/LimeSurvey/pull/2151

First of - in a broader view I think each question template view should have access to relevant question attributes.

Yes : just add a function for this ? No ?
https://bugs.limesurvey.org/view.php?id=14228
https://bugs.limesurvey.org/view.php?id=14248

Else we do again and again same code …

I am quoting you from 15814 : "14228 is better , but more time to do ?" :)

what is the status of 14228?

It's just life, I need the is_numeric in short free text and it just seems more realistic to get that in a realistic time frame than realizing the whole concept of getting similar data for all questions. Surely this would be better, no question. What I did was a small addition to the current not ideal solution to have a quick result.

@tpartner seems to prefer an array … then need to update each question type ?

And here : you update qanda, but qanda is deprecated …
Did you test if it waork in 5.X : https://github.com/LimeSurvey/LimeSurvey/tree/master/application/core/QuestionTypes/ShortFreeText

With a new twig function : no need to update all question type …

Hi All,

Is this usefull?

In the questions theme, the array question_template_attribute is available.
That allows to pickup attributes.

Are you saying that the std attributes are not available while custom are?
Is that the issue? Maybe it is a bug instead of a Feature Request?

Thanks!

image.png (25,820 bytes)   

image.png (25,820 bytes)   

image-2.png (9,451 bytes)   

image-2.png (9,451 bytes)   

This is a bug.
The config.xml file for base question types are not being found as these are only searched in user themes folder and "core" themes folder.

Initially, we believe that standard question types folder should also be added as a place where to lookup for config.xml files.
Still, that may be only part of the solution, not sure if all.

Thanks!

@ollehar let me know if I should take this or not.

Hm, Ahmed already closed the PR tho?

@gabrieljenik Seems like we have a couple of issues with higher priority right now

Since we won't be merging partial fix, I am closing the ticket. Already picked another report which addresses this issue in the fix.