A customer (Dutch workers union FNV Bondgenoten) was not satisfied with the available templates in LimeSurvey, so we designed one for them.

We started with the few question types that they wanted to use in their surveys and later started to diverge.

We are currently at a stage where we want to share this work in progress with the community.

If you are interested, please download the attached template and test it and give us feedback. We will work on this freely downloadable template whenever we have the time for that and when we see the need for our use cases.

The basic template will remain free, we are of course for hire for special needs.

The template as is has at least the following requirements and know shortcomings:

• only usable for LimeSurvey 2.0 and up
• not usable in Internet Explorer 8.0 and lower
• not all questions types have been implemented
• ... please tell us

We are Tools for Research, a small Dutch organisation that provides support for research oriented organisations. We develop in Drupal, LimeSurvey and some other PHP-based open source platforms.

An example of our work: demo.gewoongoedwerkmeter.nl (sorry in Dutch only), which presents you with a (still LS 1.92 based) survey and a custom made report at the end.

Thanks for sharing your template. Maybe you can outline the biggest problems you faced when creating a Bootstrap version of a Limesurvey template?

Which question types are not supported yet?

What has been tested to work:

• short free text
• long free text
• date/time (styling for time not yet done)
• yes/no
• gender
• multiple choice
• Array (5 point choice)
• List (dropdown)
• List (radio)
• List with comment
• Array (still missing hover over row)
• Array by column (still missing hover over column)
• Multiple numerical input
• Multiple numerical input (slider)
• Ranking

Other questions have not been tested yet.

We will come up with a report on what were challenges. Our developers complained a bit about inconsistent coding in Limesurvey sources, they then used javascript to alter placing of classes etc.. The main coders are on holiday now, will be back in three weeks.

We have greatly improved the template.
In IE8 it will look less good, but it will still be usable.

Please let us know of any found issues. We may not be able to address all issues, though, but we will certainly look at it.

Tammo ter Hark
Tools for Research
www.toolsforresearch.com

Hi!

Tried to install this template and I get the following error message:

I have not seen this message before. What version of LS are you using?

And where did you put the template? We put it in upload/templates

The name of the theme ( in my installation) is tfr

Tammo

Latest install. Version 2.05+ Build 141113.

I have seen a similar complaint last week for a bootstrap based template and I tested it with the skeleton template from Denis and a similar error message appears. might be a bug in the latest version of LS.

Currently checking.

Glad I did not update yet

Tammo

I just tested your demo at demo.gewoongoedwerkmeter.nl/ and there are two slashes top right, probably some left over comment or the like at the .pstpl file:

It also looks like your template.js file is placed at a subfolder of the template ("/js", see screenshot above) which can cause the problem mentioned earlier.

We will get rid of the // of course.
We hope to have the flexibility to pput files in another location than the root of the template, we think that the current way of putting all files together, is a bit messy.

Since the previous release we added support for the slider question and the double array.

Hey tammo, first of all, thanks for the great work!


By uploading the template unsing the buildin limesurvey upload function, I noticed, that the fonts directory was not uploaded although the import log says so. Adding the missing files by ftp solves the problem and the template workes fine. But I think, this is not the way, the upload is intended to work.





Does anyone else discoverd this problem? Does limesurvey block upload of specific file types?



By checking missing files I noticed that the template tries to use a temp.css, but the file is not included in the template. Maybe some left over from testing?