View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|07541||Feature requests||Theme editor||public||2012-01-17 14:38||2015-06-16 09:15|
|Summary||07541: Each page an unique body class|
|Description||In some cases I want to switch design aspects on different pages. |
Currently this is only partly possible (by putting
div class="group GROUPNAME"
But sometimes a whole page needs another header, footer or color.
Giving each page an unique body class would make this possible. When each page is a group, it could be:
, this could even be an extra field on group definition pages, next to group name and group definition.
You could also do this on 1 question per page surveys.
|Additional Information||A possible solution: Put it somewhere in the code|
I do not have programming skills, I am just a user, doing some templating. I wish I could...
|Tags||No tags attached.|
Alternative solution: Need more input
Think of this idea: http://ideas.limesurvey.org/ideatorrent/idea/343/
Can combine the 2 idea:
- extra input for survey : put in body (startpage.pstl and other)
- extra inout for group : add GROUP_ID and GROUP_CLASS in startgroup.pstpl, groupdescription, question.pstpl
- extra input for each question : included in QUESTION_CLASS (question.pstpl)
If you put it in the template, it might put a lot of noise to the template, because each entry may be needed for one survey only. By adding a field to each survey, each group and each question, a field called "extra classes", you can target at the level you need.
An extra css per survey [sid].css might be called, from /upload/survey/[sid]
BTW: I cannot reach the link to ideas.limesurvey.org anymore. Where is that located nowadays?
idea is closed since more than one year, now we use mantis for Feature too.
Actually, i think a extra CSS by survey can be done in plugin. For ls3 : we work on Question plugin and maybe Group plugin.
Thank you Dennis. Is there a roadmap for LimeSurvey developments? Where would I be able to find that?
I did find: https://manual.limesurvey.org/LimeSurvey_roadmap but that seems to be updated in January 2013...
|Addition to earlier idea: please add the version numer and built number as body classes, so differences between versions can be styled: the most recent exchange of label and input in arrays is quite hard to target when you want a template to both work on 2.05 and 2.06|
@tammo : what difference between 2.05 and 2.06 ? I think it's more easily, but don't need a clean difference ?
PS: we need some class : save/reload/welcome/end/quotaend/error/survey ...
|2015-05-08 09:42||tammo||Note Added: 32132|
|2015-05-08 10:25||DenisChenu||Note Added: 32133|
|2015-05-08 10:41||tammo||Note Added: 32134|
|2015-06-15 12:16||tammo||Note Added: 32361|
|2015-06-16 09:15||DenisChenu||Note Added: 32377|
|2015-12-11 14:40||c_schmitz||Category||Templates => Theme editor|