Transferring an installation/pt-br - Revision history

FuzzyBot: Updating to match new version of source page

2022-03-09T17:32:44Z

Updating to match new version of source page

← Older revision		Revision as of 19:32, 9 March 2022
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 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.~~		<div class="mw-translate-fuzzy">
			Talvez você terá a tarefa de mover sua instalação para um novo servidor. O processo deverá ser simples, mas pode ficar complicado por outros fatores. Aqui nós documentamos como transferir, o que fazer e como recuperar se você encontrar um problema
			</div>

	~~In general~~, ~~the only changes from a new and clean installation are the following~~:		<div class="mw-translate-fuzzy">
	# '''config.php''' ~~is usually changed to store basic installation parameters as well as any custom settings made;~~		Em geral, as únicas mudanças da nova e correta instalação são as seguintes:
	# '''upload/*''' ~~may contain custom templates or uploaded files;~~		# '''config.php''' é normalmente mudado para armazenar os parâmetros básicos da instalação básica assim como qualquer mudança customizada feita
	# '''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...'''.		# '''upload/*''' pode conter modelos customizados ou arquivos enviados
			# '''SQL database tables''' deverão ter os dados adicionados às tabelas criadas na instalação. Note também que algumas novas tabelas podem ser criadas para salvar cópias dos códigos de acesso e dados de resultado de uma pesquisas anteriores ou atualmente ativas. Essas novas tabelas são normalmente nomeadas '''lime_survey_nnn...''', '''lime_tokens_nnn...''', lime_oldsurvey_nnn...''', and lime_oldtokens_nnn...'''.
			</div>

	~~Otherwise~~, ~~unless you went in and made custom patches to the code~~, ~~changes should be limited to these areas~~.		<div class="mw-translate-fuzzy">
			De outra forma, a menos que você tenha saído e feito reparos customizados no código, mudanças são limitadas a essas áreas.
			</div>

	~~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~~.		<div class="mw-translate-fuzzy">
			O objetivo em transferir uma instalação para um novo sistema é similar à atualização. A maior diferença é que nós tentamos recriar simplificadamente a instalação atual no novo computador. Se você desejar [[Atualizar de uma versão anterior\|atualizar para uma nova versão]] também pode fazer isso depois, o segundo passo, uma vez que você tenha transferido a instalação, é verificar se está funcionando.
			</div>

	=~~Transferring any version~~=		<div class="mw-translate-fuzzy">
	* Prepare ~~and save the old release~~		=Transferir uma versão=
	** Backup your installation directory files and SQL~~-based database~~		# Prepare e salve o lançamento anterior
	*** At the command-line level, ~~make a~~ '''.zip''' or similar ~~archive of the whole installation directory tree of files~~		## Salve seus arquivos de diretório de instalação e o banco de dados baseado em SQL
	~~***~~ 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~~		### No nível do comando em linha, faça um arquivo '''.zip''' ou similar de todos os arquivos do diretório de instalação
	** Copy your '''config.php''' ~~file separately to ease the editing process~~		### Use phpMyAdmin ou similar para exportar todas as tabelas; ou use o botão '''Administração do LimeSurvey''' [[File:button-export-sql.png]] para salvar todo o banco de dados
	* Move the saved release to the new machine		## Copie seu arquivo '''config.php''' separadamente para fácil acesso posterior para editar
	** Unpack your installation files		# Mova o lançamento salvo para a nova máquina
	*** Create your new installation directory (~~same name is convenient~~)		## Descompacte seus arquivos de instalação
	*** Unpack/unzip the installation files into the same folder		### Crie o diretório para sua nova instalaçao (mesmo nome é conveniente)
	** Setup your SQL ~~database~~		### Descompacte os arquivos de instalação onde salvamos anteriormente
	*** Create the new database using phpMyAdmin ~~or a command-line~~ interface		## Configure seu banco de dados SQL
	*** Load the saved SQL~~-based database to recreate the tables and content~~		### Crie o novo banco de dados usando phpMyAdmin ou uma linha de comando de interface
	* Edit '''config.php''' ~~to reflect changes from the old release and check your installation~~		### Carregue o banco de dados SQL salvo para recriar as tabelas e conteúdo
	** 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~~		# Edite '''config.php''' para refletir as mudanças do antigo lançamento e conferir sua instalação
	** Visit the survey admin page or the page of an active survey and check if everything works		## Seja cuidadoso ao conferir o nome, usuário e senha do banco de dados; assim como o nome do servidor de instalação, caminho URL e diretório físico da instalação
	* You are good to go now :)		## Visite a página do administrador da pesquisa ou a página de uma pesquisa ativa; verifique se aparentemente tudo funciona.
			# Terminado (:biggrin:) .
			</div>

	~~{{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~~]].}}		<div class="mw-translate-fuzzy">
			Se você deseja atualizar na mesma máquina, você pode ir pelo mesmo processo descrito anterior para [[Atualizando de uma versão anterior\|atualizar de uma versão anterior]].
			</div>

	=~~Things that could go wrong~~=		<div class="mw-translate-fuzzy">
			=Coisas que podem dar errado=
			</div>

	~~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~~.		<div class="mw-translate-fuzzy">
			Tão simples como isso parece, coisas parecem dar errado. Respire fundo. Verifique se você seguiu os passos. Caso contrário, leia para saber onde outras pessoas desistiram no caminho.
			</div>

	==Instalação diferente de PHP em cada máquina==		==Instalação diferente de PHP em cada máquina==
