Transferring an installation/en - Revision history

C schmitz: Text replacement - " enclose="div"" to ""

2022-02-16T13:08:30Z

Text replacement - " enclose="div"" to ""

← Older revision		Revision as of 15:08, 16 February 2022
Line 45:		Line 45:
	There is a possibility that you did not have the correct installation backup code to match the backed-up SQL database. It could be easy to get these separate backups confused, out of sync, or otherwise separated. There are a few things that can help you find out what version each backup may be. When using the '''LimeSurvey''' SQL backup option, the default file name it creates has the date of the backup in the name. Also, if you search inside the SQL database backup file, you will find a section that looks similar to the example provided below where the database version is stored:		There is a possibility that you did not have the correct installation backup code to match the backed-up SQL database. It could be easy to get these separate backups confused, out of sync, or otherwise separated. There are a few things that can help you find out what version each backup may be. When using the '''LimeSurvey''' SQL backup option, the default file name it creates has the date of the backup in the name. Also, if you search inside the SQL database backup file, you will find a section that looks similar to the example provided below where the database version is stored:

	<syntaxhighlight lang="sql~~" enclose="div~~">		<syntaxhighlight lang="sql">
	#-----------------------------------------------------------------------		#-----------------------------------------------------------------------
	# Table data for lime_settings_global		# Table data for lime_settings_global

FuzzyBot: Updating to match new version of source page

2017-10-19T11:30:06Z

Updating to match new version of source page

FuzzyBot: Updating to match new version of source page

2017-09-11T09:05:09Z

Updating to match new version of source page

← Older revision		Revision as of 11:05, 11 September 2017
Line 17:		Line 17:
	## Backup your installation directory files and SQL-based database:		## Backup your installation directory files and SQL-based database:
	### At the command-line level, make a '''.zip''' or similar archive of the whole installation directory tree of files;		### At the command-line level, make a '''.zip''' or similar archive of the whole installation directory tree of files;
	### Use phpMyAdmin or similar to export all tables; or use the ''LimeSurvey backup entire database'' button that is located in the ''Configuration'' dialog, under the Advanced tab;		### Use phpMyAdmin or similar to export all tables; or use the '''LimeSurvey backup entire database''' button that is located in the '''Configuration''' dialog, under the Advanced tab;
	## Copy your '''config.php''' file separately to ease the editing process.		## Copy your '''config.php''' file separately to ease the editing process.
	# Move the saved release to the new machine:		# Move the saved release to the new machine:

FuzzyBot: Updating to match new version of source page

2017-08-14T10:30:02Z

Updating to match new version of source page

FuzzyBot: Updating to match new version of source page

2017-08-07T10:25:02Z

Updating to match new version of source page

← Older revision		Revision as of 12:25, 7 August 2017
Line 2:		Line 2:
	__TOC__		__TOC__

	~~So maybe you have~~ the task of moving ~~your~~ installation to a new server. ~~The~~ process should be simple but can get complicated by other factors. ~~Here we document~~ how to do the transfer and what to look out for and recover from if you encounter a problem.		You might get the task of moving the LimeSurvey installation to a new server. The process should be simple, but it can get complicated by other factors. You may find below information on how to do the transfer and what to look out for, and information on how to recover from if you encounter a problem.

	In general, the only changes from a new, clean installation are the following:		In general, the only changes from a new and clean installation are the following:
	# '''config.php''' is usually changed to store basic installation parameters as well as any custom settings made		# '''config.php''' is usually changed to store basic installation parameters as well as any custom settings made;
	# '''upload/*''' may contain custom templates or uploaded files		# '''upload/*''' may contain custom templates or uploaded files;
	# '''SQL database tables''' should have had data added to the tables created at installation time. ~~Note~~ also that some new tables may have been created to save copies of token and result data from previously or currently active surveys. ~~These~~ new tables are usually named '''lime_survey_nnn...''', '''lime_tokens_nnn...''', lime_oldsurvey_nnn...''', and lime_oldtokens_nnn...'''.		# '''SQL database tables''' should have had data added to the tables created at installation time. Note also that some new tables may have been created to save copies of token and result data from previously or currently active surveys. These new tables are usually named '''lime_survey_nnn...''', '''lime_tokens_nnn...''', '''lime_oldsurvey_nnn...''', and '''lime_oldtokens_nnn...'''.

	Otherwise, unless you ~~have gone~~ in and made custom patches to the code, changes ~~are~~ limited to these areas.		Otherwise, unless you went in and made custom patches to the code, changes should be limited to these areas.

	The goal in transferring an installation over to a new system is similar to upgrading. ~~The~~ biggest difference is we try to ~~simply~~ recreate the existing installation on the new computer. If you wish to [[Upgrading from a previous version\|upgrade to a newer version]] also, do this as a later, second step once you have transferred the installation and ~~verify~~ it ~~is working~~.		The goal in transferring an installation over to a new system is similar to upgrading. The biggest difference is that we simply try to recreate the existing installation on the new computer. If you wish to [[Upgrading from a previous version\|upgrade to a newer version]] also, do this as a later, second step once you have transferred the installation and verified that it works.

	=Transferring any version=		=Transferring any version=
