Upgrading from a previous version - Revision history

C schmitz: Marked this version for translation

2024-11-18T16:08:59Z

Marked this version for translation

← Older revision		Revision as of 18:08, 18 November 2024
Line 12:		Line 12:
	If you don't know how to do this, you should not proceed further and ask someone who knows.		If you don't know how to do this, you should not proceed further and ask someone who knows.

	~~==Recommendation to use ComfortUpdate==~~ <!--T:28-->		<!--T:28-->
			==Recommendation to use ComfortUpdate==
	'''The easiest/safest way to upgrade is to use our [[ComfortUpdate]] service.'''		'''The easiest/safest way to upgrade is to use our [[ComfortUpdate]] service.'''

Line 21:		Line 22:
	</translate><translate>		</translate><translate>

			<!--T:37-->
	#Log out of the administration		#Log out of the administration
	#Backup your files and database		#Backup your files and database
Line 32:		Line 34:
	#Done!		#Done!

			<!--T:38-->
	<div class="simplebox">[[File:help.png]]'''Note:''' Between major versions (for example from version 3 to 4) the template/design themes change usually completely. Old survey design templates/themes will usually not work anymore.</div>		<div class="simplebox">[[File:help.png]]'''Note:''' Between major versions (for example from version 3 to 4) the template/design themes change usually completely. Old survey design templates/themes will usually not work anymore.</div>

Line 39:		Line 42:
	You can upgrade the database via the PHP CLI: <code>php application/commands/console.php updatedb</code>. This allows you to set up an auto-upgrade system via command line (for example, in a crontab), although it is not recommended.		You can upgrade the database via the PHP CLI: <code>php application/commands/console.php updatedb</code>. This allows you to set up an auto-upgrade system via command line (for example, in a crontab), although it is not recommended.

	= Failed database upgrade after manual update/ComfortUpdate= ~~<!--T:29-->~~		<!--T:29-->
			= Failed database upgrade after manual update/ComfortUpdate=
	Sometimes, even though you did everything correct, things don't work out they are supposed to during database upgrade.		Sometimes, even though you did everything correct, things don't work out they are supposed to during database upgrade.
	That may happen because of various reasons: Different database versions, unexpected data formats or contents, unusual configurations or anything else that did not show up in our tests (yes, we test a lot!)		That may happen because of various reasons: Different database versions, unexpected data formats or contents, unusual configurations or anything else that did not show up in our tests (yes, we test a lot!)

C schmitz at 16:08, 18 November 2024

2024-11-18T16:08:24Z

