Hi everyone,


we could like to upgrade from 2.56.1 to 3.15.5 via the ComfortUpdate.
We have ~80 finished surveys and ~10 live ones. Some of them use very light,
only few lines, of modification in already existing templates.

How save will the transition be, considering having live surveys?

Thank you
fu

limesurveyfu1 wrote: only few lines, of modification in already existing templates.

Yoir old template are directly disable, you need to make new ones.

limesurveyfu1 wrote: How save will the transition be, considering having live surveys?

Too many things we don't know to answer (server size, memory etc … DB type, size and memory …, survey size etc …)

But if there are no issue : less than 5 minutes.

I personally would not run an update from 2.x to 3.x with live surveys, at least not with thorough testing in a parallel test installation with these surveys.

As Denis says, the template from one won't work in the other.

I personally would probably run a parallel installation with the new version and start all new surveys in the new installation, but let the old surveys run out in the old installation.

Updating to a major new version with live surveys is always risky. As Denis says, in theory the update is "quick and easy". But you know Murphy's law...

I would at least run a parallel test installation to check if all live surveys still work. You can create a copy of your database and install 3.x on top of that and see how the current surveys behave and if they are working well. Then you can adapt your templates/themes to your needs. Then, if everything works on the test environment as it should, you can run an update on your production server and copy your templates over to the production server.

Thank you both very much for your quick and thorough answers.
I agree. The best solution would be a parallel installation and let the old one slowly retire.


Thanks again
fu

holch wrote: I personally would not run an update from 2.x to 3.x with live surveys, at least not with thorough testing in a parallel test installation with these surveys. …

General situation.

1. Do a bakcup
2. Do another backup
3. Test on a test server
4. Test on a prepoduction server
5. Test all survey‘s
6. Do a backup
7. Do a backup
8. Update on production
9. Test all survey‘s
10. Do a backup

Theory:

General situation.

1. Do a bakcup
2. Do another backup
3. Test on a test server
4. Test on a prepoduction server
5. Test all survey‘s
6. Do a backup
7. Do a backup
8. Update on production
9. Test all survey‘s
10. Do a backup

Practice:
1. I should do a backup, but - a lot of work. What could go wrong? Naa, we'll be fine.
2. I should be testing this before, but - a lot of work. What could go wrong? Naa, we'll be fine.
3. Update directly on production without backup and testing
4. WAAAAAAAAAAAAAAAAAAAAA
5. Dear forum, I need help urgently...
6. Crying, shouting, heads rolling...

holch wrote: 3. Update directly on production without backup and testing
4. WAAAAAAAAAAAAAAAAAAAAA
6. Crying, shouting, heads rolling...

I do this a lot …