LimeSurvey 7 Fieldname Refactor - Revision history

C schmitz: Marked this version for translation

2026-06-30T08:41:15Z

Marked this version for translation

Jorynagel at 11:11, 29 January 2026

2026-01-29T11:11:25Z

← Older revision		Revision as of 13:11, 29 January 2026
Line 62:		Line 62:

	# Backup the database, as the changes are not reversible and if it goes wrong, it will be useful to have the database prior the change to recover		# Backup the database, as the changes are not reversible and if it goes wrong, it will be useful to have the database prior the change to recover
	# Checkout the develop-major ~~branche~~: <pre>git checkout develop-major</pre> or to clone/download the project directly at this branch at https://github.com/LimeSurvey/LimeSurvey/tree/develop-major		# Checkout the develop-major branch: <pre>git checkout develop-major</pre> or to clone/download the project directly at this branch at https://github.com/LimeSurvey/LimeSurvey/tree/develop-major
	# Load an admin page to trigger the change script		# Load an admin page to trigger the change script
	# Report any error you may get during the execution of the change script		# Report any error you may get during the execution of the change script

Jorynagel at 11:10, 29 January 2026

2026-01-29T11:10:51Z

← Older revision		Revision as of 13:10, 29 January 2026
Line 62:		Line 62:

	# Backup the database, as the changes are not reversible and if it goes wrong, it will be useful to have the database prior the change to recover		# Backup the database, as the changes are not reversible and if it goes wrong, it will be useful to have the database prior the change to recover
	# Checkout the ~~tablename/fieldname refactor epic~~: <pre>git checkout ~~epic/LE-33-tablename-fieldname~~-~~refactoring~~</pre> or to clone/download the project directly at this branch at https://github.com/LimeSurvey/LimeSurvey/tree/~~epic/LE-33-tablename-fieldname~~-~~refactoring~~		# Checkout the develop-major branche: <pre>git checkout develop-major</pre> or to clone/download the project directly at this branch at https://github.com/LimeSurvey/LimeSurvey/tree/develop-major
	# Load an admin page to trigger the change script		# Load an admin page to trigger the change script
	# Report any error you may get during the execution of the change script		# Report any error you may get during the execution of the change script

Jorynagel: Jorynagel moved page LimeSurvey Manual:LimeSurvey 7 Fieldname Refactor to LimeSurvey 7 Fieldname Refactor

2026-01-28T10:12:55Z

Jorynagel moved page LimeSurvey Manual:LimeSurvey 7 Fieldname Refactor to LimeSurvey 7 Fieldname Refactor

← Older revision		Revision as of 12:12, 28 January 2026
(No difference)

Jorynagel: Jorynagel moved page LimeSurvey 7 Major Version Upgrade to LimeSurvey Manual:LimeSurvey 7 Fieldname Refactor

2026-01-28T10:12:16Z

Jorynagel moved page LimeSurvey 7 Major Version Upgrade to LimeSurvey Manual:LimeSurvey 7 Fieldname Refactor

← Older revision		Revision as of 12:12, 28 January 2026
(No difference)

Jorynagel at 09:59, 28 January 2026

2026-01-28T09:59:52Z

← Older revision		Revision as of 11:59, 28 January 2026
Line 2:		Line 2:
	<translate>		<translate>

	= ~~Major Version Upgrade~~ - LimeSurvey 7 ~~(Beta 1)~~ =		= Fieldname and Response Table Refactor - LimeSurvey 7 =

	LimeSurvey 7 introduces a major cleanup of how response tables and fieldnames are generated.		LimeSurvey 7 introduces a major cleanup of how response tables and fieldnames are generated.

Jorynagel at 09:57, 28 January 2026

2026-01-28T09:57:58Z

← Older revision		Revision as of 11:57, 28 January 2026
Line 2:		Line 2:
	<translate>		<translate>

	= Major Version Upgrade - LimeSurvey 7 =		= Major Version Upgrade - LimeSurvey 7 (Beta 1) =

	LimeSurvey 7 introduces a major cleanup of how response tables and fieldnames are generated.		LimeSurvey 7 introduces a major cleanup of how response tables and fieldnames are generated.
	This update modernizes long-standing internal naming conventions and creates a more predictable and robust foundation for plugins, integrations, and future development.		This update modernizes long-standing internal naming conventions and creates a more predictable and robust foundation for plugins, integrations, and future development.

			This page currently documents the LS7 Beta 1 release and focuses on the response table and fieldname refactor.

	Because this is a structural change, any custom work that relies on old naming may require updates.		Because this is a structural change, any custom work that relies on old naming may require updates.
