LimeSurvey 7 Question Editor - Revision history

C schmitz: /* How to switch from get to path */

2026-08-06T09:25:54Z

How to switch from get to path

← Older revision		Revision as of 11:25, 6 August 2026
Line 118:		Line 118:

	* '''Apache:''' The <code>mod_rewrite</code> module must be enabled. Check that the <code>.htaccess</code> file in your LimeSurvey root directory is being processed (<code>AllowOverride All</code> or <code>AllowOverride FileInfo Options</code> must be set for your document root in the Apache configuration).		* '''Apache:''' The <code>mod_rewrite</code> module must be enabled. Check that the <code>.htaccess</code> file in your LimeSurvey root directory is being processed (<code>AllowOverride All</code> or <code>AllowOverride FileInfo Options</code> must be set for your document root in the Apache configuration).
	* '''nginx:''' Your <code>nginx.conf</code> or site configuration must include a <code>try_files</code> directive that forwards requests to <code>index.php</code>. Also check out our [[LimeSurvey nginx example configuration]]-		* '''nginx:''' Your <code>nginx.conf</code> or site configuration must include a <code>try_files</code> directive that forwards requests to <code>index.php</code>. Also check out our [[LimeSurvey nginx example configuration]].
	* '''IIS:''' The URL Rewrite module must be installed and a <code>web.config</code> rewrite rule must be in place.		* '''IIS:''' The URL Rewrite module must be installed and a <code>web.config</code> rewrite rule must be in place.

C schmitz: /* Step 1 – Verify your server supports URL rewriting */

2026-08-06T08:17:51Z

Step 1 – Verify your server supports URL rewriting

← Older revision		Revision as of 10:17, 6 August 2026
Line 118:		Line 118:

	* '''Apache:''' The <code>mod_rewrite</code> module must be enabled. Check that the <code>.htaccess</code> file in your LimeSurvey root directory is being processed (<code>AllowOverride All</code> or <code>AllowOverride FileInfo Options</code> must be set for your document root in the Apache configuration).		* '''Apache:''' The <code>mod_rewrite</code> module must be enabled. Check that the <code>.htaccess</code> file in your LimeSurvey root directory is being processed (<code>AllowOverride All</code> or <code>AllowOverride FileInfo Options</code> must be set for your document root in the Apache configuration).
	* '''nginx:''' Your <code>nginx.conf</code> or site configuration must include a <code>try_files</code> directive that forwards requests to <code>index.php</code>. ~~Check~~ out our [[LimeSurvey nginx example configuration]]		* '''nginx:''' Your <code>nginx.conf</code> or site configuration must include a <code>try_files</code> directive that forwards requests to <code>index.php</code>. Also check out our [[LimeSurvey nginx example configuration]]-
	* '''IIS:''' The URL Rewrite module must be installed and a <code>web.config</code> rewrite rule must be in place.		* '''IIS:''' The URL Rewrite module must be installed and a <code>web.config</code> rewrite rule must be in place.

C schmitz at 08:17, 6 August 2026

2026-08-06T08:17:20Z

← Older revision		Revision as of 10:17, 6 August 2026
Line 118:		Line 118:

	* '''Apache:''' The <code>mod_rewrite</code> module must be enabled. Check that the <code>.htaccess</code> file in your LimeSurvey root directory is being processed (<code>AllowOverride All</code> or <code>AllowOverride FileInfo Options</code> must be set for your document root in the Apache configuration).		* '''Apache:''' The <code>mod_rewrite</code> module must be enabled. Check that the <code>.htaccess</code> file in your LimeSurvey root directory is being processed (<code>AllowOverride All</code> or <code>AllowOverride FileInfo Options</code> must be set for your document root in the Apache configuration).
	* '''nginx:''' Your <code>nginx.conf</code> or site configuration must include a <code>try_files</code> directive that forwards requests to <code>index.php</code>.		* '''nginx:''' Your <code>nginx.conf</code> or site configuration must include a <code>try_files</code> directive that forwards requests to <code>index.php</code>. Check out our [[LimeSurvey nginx example configuration]]
	* '''IIS:''' The URL Rewrite module must be installed and a <code>web.config</code> rewrite rule must be in place.		* '''IIS:''' The URL Rewrite module must be installed and a <code>web.config</code> rewrite rule must be in place.

Twilllig at 10:22, 27 April 2026

2026-04-27T10:22:37Z

