@LouisGac : any project to allow twig file from plugin ? Something like :
F

Exemple here:
find register_form_plugin in template, if not => Mother template , If not => Plugin template
Something like that

sure could be easy to do

If i remind i spoke for "core twig" file ?
Currently : vanilla is the mother/grand-mother of all plugin, then core == vanilla.

But what happen when another user create a mother/grand-mother plugin ?
We can not add twig file ?

Maybe move vanilla to "If mother/grand-mother AND grand-grand-mother" don't have this twig file : get it in vanilla ?

have a look to the question template rendering process:
https://github.com/LimeSurvey/LimeSurvey/blob/master/application/core/LSETwigViewRenderer.php#L84

it doesn't depend on survey themes, nor on inheritance system

but maybe you want an inheritance system for plugin?

Yes : there are a way for Question, but plugin can not use Question ?

Maybe allow another alias in renderTemplateFromFile ?
Because renderTemplateFromFile get only via Template

Question do : get it in current template and mother template, if don't have => get from Question::Template get core views, die if no view

But all other part do : get it in current template and mother template, die if no file

I like to have a solution for any file (even if not by plugin)

For example : we add in core a new System : didn't know , say "Last Correction before Validate" using twig view in vanilla. If User template are no a child of Vanilla : what happen ?

Have a a renderPluginView is great, but didn't fix "When core add file to vanilla : what happen to other" ?
:)

"I like to have a solution for any file (even if not by plugin)"

sure

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

\o/

Release 3.14.2+180807