Line 31:		Line 31:
	# You are done (:biggrin:) .		# You are done (:biggrin:) .

	If you wish to upgrade on this ~~same~~ machine, you now ~~can~~ go through the same process described ~~earlier~~ to [[Upgrading from a previous version\|upgrade to a newer version]].		If you wish to upgrade on this machine, you can now go through the same process described in the section related to the [[Upgrading from a previous version\|LimeSurvey upgrade to a newer version]].

	=Things that go wrong=		=Things that go wrong=

	As simple as this appears, things do seem to go wrong. Take a deep breath. ~~Verify~~ you followed the steps. ~~Otherwise~~ read on to see where other people got hung up along the way.		As simple as this appears, things do seem to go wrong sometimes. Take a deep breath. Verify that you followed thoroughly the steps. Otherwise, read below to see where other people got hung up along the way.

	==Different PHP installation on each machine==		==Different PHP installation on each machine==
Line 43:		Line 43:
	==Different LimeSurvey version (installation and DB backup file archives do not match)==		==Different LimeSurvey version (installation and DB backup file archives do not match)==

	~~Maybe~~ you did not have the correct installation backup code to match the backed-up SQL database? It could be easy to get these separate backups confused, out of sync, or otherwise separated. ~~There~~ are a few things that can help you find out what version each backup may be. ~~When~~ using the '''LimeSurvey''' SQL backup option, the default file name it creates has the date of the backup in the name. ~~Also~~, ~~searching~~ inside the SQL database backup file, ~~there should be~~ a section that looks similar to the below where the database version is stored~~. This value is used by the installer to determine how to apply changes to tables when upgrading, for example.~~		There is a possibility that you did not have the correct installation backup code to match the backed-up SQL database. It could be easy to get these separate backups confused, out of sync, or otherwise separated. There are a few things that can help you find out what version each backup may be. When using the '''LimeSurvey''' SQL backup option, the default file name it creates has the date of the backup in the name. Also, if you search inside the SQL database backup file, you will find a section that looks similar to the example provided below where the database version is stored:


Line 52:		Line 52:
	INSERT INTO lime_settings_global VALUES("DBVersion","126");		INSERT INTO lime_settings_global VALUES("DBVersion","126");
	....</syntaxhighlight>		....</syntaxhighlight>

			'''This value is used by the installer to determine how to apply changes to tables when upgrading.'''

C schmitz: Text replace - "Limesurvey" to "LimeSurvey"

2013-06-06T13:30:11Z

Text replace - "Limesurvey" to "LimeSurvey"

← Older revision		Revision as of 15:30, 6 June 2013
Line 17:		Line 17:
	## Backup your installation directory files and SQL-based database		## Backup your installation directory files and SQL-based database
	### At the command-line level, make a '''.zip''' or similar archive of the whole installation directory tree of files		### At the command-line level, make a '''.zip''' or similar archive of the whole installation directory tree of files
	### Use phpMyAdmin or similar to export all tables; or use the '''~~Limesurvey~~ Administration''' button [[File:button-export-sql.png]] to backup the entire database		### Use phpMyAdmin or similar to export all tables; or use the '''LimeSurvey Administration''' button [[File:button-export-sql.png]] to backup the entire database
	## Copy your '''config.php''' file separately for easy access to edit		## Copy your '''config.php''' file separately for easy access to edit
	# Move the saved release to the new machine		# Move the saved release to the new machine

C schmitz: Text replace - "Limesurvey" to "LimeSurvey"

2013-06-06T13:29:46Z

Text replace - "Limesurvey" to "LimeSurvey"

← Older revision		Revision as of 15:29, 6 June 2013
Line 17:		Line 17:
	## Backup your installation directory files and SQL-based database		## Backup your installation directory files and SQL-based database
	### At the command-line level, make a '''.zip''' or similar archive of the whole installation directory tree of files		### At the command-line level, make a '''.zip''' or similar archive of the whole installation directory tree of files
	### Use phpMyAdmin or similar to export all tables; or use the '''~~LimeSurvey~~ Administration''' button [[File:button-export-sql.png]] to backup the entire database		### Use phpMyAdmin or similar to export all tables; or use the '''Limesurvey Administration''' button [[File:button-export-sql.png]] to backup the entire database
	## Copy your '''config.php''' file separately for easy access to edit		## Copy your '''config.php''' file separately for easy access to edit
	# Move the saved release to the new machine		# Move the saved release to the new machine