@@ Line 63: / Line 63: @@
 | '''Note:''' With <code>showScriptName = true</code> (the default), <code>index.php</code> remains visible in the URL. Setting it to <code>false</code> removes it entirely but requires additional server configuration and is not covered by this article.
 |}
 ----
@@ Line 130: / Line 173: @@
 Log in normally. The new editor can now be activated from the editor selection modal or from your account settings.
 ----

Twilllig: /* path format (required for the new editor) */

2026-04-23T10:25:34Z

path format (required for the new editor)

← Older revision		Revision as of 12:25, 23 April 2026
Line 46:		Line 46:
	\| Admin area \|\| <code><nowiki>https://example.com/limesurvey/index.php/admin</nowiki></code>		\| Admin area \|\| <code><nowiki>https://example.com/limesurvey/index.php/admin</nowiki></code>
	\|-		\|-
	\| Survey start \|\| <code><nowiki>https://example.com/limesurvey/index.php~~/survey~~/123456</nowiki></code>		\| Survey start \|\| <code><nowiki>https://example.com/limesurvey/index.php/123456</nowiki></code>
	\|-		\|-
	\| Survey with token \|\| <code><nowiki>https://example.com/limesurvey/index.php~~/survey~~/123456?token=abc123</nowiki></code>		\| Survey with token \|\| <code><nowiki>https://example.com/limesurvey/index.php/123456?token=abc123</nowiki></code>
	\|-		\|-
	\| Survey with token + custom variables \|\| <code><nowiki>https://example.com/limesurvey/index.php~~/survey~~/123456?token=abc123&myvar=321</nowiki></code>		\| Survey with token + custom variables \|\| <code><nowiki>https://example.com/limesurvey/index.php/123456?token=abc123&myvar=321</nowiki></code>
	\|}		\|}
	{\| style="border-left: 4px solid #3a87ad; background-color: #d9edf7; padding: 8px 12px; width: 100%"		{\| style="border-left: 4px solid #3a87ad; background-color: #d9edf7; padding: 8px 12px; width: 100%"

Twilllig: /* path format (required for the new editor) */

2026-04-23T10:23:47Z

path format (required for the new editor)

← Older revision		Revision as of 12:23, 23 April 2026
Line 37:		Line 37:
	==== <code>path</code> format (required for the new editor) ====		==== <code>path</code> format (required for the new editor) ====

	~~Parameters are~~ embedded as segments of the URL path, separated by <code>/</code>.		The routing part of the URL is embedded as segments of the URL path, separated by <code>/</code>. Custom parameters such as tokens and user-defined variables are still passed as regular query string arguments after a <code>?</code> character.

	'''Examples:'''		'''Examples:'''
Line 46:		Line 46:
	\| Admin area \|\| <code><nowiki>https://example.com/limesurvey/index.php/admin</nowiki></code>		\| Admin area \|\| <code><nowiki>https://example.com/limesurvey/index.php/admin</nowiki></code>
	\|-		\|-
	\| Survey start \|\| <code><nowiki>https://example.com/limesurvey/index.php/survey~~/index/sid~~/123456</nowiki></code>		\| Survey start \|\| <code><nowiki>https://example.com/limesurvey/index.php/survey/123456</nowiki></code>
	\|-		\|-
	\| Survey with token \|\| <code><nowiki>https://example.com/limesurvey/index.php/survey/index/~~sid~~/123456/token/abc123</nowiki></code>		\| Survey with token \|\| <code><nowiki>https://example.com/limesurvey/index.php/survey/123456?token=abc123</nowiki></code>
			\|-
			\| Survey with token + custom variables \|\| <code><nowiki>https://example.com/limesurvey/index.php/survey/123456?token=abc123&myvar=321</nowiki></code>
			\|}
			{\| style="border-left: 4px solid #3a87ad; background-color: #d9edf7; padding: 8px 12px; width: 100%"
			\|-
			\| '''Note:''' Existing panel integrations and other use cases that pass custom URL parameters (e.g. <code>?token=...&panelid=...</code>) will continue to work without modification. Only the routing part of the URL has changed; query string parameters are appended the same way as before.
	\|}		\|}

Twilllig at 12:23, 26 March 2026

2026-03-26T12:23:00Z

Show changes

Jorynagel: Replaced content with "Test"

2026-01-28T14:25:33Z

Replaced content with "Test"

