Some things on LimeSurvey are set to general options that effect all surveys while some are set to options custom to each survey.

It looks like the page that notifies respondents that a "survey is not active" (i.e. when it is no longer accepting respondents) falls under the 'general options' in that it gives a basic statement of "This survey is currently not active" (or something similar) that is shared across all surveys.

Is it possible to make this 'survey is not active' page to be customized for each survey?

For instance, if could be a survey about hamburgers it would bring up a picture of a hamburger and say, "the hamburger survey is no longer active" .... AND ... a survey about hotdogs that would bring up a picture of a hotdog and say, "the hotdog survey is no longer active"

As far as I know this is not possible at the moment. I can see the value of it: please make a feature request at: www.limesurvey.org/community-services/feature-requests

Or maybe DenisChenu has/knows/develops a plugin?

Tammo

You could add something like this to template.js (modify "keyWord" for different activation states or languages):

tammo wrote: As far as I know this is not possible at the moment. I can see the value of it: please make a feature request

With a broader scope in mind (and a few years old):
www.limesurvey.org/forum/future-features...tallation-per-survey
bugs.limesurvey.org/view.php?id=10038

It's in survey runtime helper:
github.com/LimeSurvey/LimeSurvey/blob/ma...timeHelper.php#L1403

If it's something urgent, I can move that code to a view, so you can overwrite it in your template.

That is dangerous to ask: "if it's something urgent...."....

Requests are always urgent, but are they important?

99u.com/workbook/25721/urgent-vs-important

I would say that this is important, but not urgent. That is my way of getting it higher on the priorities list. But stick to your list!

Tammo

I mean it would take me 15 minutes to do.

Well, I'll take the bait. If you can do it that fast: let's make it urgent then..



Tammo

BTW: it is always good to have a nice new feature in a new release, it makes upgrading/updating worth the trouble!

Tammo

You're going to have a really nice new feature in LS3. We're moving the template view override to a real question template engine: each question could have their own specific template (selected in Display settings). So, it will be very easy to share zip files containing HTML, JS and CSS for custom question types, and with custom question attributes if needed (basically: any old "workaround" could be distributed as question templates).

Btw, long time I didn't spoke with you: You'll be glad to know that Twig engine is integrated for question views and survey templates. So, instead of using keywords in pstpl files, now you can for exemple do something like: {{ aSurveyInfo.adminemail }}. We need to think about what variables should be available from pstpl files (my bet: $oSurvey, $oQuestionGroup, $oQuestion and $oToken)

I'll do the subtemplating engine in January, should be very easy.

Looking forward to you saying: let's test this!

Tammo

It would be fantastic if this can be made to work.

The only reason I have not offered to do it myself is I am not a programmer.

Thanks.