C schmitz: Text replace - "Limesurvey" to "LimeSurvey"

2013-06-06T13:23:42Z

Text replace - "Limesurvey" to "LimeSurvey"

← Older revision		Revision as of 15:23, 6 June 2013
Line 17:		Line 17:
	## Backup your installation directory files and SQL-based database		## Backup your installation directory files and SQL-based database
	### At the command-line level, make a '''.zip''' or similar archive of the whole installation directory tree of files		### At the command-line level, make a '''.zip''' or similar archive of the whole installation directory tree of files
	### Use phpMyAdmin or similar to export all tables; or use the '''~~Limesurvey~~ Administration''' button [[File:button-export-sql.png]] to backup the entire database		### Use phpMyAdmin or similar to export all tables; or use the '''LimeSurvey Administration''' button [[File:button-export-sql.png]] to backup the entire database
	## Copy your '''config.php''' file separately for easy access to edit		## Copy your '''config.php''' file separately for easy access to edit
	# Move the saved release to the new machine		# Move the saved release to the new machine
Line 43:		Line 43:
	==Different LimeSurvey version (installation and DB backup file archives do not match)==		==Different LimeSurvey version (installation and DB backup file archives do not match)==

	Maybe you did not have the correct installation backup code to match the backed-up SQL database? It could be easy to get these separate backups confused, out of sync, or otherwise separated. There are a few things that can help you find out what version each backup may be. When using the '''~~Limesurvey~~''' SQL backup option, the default file name it creates has the date of the backup in the name. Also, searching inside the SQL database backup file, there should be a section that looks similar to the below where the database version is stored. This value is used by the installer to determine how to apply changes to tables when upgrading, for example.		Maybe you did not have the correct installation backup code to match the backed-up SQL database? It could be easy to get these separate backups confused, out of sync, or otherwise separated. There are a few things that can help you find out what version each backup may be. When using the '''LimeSurvey''' SQL backup option, the default file name it creates has the date of the backup in the name. Also, searching inside the SQL database backup file, there should be a section that looks similar to the below where the database version is stored. This value is used by the installer to determine how to apply changes to tables when upgrading, for example.

FuzzyBot: Updating to match new version of source page

2013-05-26T15:28:36Z

Updating to match new version of source page

← Older revision		Revision as of 17:28, 26 May 2013
Line 45:		Line 45:
	Maybe you did not have the correct installation backup code to match the backed-up SQL database? It could be easy to get these separate backups confused, out of sync, or otherwise separated. There are a few things that can help you find out what version each backup may be. When using the '''Limesurvey''' SQL backup option, the default file name it creates has the date of the backup in the name. Also, searching inside the SQL database backup file, there should be a section that looks similar to the below where the database version is stored. This value is used by the installer to determine how to apply changes to tables when upgrading, for example.		Maybe you did not have the correct installation backup code to match the backed-up SQL database? It could be easy to get these separate backups confused, out of sync, or otherwise separated. There are a few things that can help you find out what version each backup may be. When using the '''Limesurvey''' SQL backup option, the default file name it creates has the date of the backup in the name. Also, searching inside the SQL database backup file, there should be a section that looks similar to the below where the database version is stored. This value is used by the installer to determine how to apply changes to tables when upgrading, for example.

	<syntaxhighlight lang="~~php~~" enclose="div">
			<syntaxhighlight lang="sql" enclose="div">
	#-----------------------------------------------------------------------		#-----------------------------------------------------------------------
	# Table data for lime_settings_global		# Table data for lime_settings_global
	#-----------------------------------------------------------------------		#-----------------------------------------------------------------------

	INSERT INTO lime_settings_global VALUES("DBVersion","126");		INSERT INTO lime_settings_global VALUES("DBVersion","126");

	....</syntaxhighlight>		....</syntaxhighlight>

FuzzyBot: 从外部源导入一个新的版本

2013-05-21T13:36:50Z

从外部源导入一个新的版本