Line 49:		Line 51:

	= 2. Why this matters =		= 2. Why this matters =
	This cleanup addresses naming patterns that were formally defined and used over many years and brings them into a consistent and ~~robost~~ structure we can build on for the future.		This cleanup addresses naming patterns that were formally defined and used over many years and brings them into a consistent and robust structure we can build on for the future.

	Structural changes like this are rarely simple. They touch parts of the system that many plugins and integrations rely on, which is why they are often postponed due to their complexity. But keeping things consistent and predictable is important for long-term stability.		Structural changes like this are rarely simple. They touch parts of the system that many plugins and integrations rely on, which is why they are often postponed due to their complexity. But keeping things consistent and predictable is important for long-term stability.
Line 104:		Line 106:
	* custom JavaScript		* custom JavaScript
	* any custom integrations you have built		* any custom integrations you have built
	* or anything else you might worry about.

	Check if everything works as expected with the new table and fieldname naming.		Check if everything works as expected with the new table and fieldname naming.
Line 132:		Line 133:
	* any custom integrations you have built		* any custom integrations you have built
	* JavaScript using fieldname based selectors		* JavaScript using fieldname based selectors
	* custom themes interacting with response related identifiers		* custom themes interacting with response-related identifiers
	* integrations dependent on the previous naming scheme		* integrations dependent on the previous naming scheme
	* importing old exports such as survey, themes, question themes etc.		* importing old exports such as survey, themes, question themes etc.

Jorynagel: /* 3. How to preview new fieldnames */

2025-12-05T11:40:36Z

3. How to preview new fieldnames

← Older revision		Revision as of 13:40, 5 December 2025
Line 64:		Line 64:
	# Report any error you may get during the execution of the change script		# Report any error you may get during the execution of the change script
	# Study the new tablenames and fieldnames		# Study the new tablenames and fieldnames
	# Test ~~their~~ plugins/themes and fix errors related to tablenames and/or fieldnames		# Test your plugins/themes and fix errors related to tablenames and/or fieldnames

	The function used to convert old fieldnames into new fieldnames is the following:		The function used to convert old fieldnames into new fieldnames is the following:

Jorynagel: /* Parameters */

2025-12-05T11:04:32Z

Parameters

← Older revision		Revision as of 13:04, 5 December 2025
Line 78:		Line 78:
	* <b>$sid</b> - survey ID		* <b>$sid</b> - survey ID
	* <b>$gid</b> - group ID		* <b>$gid</b> - group ID
	n* <b>$cd</b> - whether condition designer logic applies		* <b>$cd</b> - whether condition designer logic applies

	== Result ==		== Result ==

Jorynagel: /* 3. How to preview new fieldnames */

2025-12-05T11:04:13Z

3. How to preview new fieldnames

← Older revision		Revision as of 13:04, 5 December 2025
Line 62:		Line 62:
	# Checkout the tablename/fieldname refactor epic: <pre>git checkout epic/LE-33-tablename-fieldname-refactoring</pre> or to clone/download the project directly at this branch at https://github.com/LimeSurvey/LimeSurvey/tree/epic/LE-33-tablename-fieldname-refactoring		# Checkout the tablename/fieldname refactor epic: <pre>git checkout epic/LE-33-tablename-fieldname-refactoring</pre> or to clone/download the project directly at this branch at https://github.com/LimeSurvey/LimeSurvey/tree/epic/LE-33-tablename-fieldname-refactoring
	# Load an admin page to trigger the change script		# Load an admin page to trigger the change script
	# Report any error ~~they~~ may get during the execution of the change script		# Report any error you may get during the execution of the change script
	# Study the new tablenames and fieldnames		# Study the new tablenames and fieldnames
	# Test their plugins/themes and fix errors related to tablenames and/or fieldnames		# Test their plugins/themes and fix errors related to tablenames and/or fieldnames