← Older revision		Revision as of 16:25, 28 January 2026
Line 1:		Line 1:
	~~<languages />~~		Test
	~~<translate>~~

	~~= New Question Editor in LimeSurvey 7 =~~

	~~LimeSurvey 7 introduces a new Question Editor designed to improve how surveys and questions are created and managed.~~

	The new editor focuses on clearer structure, improved usability, and a more consistent editing experience across question types. It updates the user interface and workflows used when creating, editing, and configuring questions, while keeping existing survey logic and data handling intact.

	~~This page provides an overview of the new Question Editor and links to more detailed documentation where relevant.~~

	~~__TOC__~~


	~~= What is the new Question Editor =~~

	The Question Editor is the interface used to create and configure questions in a survey. In LimeSurvey 7, this editor has been redesigned to make common tasks easier and to reduce complexity when working with more advanced question setups.

	~~Key goals of the new editor include:~~

	* clearer separation between question content and settings
	* improved navigation within complex questions
	* more consistent behavior across question types
	* a foundation that is easier to extend in future versions


	~~= Who should review this change =~~

	~~You should review the new Question Editor if you:~~

	* create or edit surveys regularly
	* work with complex question structures
	* maintain custom question themes
	* rely on specific editor workflows in LimeSurvey

	~~For most users, existing surveys continue to work as before. The changes mainly affect how questions are edited, not how they behave when a survey is run.~~


	~~= Scope and limitations =~~

	~~The new Question Editor focuses on the user interface and editing workflows.~~

	~~It does not change:~~

	* how responses are stored
	* how survey logic is evaluated
	* how conditions or expressions work
	* existing response data

	~~Structural backend changes, such as response table and fieldname updates, are documented separately.~~


	~~= Related documentation =~~

	* [[LimeSurvey_7_Fieldname_Refactor\|Fieldname and Response Table Refactor - LimeSurvey 7]]
	* [[LimeSurvey_7_Major_Version\|LimeSurvey 7 Major Version]]


	~~= Notes =~~

	~~The Question Editor is part of the ongoing LimeSurvey 7 release. Documentation may be extended as the editor evolves and additional features are introduced.~~

	~~</translate>~~

Jorynagel: Created page with " = New Question Editor in LimeSurvey 7 = LimeSurvey 7 introduces a new Question Editor designed to improve how surveys and questions are created and managed. The new editor focuses on clearer structure, improved usability, and a more consistent editing experience across question types. It updates the user interface and workflows used when creating, editing, and configuring questions, while keeping existing survey logic and data handling intact..."

2026-01-28T14:23:48Z

Created page with "<languages /> <translate> = New Question Editor in LimeSurvey 7 = LimeSurvey 7 introduces a new Question Editor designed to improve how surveys and questions are created and managed. The new editor focuses on clearer structure, improved usability, and a more consistent editing experience across question types. It updates the user interface and workflows used when creating, editing, and configuring questions, while keeping existing survey logic and data handling intact..."

New page

<languages />
<translate>

= New Question Editor in LimeSurvey 7 =

LimeSurvey 7 introduces a new Question Editor designed to improve how surveys and questions are created and managed.

The new editor focuses on clearer structure, improved usability, and a more consistent editing experience across question types. It updates the user interface and workflows used when creating, editing, and configuring questions, while keeping existing survey logic and data handling intact.

This page provides an overview of the new Question Editor and links to more detailed documentation where relevant.

__TOC__

= What is the new Question Editor =

The Question Editor is the interface used to create and configure questions in a survey. In LimeSurvey 7, this editor has been redesigned to make common tasks easier and to reduce complexity when working with more advanced question setups.

Key goals of the new editor include:

* clearer separation between question content and settings
* improved navigation within complex questions
* more consistent behavior across question types
* a foundation that is easier to extend in future versions

= Who should review this change =

You should review the new Question Editor if you:

* create or edit surveys regularly
* work with complex question structures
* maintain custom question themes
* rely on specific editor workflows in LimeSurvey

For most users, existing surveys continue to work as before. The changes mainly affect how questions are edited, not how they behave when a survey is run.

= Scope and limitations =

The new Question Editor focuses on the user interface and editing workflows.

It does not change:

* how responses are stored
* how survey logic is evaluated
* how conditions or expressions work
* existing response data

Structural backend changes, such as response table and fieldname updates, are documented separately.

= Related documentation =

* [[LimeSurvey_7_Fieldname_Refactor|Fieldname and Response Table Refactor - LimeSurvey 7]]
* [[LimeSurvey_7_Major_Version|LimeSurvey 7 Major Version]]

= Notes =

The Question Editor is part of the ongoing LimeSurvey 7 release. Documentation may be extended as the editor evolves and additional features are introduced.

</translate>