← Older revision		Revision as of 18:08, 18 November 2024
Line 18:		Line 18:

	<!--T:6-->		<!--T:6-->
	Please follow these ~~instructions~~:		Please follow these steps:
	*Log out of the administration		</translate><translate>
	*Backup your files and database
	*Delete all the old files/folders except for:
	**/application/config/security.php -'''Important!! This is the key to all encrypted data in LimeSurvey (version 4 and later)'''
	**/application/config/config.php;
	**/~~upload directory~~

	~~<!--T~~:~~27-->~~		#Log out of the administration
	~~<div class="simplebox">[[File:help~~.~~png]]~~'''~~Note:~~''' ~~If you have any customized templates in~~ /~~upload~~/~~templates, make sure you 'refresh' those with any changes that come with the new LimeSurvey version~~. The easiest way to check for such changes is to file-compare your old template with the new version of the default template. If you see any differences other than your customizations, a refresh is needed.</~~div>~~		#Backup your files and database
	*Copy the new files from the new LimeSurvey package to the existing location.		#Delete all the old files/folders except for:
	*Open the admin page in your browser (e.g. https://www.example.com/limesurvey/admin) ~~and check if~~ a database scheme upgrade is necessary.		##/application/config/security.php - '''Important!! This is the key to all encrypted data in LimeSurvey (version 4 and later)'''
	*After the upgrade: '''~~Clear your browser cache and cookies!~~'''		##/application/config/config.php;
			##/upload directory
			#Copy the new files from the new LimeSurvey package to the existing location.
			#Now clear your browser cache and cookies.
			#Open the admin page in your browser (e.g. https://www.example.com/limesurvey/admin). If a database scheme upgrade is necessary you will be prompted to confirm it.
			#Done!

			<div class="simplebox">[[File:help.png]]'''Note:''' Between major versions (for example from version 3 to 4) the template/design themes change usually completely. Old survey design templates/themes will usually not work anymore.</div>

	= Upgrading using CLI = <!--T:25-->		= Upgrading using CLI = <!--T:25-->

C schmitz: Added a step to log out

2024-11-18T16:01:35Z

Added a step to log out

← Older revision		Revision as of 18:01, 18 November 2024
Line 19:		Line 19:
	<!--T:6-->		<!--T:6-->
	Please follow these instructions:		Please follow these instructions:
	*Backup your files and database ~~([[Upgrading from a previous version#Before you start...\|did we already mention that?]]).~~		*Log out of the administration
			*Backup your files and database
	*Delete all the old files/folders except for:		*Delete all the old files/folders except for:
	**/application/config/security.php -'''Important!! This is the key to all encrypted data in LimeSurvey (version 4 and later)'''		**/application/config/security.php -'''Important!! This is the key to all encrypted data in LimeSurvey (version 4 and later)'''

C schmitz: Removed update instructions for versions earlier than 2.x.

2024-11-18T15:59:32Z

Removed update instructions for versions earlier than 2.x.

@@ Line 30: / Line 30: @@
 *Open the admin page in your browser (e.g. https://www.example.com/limesurvey/admin) and check if a database scheme upgrade is necessary.
 *After the upgrade: '''Clear your browser cache and cookies!'''
 = Upgrading using CLI = <!--T:25-->

C schmitz: Added information on MySQL error

2024-04-03T08:51:03Z

Added information on MySQL error

← Older revision		Revision as of 10:51, 3 April 2024
Line 133:		Line 133:

	==Survey theme incompatibility==		==Survey theme incompatibility==
			With certain major version updates any custom survey themes will not be compatible, anymore:

	~~Old survey theme are totally incompatible for this version : old theme are totally disabled~~		* Update from LimeSurvey 2.6 or lower to LimeSurvey 2.50
			* Update from LimeSurvey 5.x or lower to LimeSurvey 6.x

	* Update to ~~LimeSurvey 2.6lts or lower~~ to ~~LimeSurvey 2~~.50		==Error "Multiple primary key defined" when updating MySQL database==
	* Update from ~~LimeSurvey 5 or lower to LimeSurvey 6~~.0		If you encounter this error, please check the setting ''sql_generate_invisible_primary_key'' in your MySQL server variables. This is most likely set to ''ON'', but should be set to ''OFF''. Then restore your database from the backup (as explained above) and try again.

DenisChenu: Survey theme incompatibility

2023-11-15T08:50:21Z

Survey theme incompatibility

← Older revision		Revision as of 10:50, 15 November 2023
Line 131:		Line 131:
	Install version 1.50, import the file, and export the survey structure to the newer .csv format. Then install the latest Version 2.x and import the .csv format and export it to the current .lss format.		Install version 1.50, import the file, and export the survey structure to the newer .csv format. Then install the latest Version 2.x and import the .csv format and export it to the current .lss format.
	</translate>		</translate>

			==Survey theme incompatibility==

			Old survey theme are totally incompatible for this version : old theme are totally disabled

			* Update to LimeSurvey 2.6lts or lower to LimeSurvey 2.50
			* Update from LimeSurvey 5 or lower to LimeSurvey 6.0

C schmitz at 12:08, 30 August 2021

2021-08-30T12:08:22Z

← Older revision		Revision as of 14:08, 30 August 2021
Line 97:		Line 97:
	<!--T:30-->		<!--T:30-->
	If you have an error during database update and your LimeSurvey instance ends up in an unusable state, you want to go back to the previous version.		If you have an error during database update and your LimeSurvey instance ends up in an unusable state, you want to go back to the previous version.
	This assumes that you still have the database and file backup, either from ~~ComfortUpdate,~~ or ~~you~~ created ~~these manually~~.		This assumes that you still have the database and file backup, either from your regular backup or the one created by Comfortupdate.

	<!--T:31-->		<!--T:31-->

C schmitz at 12:06, 30 August 2021

2021-08-30T12:06:54Z

← Older revision		Revision as of 14:06, 30 August 2021
Line 91:		Line 91:
	You can upgrade the database via the PHP CLI: <code>php application/commands/console.php updatedb</code>. This allows you to set up an auto-upgrade system via command line (for example, in a crontab), although it is not recommended.		You can upgrade the database via the PHP CLI: <code>php application/commands/console.php updatedb</code>. This allows you to set up an auto-upgrade system via command line (for example, in a crontab), although it is not recommended.

	= Failed database upgrade after ~~file~~ update/ComfortUpdate= <!--T:29-->		= Failed database upgrade after manual update/ComfortUpdate= <!--T:29-->
	Sometimes, even though you did everything correct, things don't work out they are supposed to during database upgrade.		Sometimes, even though you did everything correct, things don't work out they are supposed to during database upgrade.
	That may happen because of various reasons: Different database versions, unexpected data formats or contents, unusual configurations or anything else that did not show up in our tests (yes, we test a lot!)		That may happen because of various reasons: Different database versions, unexpected data formats or contents, unusual configurations or anything else that did not show up in our tests (yes, we test a lot!)

C schmitz at 07:13, 20 August 2021

2021-08-20T07:13:05Z

← Older revision		Revision as of 09:13, 20 August 2021
Line 91:		Line 91:
	You can upgrade the database via the PHP CLI: <code>php application/commands/console.php updatedb</code>. This allows you to set up an auto-upgrade system via command line (for example, in a crontab), although it is not recommended.		You can upgrade the database via the PHP CLI: <code>php application/commands/console.php updatedb</code>. This allows you to set up an auto-upgrade system via command line (for example, in a crontab), although it is not recommended.

	= Failed database upgrade = <!--T:29-->		= Failed database upgrade after file update/ComfortUpdate= <!--T:29-->
	Sometimes, even though you did everything correct, things don't work out they are supposed to during database upgrade.		Sometimes, even though you did everything correct, things don't work out they are supposed to during database upgrade.
	That may happen because of various reasons: Different database versions, unexpected data formats or contents, unusual configurations or anything else that did not show up in our tests (yes, we test a lot!)		That may happen because of various reasons: Different database versions, unexpected data formats or contents, unusual configurations or anything else that did not show up in our tests (yes, we test a lot!)

C schmitz at 07:12, 20 August 2021

2021-08-20T07:12:08Z

← Older revision		Revision as of 09:12, 20 August 2021
Line 93:		Line 93:
	= Failed database upgrade = <!--T:29-->		= Failed database upgrade = <!--T:29-->
	Sometimes, even though you did everything correct, things don't work out they are supposed to during database upgrade.		Sometimes, even though you did everything correct, things don't work out they are supposed to during database upgrade.
	That may happen because of various reasons~~, different~~ database ~~version~~, unexpected data ~~format~~ or contents, unusual configurations or anything else that did not show up in our tests (yes, we test ~~alot~~!)		That may happen because of various reasons: Different database versions, unexpected data formats or contents, unusual configurations or anything else that did not show up in our tests (yes, we test a lot!)

	<!--T:30-->		<!--T:30-->