← Older revision		Revision as of 15:36, 21 May 2013
Line 46:		Line 46:

	<syntaxhighlight lang="php" enclose="div">		<syntaxhighlight lang="php" enclose="div">
	#~~<strike>~~-~~</strike><strike>~~-~~</strike><strike>~~-~~</strike><strike>~~-~~</strike><strike>~~-~~</strike><strike>~~-~~</strike><strike>~~-~~</strike><strike>~~-~~</strike>~~--		#-----------------------------------------------------------------------
	# Table data for lime_settings_global		# Table data for lime_settings_global
	#~~<strike>~~-~~</strike><strike>~~-~~</strike><strike>~~-~~</strike><strike>~~-~~</strike><strike>~~-~~</strike><strike>~~-~~</strike><strike>~~-~~</strike><strike>~~-~~</strike>~~--		#-----------------------------------------------------------------------

	INSERT INTO lime_settings_global VALUES("DBVersion","126");		INSERT INTO lime_settings_global VALUES("DBVersion","126");

	....</syntaxhighlight>		....</syntaxhighlight>

← Older revision		Revision as of 13:30, 19 October 2017
Line 2:		Line 2:
	__TOC__		__TOC__

	You might get the task of moving the LimeSurvey installation to a new server. The process should be simple, but it can get complicated by other factors. ~~You~~ may find ~~below~~ information on how to do the transfer and what to look out for, ~~and~~ information on how to recover from ~~if you encounter a problem~~.		You might get the task of moving the LimeSurvey installation to a new server. The process should be simple, but it can get complicated due to other factors. Below, you may find information on how to do the transfer and what to look out for, as well as information on how to recover from encountering any problems.

	In general, the only changes from a new and clean installation are the following:		In general, the only changes from a new and clean installation are the following:
Line 11:		Line 11:
	Otherwise, unless you went in and made custom patches to the code, changes should be limited to these areas.		Otherwise, unless you went in and made custom patches to the code, changes should be limited to these areas.

	The goal in transferring an installation over to a new system is similar to upgrading. The biggest difference is that we simply try to recreate the existing installation on the new computer. If you wish to [[Upgrading from a previous version\|upgrade to a newer version]] also, do this ~~as a later, second step once~~ you have transferred the installation and verified that it works.		The goal in transferring an installation over to a new system is similar to upgrading. The biggest difference is that we simply try to recreate the existing installation on the new computer. If you wish to [[Upgrading from a previous version\|upgrade to a newer version]] also, rather do this after you have transferred the installation and verified that it works.

	=Transferring any version=		=Transferring any version=
	# Prepare and save the old release:		* Prepare and save the old release
	## Backup your installation directory files and SQL-based database:		** Backup your installation directory files and SQL-based database
	~~###~~ At the command-line level, make a '''.zip''' or similar archive of the whole installation directory tree of files;		*** At the command-line level, make a '''.zip''' or similar archive of the whole installation directory tree of files
	~~###~~ Use phpMyAdmin or similar to export all tables; or use the '''LimeSurvey backup entire database''' button that is located in the '''Configuration''' dialog, under the Advanced tab;		*** Use phpMyAdmin or similar to export all tables; or use the '''LimeSurvey backup entire database''' button that is located in the '''Configuration''' dialog, under the Advanced tab
	## Copy your '''config.php''' file separately to ease the editing process.		** Copy your '''config.php''' file separately to ease the editing process
	# Move the saved release to the new machine:		* Move the saved release to the new machine
	## Unpack your installation files:		** Unpack your installation files
	~~###~~ Create your new installation directory (same name is convenient);		*** Create your new installation directory (same name is convenient)
	~~###~~ Unpack/unzip the installation files into the same folder.		*** Unpack/unzip the installation files into the same folder
	## Setup your SQL database:		** Setup your SQL database
	~~###~~ Create the new database using phpMyAdmin or a command line interface;		*** Create the new database using phpMyAdmin or a command-line interface
	~~###~~ Load the saved SQL-based database to recreate the tables and content.		*** Load the saved SQL-based database to recreate the tables and content
	# Edit '''config.php''' to reflect changes from the old release and check your installation:		* Edit '''config.php''' to reflect changes from the old release and check your installation
	## Be careful to check the database name, username, and password, as well as the installation server name, URL path, and physical directory path to the installation;		** Be careful to check the database name, username, and password, as well as the installation server name, URL path, and physical directory path to the installation
	## Visit the survey admin page or the page of an active survey and check if everything works.		** Visit the survey admin page or the page of an active survey and check if everything works
	# You are good to go now :).		* You are good to go now :)

	{{Box\|If you do not change the location of your LimeSurvey installation and wish only to upgrade it, go through the same process described in the section related to the [[Upgrading from a previous version\|LimeSurvey upgrade to a newer version]].}}		{{Box\|If you do not change the location of your LimeSurvey installation and wish only to upgrade it, go through the same process described in the section related to the [[Upgrading from a previous version\|LimeSurvey upgrade to a newer version]].}}