Line 43:		Line 59:
	==Versão diferente do LimeSurvey (instalação e backup de arquivos de BD não compatíveis)==		==Versão diferente do LimeSurvey (instalação e backup de arquivos de BD não compatíveis)==

	~~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:~~		<div class="mw-translate-fuzzy">
			Talvez você não tenha feito corretamente o backup do código de instalação para ser compatível o banco de dados SQL salvo? Pode ser fácil deixar esses backups separados de outro modo, confusos ou fora de sincronia. Essas são algumas coisas que podem lhe ajudar a encontrar qual versão cada backup deve ser. Quando usar a opção salvar SQL do '''LimeSurvey''', o nome padrão do arquivo é criado e tem a data do backup no nome. Também, procurar dentro do arquivo de backup do banco de dados SQL, deve haver uma sessão parecida a de baixo onde a versão do banco de dados é armazenada. Esse valor é usado pelo instalador para determinar como aplicar mudanças às tabelas quando atualizar, por exemplo.
			</div>

	<syntaxhighlight lang="sql">		<syntaxhighlight lang="sql">

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

2022-02-16T13:00:10Z

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

← Older revision		Revision as of 15:00, 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:04Z

Updating to match new version of source page

FuzzyBot: Updating to match new version of source page

2017-09-11T09:05:08Z

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:01Z

Updating to match new version of source page

