- Posts: 15
- Thank you received: 0
Ask the community, share ideas, and connect with other LimeSurvey users!
and thisrom wrote: (We are never using comfort update for $reasons)
match?We are willing to pay for this kind of support, like we already did back then for v2.06...
rom wrote: So what I get from your reply is, that it is indeed very possible that if a huge security issue might appear in the next few weeks, the only option for Limesurvey 2.7 users to fix that security hole is to upgrade to v3.1, as v2.7 will not get any further security fixes. This means all v2.7 users have now to hurry up to get their templates/modifications ready for an upgrade, and should upgrade in their production environment to v3.1 asap to receive further security updates.
Waiting for an official statement sounds strange to me, as v3.1 is already advertised as stable. So IF there is some kind of extended support for 2.7 there should have been an official statement already imho?
Regarding our approach to comfort update (totally offtopic): I am afraid you got me wrong here, we do not care about these few Euros ($reasons = php variable, not Dollar) and would be happy to give something back to the community/developers. We already donate some money when our reported Bugs get fixed, we payed for 2.06LTS and so on, so money is not an issue here. We are using the professional partner solely to design our template files, but we have no use for comfort update as we need to modify/add some code to Limesurvey with every update. We need some special text strings, so we modify the language files. We are doing these modifications since v1.x, and even created an updater bash script to automate the update process and implementing our modifications. In the past we already had some discussions with the limesurvey developers (Denis) and also opened up a feature request long time ago, but we had no luck so far.
Depending on thing that didn't work you might can wait forever. Themes and many workarounds won't will work after upgrading.Kevin wrote: I updated to LS 3 and had to put mine back to 2.67 because I could not get things to work in version 3. I'd wait a while for a more stable version.