Line 35:		Line 35:
	=Things that could go wrong=		=Things that could go wrong=

	As simple as this appears, things do seem to go wrong sometimes. Take a deep breath. Verify that you followed ~~thoroughly~~ the steps. Otherwise, read below to see where other people got ~~hung up~~ along the way.		As simple as this appears, things do seem to go wrong sometimes. Take a deep breath. Verify that you followed the steps thoroughly. Otherwise, read below to see where other people got stuck along the way.

	==Different PHP installation on each machine==		==Different PHP installation on each machine==

← Older revision		Revision as of 12:30, 14 August 2017
Line 14:		Line 14:

	=Transferring any version=		=Transferring any version=
	# Prepare and save the old release		# Prepare and save the old release:
	## Backup your installation directory files and SQL-based database		## Backup your installation directory files and SQL-based database:
	### At the command-line level, make a '''.zip''' or similar archive of the whole installation directory tree of files		### At the command-line level, make a '''.zip''' or similar archive of the whole installation directory tree of files;
	### Use phpMyAdmin or similar to export all tables; or use the '''~~LimeSurvey Administration~~''' ~~button [[File:button-export-sql.png]] to backup~~ the ~~entire database~~		### Use phpMyAdmin or similar to export all tables; or use the ''LimeSurvey backup entire database'' button that is located in the ''Configuration'' dialog, under the Advanced tab;
	## Copy your '''config.php''' file separately ~~for easy access~~ to ~~edit~~		## Copy your '''config.php''' file separately to ease the editing process.
	# Move the saved release to the new machine		# Move the saved release to the new machine:
	## Unpack your installation files		## Unpack your installation files:
	### Create your new installation directory (same name is convenient)		### Create your new installation directory (same name is convenient);
	### Unpack/unzip the installation files into ~~it that were saved earlier~~		### Unpack/unzip the installation files into the same folder.
	## Setup your SQL database		## Setup your SQL database:
	### Create the new database using phpMyAdmin or a command line interface		### Create the new database using phpMyAdmin or a command line interface;
	### Load the saved SQL-based database to recreate the tables and content		### Load the saved SQL-based database to recreate the tables and content.
	# Edit '''config.php''' to reflect changes from the old release and check your installation		# Edit '''config.php''' to reflect changes from the old release and check your installation:
	## Be careful to check the database name, username, and password; as well as the installation server name, URL path and physical directory path to the installation		## Be careful to check the database name, username, and password, as well as the installation server name, URL path, and physical directory path to the installation;
	## Visit the survey admin page or the page of an active survey~~; verify~~ everything ~~appears to be working~~.		## Visit the survey admin page or the page of an active survey and check if everything works.
	# You are ~~done (:biggrin~~:) .		# You are good to go now :).

	If you wish to upgrade ~~on this machine~~, ~~you can now~~ go through the same process described in the section related to the [[Upgrading from a previous version\|LimeSurvey upgrade to a newer version]].		{{Box\|If you do not change the location of your LimeSurvey installation and wish only to upgrade it, go through the same process described in the section related to the [[Upgrading from a previous version\|LimeSurvey upgrade to a newer version]].}}

	=Things that go wrong=		=Things that could go wrong=

	As simple as this appears, things do seem to go wrong sometimes. Take a deep breath. Verify that you followed thoroughly the steps. Otherwise, read below to see where other people got hung up along the way.		As simple as this appears, things do seem to go wrong sometimes. Take a deep breath. Verify that you followed thoroughly the steps. Otherwise, read below to see where other people got hung up along the way.
Line 44:		Line 44:

	There is a possibility that you did not have the correct installation backup code to match the backed-up SQL database. It could be easy to get these separate backups confused, out of sync, or otherwise separated. There are a few things that can help you find out what version each backup may be. When using the '''LimeSurvey''' SQL backup option, the default file name it creates has the date of the backup in the name. Also, if you search inside the SQL database backup file, you will find a section that looks similar to the example provided below where the database version is stored:		There is a possibility that you did not have the correct installation backup code to match the backed-up SQL database. It could be easy to get these separate backups confused, out of sync, or otherwise separated. There are a few things that can help you find out what version each backup may be. When using the '''LimeSurvey''' SQL backup option, the default file name it creates has the date of the backup in the name. Also, if you search inside the SQL database backup file, you will find a section that looks similar to the example provided below where the database version is stored:


	<syntaxhighlight lang="sql" enclose="div">		<syntaxhighlight lang="sql" enclose="div">