← Older revision		Revision as of 12:30, 14 August 2017
Line 13:		Line 13:
	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, do this as a later, second step once you have transferred the installation and verified that it works.

	=~~Transferir uma versão~~=		=Transferring any version=
	# Prepare ~~e salve o lançamento anterior~~		# Prepare and save the old release:
	## ~~Salve seus arquivos de diretório de instalação e o banco de dados baseado em~~ SQL		## Backup your installation directory files and SQL-based database:
	### ~~No nível do comando em linha~~, ~~faça um arquivo~~ '''.zip''' ou similar ~~de todos os arquivos do diretório de instalação~~		### At the command-line level, make a '''.zip''' or similar archive of the whole installation directory tree of files;
	### Use phpMyAdmin ou similar ~~para exportar todas as tabelas~~; ou use ~~o botão~~ '''~~Administração do LimeSurvey~~''' ~~[[File:button-export-sql.png]] para salvar todo o banco de dados~~		### 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;
	## ~~Copie seu arquivo~~ '''config.php''' ~~separadamente para fácil acesso posterior para editar~~		## Copy your '''config.php''' file separately to ease the editing process.
	# ~~Mova o lançamento salvo para a nova máquina~~		# Move the saved release to the new machine:
	## ~~Descompacte seus arquivos de instalação~~		## Unpack your installation files:
	### ~~Crie o diretório para sua nova instalaçao~~ (~~mesmo nome é conveniente~~)		### Create your new installation directory (same name is convenient);
	### ~~Descompacte os arquivos de instalação onde salvamos anteriormente~~		### Unpack/unzip the installation files into the same folder.
	## ~~Configure seu banco de dados~~ SQL		## Setup your SQL database:
	### ~~Crie o novo banco de dados usando~~ phpMyAdmin ~~ou uma linha de comando de~~ interface		### Create the new database using phpMyAdmin or a command line interface;
	### ~~Carregue o banco de dados~~ SQL ~~salvo para recriar as tabelas e conteúdo~~		### Load the saved SQL-based database to recreate the tables and content.
	# ~~Edite~~ '''config.php''' ~~para refletir as mudanças do antigo lançamento e conferir sua instalação~~		# Edit '''config.php''' to reflect changes from the old release and check your installation:
	## ~~Seja cuidadoso ao conferir o nome~~, ~~usuário e senha do banco de dados; assim como o nome do servidor de instalação~~, ~~caminho~~ URL ~~e diretório físico da instalação~~		## 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;
	## ~~Visite a página do administrador da pesquisa ou a página de uma pesquisa ativa; verifique se aparentemente tudo funciona~~.		## Visit the survey admin page or the page of an active survey and check if everything works.
	# ~~Terminado (: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]].}}

	=~~Coisas que podem dar errado~~=		=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">

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__

	~~Talvez você terá~~ a ~~tarefa de mover sua instalação para um novo servidor~~. ~~O processo deverá ser simples~~, ~~mas pode ficar complicado por outros fatores~~. ~~Aqui nós documentamos como transferir~~, ~~o que fazer e como recuperar se você encontrar um problema~~		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.

	~~Em geral~~, ~~as únicas mudanças da nova e correta instalação são as seguintes~~:		In general, the only changes from a new and clean installation are the following:
	# '''config.php''' ~~é normalmente mudado para armazenar os parâmetros básicos da instalação básica assim como qualquer mudança customizada feita~~		# '''config.php''' is usually changed to store basic installation parameters as well as any custom settings made;
	# '''upload/*''' ~~pode conter modelos customizados ou arquivos enviados~~		# '''upload/*''' may contain custom templates or uploaded files;
	# '''SQL database tables''' ~~deverão ter os dados adicionados às tabelas criadas na instalação~~. ~~Note também que algumas novas tabelas podem ser criadas para salvar cópias dos códigos de acesso e dados de resultado de uma pesquisas anteriores ou atualmente ativas~~. ~~Essas novas tabelas são normalmente nomeadas~~ '''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...'''.

	~~De outra forma~~, ~~a menos que você tenha saído e feito reparos customizados no código~~, ~~mudanças são limitadas a essas áreas~~.		Otherwise, unless you went in and made custom patches to the code, changes should be limited to these areas.

	~~O objetivo em transferir uma instalação para um novo sistema é~~ similar ~~à atualização~~. ~~A maior diferença é que nós tentamos recriar simplificadamente a instalação atual no novo computador~~. ~~Se você desejar~~ [[~~Atualizar de uma versão anterior~~\|~~atualizar para uma nova versão~~]] ~~também pode fazer isso depois, o segundo passo~~, ~~uma vez que você tenha transferido~~ a ~~instalação~~, ~~é verificar se está funcionando~~.		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.

	=Transferir uma versão=		=Transferir uma versão=
Line 31:		Line 31:
	# Terminado (:biggrin:) .		# Terminado (:biggrin:) .

	~~Se você deseja atualizar na mesma máquina~~, ~~você pode ir pelo mesmo processo descrito anterior para~~ [[~~Atualizando de uma versão anterior~~\|~~atualizar de uma versão anterior~~]].		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]].

	=Coisas que podem dar errado=		=Coisas que podem dar errado=

	~~Tão simples como isso parece~~, ~~coisas parecem dar errado~~. ~~Respire fundo~~. ~~Verifique se você seguiu os passos~~. ~~Caso contrário~~, ~~leia para saber onde outras pessoas desistiram no caminho~~.		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.

	==Instalação diferente de PHP em cada máquina==		==Instalação diferente de PHP em cada máquina==
Line 43:		Line 43:
	==Versão diferente do LimeSurvey (instalação e backup de arquivos de BD não compatíveis)==		==Versão diferente do LimeSurvey (instalação e backup de arquivos de BD não compatíveis)==

	~~Talvez você não tenha feito corretamente o~~ backup ~~do código de instalação para ser compatível o banco de dados~~ SQL ~~salvo? Pode ser fácil deixar esses~~ backups ~~separados de outro modo~~, ~~confusos ou fora de sincronia~~. ~~Essas são algumas coisas que podem lhe ajudar~~ a ~~encontrar qual versão cada~~ backup ~~deve ser~~. ~~Quando usar a opção salvar SQL do~~ '''LimeSurvey''', ~~o nome padrão do arquivo é criado e tem a data do~~ backup ~~no nome~~. ~~Também~~, ~~procurar dentro do arquivo de~~ backup ~~do banco de dados SQL~~, ~~deve haver uma sessão parecida~~ a ~~de baixo onde a versão do banco de dados é armazenada. Esse valor é usado pelo instalador para determinar como aplicar mudanças às tabelas quando atualizar, por exemplo.~~		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.'''

Andreza: Created page with "Talvez você não tenha feito corretamente o backup do código de instalação para ser compatível o banco de dados SQL salvo? Pode ser fácil deixar esses backups separados..."

2016-04-15T15:40:04Z

Created page with "Talvez você não tenha feito corretamente o backup do código de instalação para ser compatível o banco de dados SQL salvo? Pode ser fácil deixar esses backups separados..."

← Older revision		Revision as of 17:40, 15 April 2016
Line 43:		Line 43:
	==Versão diferente do LimeSurvey (instalação e backup de arquivos de BD não compatíveis)==		==Versão diferente do LimeSurvey (instalação e backup de arquivos de BD não compatíveis)==

	~~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~~.		Talvez você não tenha feito corretamente o backup do código de instalação para ser compatível o banco de dados SQL salvo? Pode ser fácil deixar esses backups separados de outro modo, confusos ou fora de sincronia. Essas são algumas coisas que podem lhe ajudar a encontrar qual versão cada backup deve ser. Quando usar a opção salvar SQL do '''LimeSurvey''', o nome padrão do arquivo é criado e tem a data do backup no nome. Também, procurar dentro do arquivo de backup do banco de dados SQL, deve haver uma sessão parecida a de baixo onde a versão do banco de dados é armazenada. Esse valor é usado pelo instalador para determinar como aplicar mudanças às tabelas quando atualizar, por exemplo.

Andreza: Created page with "==Versão diferente do LimeSurvey (instalação e backup de arquivos de BD não compatíveis)=="

2016-04-15T15:27:39Z

Created page with "==Versão diferente do LimeSurvey (instalação e backup de arquivos de BD não compatíveis)=="

← Older revision		Revision as of 17:27, 15 April 2016
Line 41:		Line 41:
	==Banco de dados SQL diferentes entre máquinas==		==Banco de dados SQL diferentes entre máquinas==

	==~~Different~~ LimeSurvey ~~version~~ (~~installation and DB~~ backup ~~file archives do not match~~)==		==Versão diferente do LimeSurvey (instalação e backup de arquivos de BD não compatíveis)==

	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.

Andreza: Created page with "==Banco de dados SQL diferentes entre máquinas=="

2016-04-15T15:26:02Z

Created page with "==Banco de dados SQL diferentes entre máquinas=="

← Older revision		Revision as of 17:26, 15 April 2016
Line 39:		Line 39:
	==Instalação diferente de PHP em cada máquina==		==Instalação diferente de PHP em cada máquina==

	==~~Different~~ SQL ~~Database between machines~~==		==Banco de dados SQL diferentes entre máquinas==

	==Different LimeSurvey version (installation and DB backup file archives do not match)==		==Different LimeSurvey version (installation and DB backup file archives do not match)==

Andreza: Created page with "==Instalação diferente de PHP em cada máquina=="

2016-04-15T15:25:39Z

Created page with "==Instalação diferente de PHP em cada máquina=="

← Older revision		Revision as of 17:25, 15 April 2016
Line 37:		Line 37:
	Tão simples como isso parece, coisas parecem dar errado. Respire fundo. Verifique se você seguiu os passos. Caso contrário, leia para saber onde outras pessoas desistiram no caminho.		Tão simples como isso parece, coisas parecem dar errado. Respire fundo. Verifique se você seguiu os passos. Caso contrário, leia para saber onde outras pessoas desistiram no caminho.

	==~~Different~~ PHP ~~installation on each machine~~==		==Instalação diferente de PHP em cada máquina==

	==Different SQL Database between machines==		==Different SQL Database between machines==

← 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.

	==Instalação diferente de PHP em cada máquina==		==Instalação diferente de PHP em cada máquina==