Workarounds: Further solutions provided by LimeSurvey users - Revision history

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

2022-02-16T13:05:03Z

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

← Older revision		Revision as of 15:05, 16 February 2022
Line 119:		Line 119:
	Around line 75 find the corresponding code:		Around line 75 find the corresponding code:

	<syntaxhighlight lang="php~~" enclose="div~~">		<syntaxhighlight lang="php">

	//Check if this email already exists in token database		//Check if this email already exists in token database
Line 159:		Line 159:
	Sometimes people would like to be able to preview all questions in a survey before actually ''taking ''the survey - it gives them a chance to prepare their information in advance. While the LimeSurvey admin tool lets you create a printable version of a survey, this is not really appropriate for end users, as it contains placeholders for token values, etc. So, for our installation I created a separate PHP script, which you can install on your server and provide for users. Further notes are in the body of the script:		Sometimes people would like to be able to preview all questions in a survey before actually ''taking ''the survey - it gives them a chance to prepare their information in advance. While the LimeSurvey admin tool lets you create a printable version of a survey, this is not really appropriate for end users, as it contains placeholders for token values, etc. So, for our installation I created a separate PHP script, which you can install on your server and provide for users. Further notes are in the body of the script:

	<syntaxhighlight lang="php~~" enclose="div~~"><?php		<syntaxhighlight lang="php"><?php

	/******		/******
Line 471:		Line 471:
	Now the code:		Now the code:

	<syntaxhighlight lang="php~~" enclose="div~~"> <Macro name="format.1to5" Ctrl="no" Alt="no" Shift="no" Key="0">		<syntaxhighlight lang="php"> <Macro name="format.1to5" Ctrl="no" Alt="no" Shift="no" Key="0">

	<Action type="0" message="2316" wParam="0" lParam="0" sParam="" />		<Action type="0" message="2316" wParam="0" lParam="0" sParam="" />
Line 974:		Line 974:
	Here is the full script ready to go with google JS and HTML code:		Here is the full script ready to go with google JS and HTML code:

	<syntaxhighlight lang="php~~" enclose="div~~">		<syntaxhighlight lang="php">
	<?php		<?php

Line 1,227:		Line 1,227:
	#In your spreadsheet use the following format (pasting in a cell):		#In your spreadsheet use the following format (pasting in a cell):

	<syntaxhighlight lang="html~~" enclose="div~~">=IMPORTXML("http://mysite.com/myxml.php?refresh=&GoogleClock()", "//mytaglabel")</syntaxhighlight>		<syntaxhighlight lang="html">=IMPORTXML("http://mysite.com/myxml.php?refresh=&GoogleClock()", "//mytaglabel")</syntaxhighlight>


	To protect your XML file(s) from direct access you can put them in a dedicated folder and use a .htacess file to limit the access exclusively to Google Apps web crawlers filtered by ip ranges		To protect your XML file(s) from direct access you can put them in a dedicated folder and use a .htacess file to limit the access exclusively to Google Apps web crawlers filtered by ip ranges

	<syntaxhighlight lang="html~~" enclose="div~~">order allow, deny		<syntaxhighlight lang="html">order allow, deny
	deny from all		deny from all
	# allow from your_ip		# allow from your_ip
Line 1,247:		Line 1,247:
	The following php file will generate an XML view printing ID, STARTDATE and STARTLANGUAGE values of a survey.		The following php file will generate an XML view printing ID, STARTDATE and STARTLANGUAGE values of a survey.

	<syntaxhighlight lang="php~~" enclose="div~~">		<syntaxhighlight lang="php">
	<?php		<?php

Line 1,314:		Line 1,314:
	Add this to your .htaccess in the Limesurvey installation folder.		Add this to your .htaccess in the Limesurvey installation folder.
	And replace the myLimeFolder and domain name to whatever you have repecively.		And replace the myLimeFolder and domain name to whatever you have repecively.
	<syntaxhighlight lang="html~~" enclose="div~~">		<syntaxhighlight lang="html">
	# ALL ADMIN TO SSL		# ALL ADMIN TO SSL
	RewriteCond %{SERVER_PORT} 80		RewriteCond %{SERVER_PORT} 80
Line 1,330:		Line 1,330:

	The place to start is adding a bunch of attributes to the regular token table. At some point, according to the documentation, it was possible to specify how long each of the additional attributes should be. In my current version (2.50+) this is no longer a part of the token management screen, and all the tokens created have length 255. This means that you rapidly run out of space in the tokens table (at about 85 columns in utf8 character set). Limesurvey is perfectly happy if you downsize the columns, which you can do by running an "alter table modify …" on columns of the lime_tokens_<sid> table. MySQL does not allow the SQL variant dealing with more than one row at a time, so most efficient is to write a script to create the one-column-at-a-time statements, e.g.:		The place to start is adding a bunch of attributes to the regular token table. At some point, according to the documentation, it was possible to specify how long each of the additional attributes should be. In my current version (2.50+) this is no longer a part of the token management screen, and all the tokens created have length 255. This means that you rapidly run out of space in the tokens table (at about 85 columns in utf8 character set). Limesurvey is perfectly happy if you downsize the columns, which you can do by running an "alter table modify …" on columns of the lime_tokens_<sid> table. MySQL does not allow the SQL variant dealing with more than one row at a time, so most efficient is to write a script to create the one-column-at-a-time statements, e.g.:
	<syntaxhighlight lang="html~~" enclose="div~~">		<syntaxhighlight lang="html">
	select CONCAT('alter table lime_tokens_<SID> modify ',COLUMN_NAME,' varchar(10);')		select CONCAT('alter table lime_tokens_<SID> modify ',COLUMN_NAME,' varchar(10);')
	from information_schema.COLUMNS		from information_schema.COLUMNS
Line 1,343:		Line 1,343:
	# Columns called attribute_1 through attribute_n. The columns cannot be called by the alias names that you might have given them in the first step. Clearly this means that you (as the programmer in the database from which the information is being brought), need to have some sort of concordance list that tells you that "attribute_23" is the data of birth of the 3rd child (or whatever). In limesurvey the concordance is stored in JSON in the attributedescriptions column of the appropriate row in the lime_surveys table. You can extract it in MySQL using "select attributedescriptions from lime_surveys where sid = <whatever>", and you should then be able to format it with one row per line and use that to guide writing the .csv file.		# Columns called attribute_1 through attribute_n. The columns cannot be called by the alias names that you might have given them in the first step. Clearly this means that you (as the programmer in the database from which the information is being brought), need to have some sort of concordance list that tells you that "attribute_23" is the data of birth of the 3rd child (or whatever). In limesurvey the concordance is stored in JSON in the attributedescriptions column of the appropriate row in the lime_surveys table. You can extract it in MySQL using "select attributedescriptions from lime_surveys where sid = <whatever>", and you should then be able to format it with one row per line and use that to guide writing the .csv file.
	Alternatively, when you export the token table, the column headers will look like "attribute_8<ISElig>" which you could transpose in Excel to use as the list. In my case I created a table in the database with meaningful column names , and then had to write a query to turn then back into columns named attribute_1 through attribute_n, like:		Alternatively, when you export the token table, the column headers will look like "attribute_8<ISElig>" which you could transpose in Excel to use as the list. In my case I created a table in the database with meaningful column names , and then had to write a query to turn then back into columns named attribute_1 through attribute_n, like:
	<syntaxhighlight lang="html~~" enclose="div~~">		<syntaxhighlight lang="html">
	select firstname "firstname",lastname "lastname",email "email",		select firstname "firstname",lastname "lastname",email "email",
	case_id "attribute_1",		case_id "attribute_1",
Line 1,360:		Line 1,360:

	The ExpressionScript (introduced about version 1.96) makes assigning the values from the TOKEN to the survey field quite easy. Each assignment should look something like:		The ExpressionScript (introduced about version 1.96) makes assigning the values from the TOKEN to the survey field quite easy. Each assignment should look something like:
	<syntaxhighlight lang="html~~" enclose="div~~">		<syntaxhighlight lang="html">
	{II2_1 = if(is_empty(II2_1),TOKEN:ATTRIBUTE_7,II2_1)}		{II2_1 = if(is_empty(II2_1),TOKEN:ATTRIBUTE_7,II2_1)}
	</syntaxhighlight>		</syntaxhighlight>
Line 1,373:		Line 1,373:
	# You can add multiple EM assignment statements in a single question.		# You can add multiple EM assignment statements in a single question.
	# If your token attribute is not actually what you need to put into the survey variable, then you can use an "if" function to transform it, e.g. your imported data has 'Yes' and you need to set the variable to A1, otherwise A2 use:		# If your token attribute is not actually what you need to put into the survey variable, then you can use an "if" function to transform it, e.g. your imported data has 'Yes' and you need to set the variable to A1, otherwise A2 use:
	<syntaxhighlight lang="html~~" enclose="div~~">		<syntaxhighlight lang="html">
	§ If(TOKEN:ATTRIBUTE_7=="Yes","A1","A2")		§ If(TOKEN:ATTRIBUTE_7=="Yes","A1","A2")
	</syntaxhighlight>		</syntaxhighlight>

C schmitz: Text replacement - "Expression Manager" to "ExpressionScript"

2020-02-11T13:50:08Z

Text replacement - "Expression Manager" to "ExpressionScript"

← Older revision		Revision as of 15:50, 11 February 2020
Line 1,359:		Line 1,359:
	The third part of the process is to write the code to copy the values from the token table to the survey variable for which they are required. The place to put this code is in the Question box of an question that is of type "Equation", and which has an advanced setting of "Always hide this question" = "Yes".		The third part of the process is to write the code to copy the values from the token table to the survey variable for which they are required. The place to put this code is in the Question box of an question that is of type "Equation", and which has an advanced setting of "Always hide this question" = "Yes".

	The ~~Expression Manager~~ (introduced about version 1.96) makes assigning the values from the TOKEN to the survey field quite easy. Each assignment should look something like:		The ExpressionScript (introduced about version 1.96) makes assigning the values from the TOKEN to the survey field quite easy. Each assignment should look something like:
	<syntaxhighlight lang="html" enclose="div">		<syntaxhighlight lang="html" enclose="div">
	{II2_1 = if(is_empty(II2_1),TOKEN:ATTRIBUTE_7,II2_1)}		{II2_1 = if(is_empty(II2_1),TOKEN:ATTRIBUTE_7,II2_1)}

Tpartner at 13:55, 14 June 2016

2016-06-14T13:55:07Z

← Older revision		Revision as of 15:55, 14 June 2016
Line 1,376:		Line 1,376:
	§ If(TOKEN:ATTRIBUTE_7=="Yes","A1","A2")		§ If(TOKEN:ATTRIBUTE_7=="Yes","A1","A2")
	</syntaxhighlight>		</syntaxhighlight>

			=Insert a JavaScript file into a custom admin theme (LimeSurvey 2.06)=

			*Create your own admin template - see [[Custom_Admin_Themes#Creating_a_new_theme\|Custom Admin Themes]]
			*Add a custom JavaScript file to your new template directory
			*Extract the attached [[Media:InsertAdminJS.zip\|insertAdminJS plugin folder]] in your /plugins directory
			*In Plugin manager, activate the "'''''Insert Custom Admin JS File'''''" plugin
			* If you have named your custom JS file something other than "'''''custom.js'''''", go to the plugin settings and enter the filename

			You will then see the custom JavaScript file inserted into all admin pages:

			[[File:Inserted_js_file.png]]

Jonwat at 12:39, 13 May 2016

2016-05-13T12:39:52Z

@@ Line 1,319: / Line 1,319: @@
 RewriteCond %{REQUEST_URI} myLimeFolder/index.php/admin
 RewriteRule ^(.*)$ https://myserver.com/myLimeFolder/index.php/admin/$2 [R,L]
 </syntaxhighlight>

Ben V: /* Import & show data into a Google Drive Spreadsheet */

2016-05-02T09:11:41Z

Import & show data into a Google Drive Spreadsheet

← Older revision		Revision as of 11:11, 2 May 2016
Line 1,235:		Line 1,235:
	deny from all		deny from all
	# allow from your_ip		# allow from your_ip
			allow from 66.249.64.0/19 # Used by User-Agents 'apps-spreadsheets' & 'Feedfetcher-Google'
	allow from 66.249.80.0/20 # Used by User-Agents 'apps-spreadsheets' & 'Feedfetcher-Google'		allow from 66.249.80.0/20 # Used by User-Agents 'apps-spreadsheets' & 'Feedfetcher-Google'
	allow from 64.233.160.0/19 # Used by 'GoogleApps' UA		allow from 64.233.160.0/19 # Used by 'GoogleApps' UA

T6nnp6nn at 10:04, 4 April 2016

2016-04-04T10:04:48Z

← Older revision		Revision as of 12:04, 4 April 2016
Line 1,308:		Line 1,308:

	?>		?>
			</syntaxhighlight>

			=Force HTTPS only for admins (not survey takers) with .htaccess=
			Add this to your .htaccess in the Limesurvey installation folder.
			And replace the myLimeFolder and domain name to whatever you have repecively.
			<syntaxhighlight lang="html" enclose="div">
			# ALL ADMIN TO SSL
			RewriteCond %{SERVER_PORT} 80
			RewriteCond %{REQUEST_URI} myLimeFolder/index.php/admin
			RewriteRule ^(.*)$ https://myserver.com/myLimeFolder/index.php/admin/$2 [R,L]
	</syntaxhighlight>		</syntaxhighlight>

Ben V: /* Import & show data into a Google Drive Spreadsheet */

2016-03-01T10:29:39Z

Import & show data into a Google Drive Spreadsheet

← Older revision		Revision as of 12:29, 1 March 2016
Line 1,219:		Line 1,219:


	=Import show data into a Google Drive Spreadsheet=		=Import & show data into a Google Drive Spreadsheet=

	''Tested with: LS >= 2.05''		''Tested with: LS >= 2.05''
Line 1,253:		Line 1,253:
	- Please edit variables for db credentials and survey id ($sid)		- Please edit variables for db credentials and survey id ($sid)
	*/		*/
			header('Content-type: application/xml; charset=utf-8');
	header('Content-~~Type~~: ~~text~~/~~html~~; charset=~~iso~~-~~8859-1~~');		header ('X-Robots-Tag: none', true);
	header('~~Content~~-~~type~~: ~~application/xml~~');

	// Fetch database credentials (much better outside the wwww root directory)		// Fetch database credentials (much better outside the wwww root directory)
Line 1,275:		Line 1,274:
	// Start XML output		// Start XML output

	echo "<?xml version='1.0' encoding='~~iso~~-~~8859-1~~'?>";		echo "<?xml version='1.0' encoding='utf-8'?>";
	echo "<answers>";		echo "<answers>";

Ben V: /* Import show data into a Google Drive Spreadsheet */

2016-02-29T13:47:41Z

Import show data into a Google Drive Spreadsheet

← Older revision		Revision as of 15:47, 29 February 2016
Line 1,230:		Line 1,230:


	To protect your XML file(s) from direct access you can put them in a dedicated folder and use a .htacess file to limit the access exclusively to Google Apps web crawlers		To protect your XML file(s) from direct access you can put them in a dedicated folder and use a .htacess file to limit the access exclusively to Google Apps web crawlers filtered by ip ranges

	<syntaxhighlight lang="html" enclose="div">order allow, deny		<syntaxhighlight lang="html" enclose="div">order allow, deny
Line 1,244:		Line 1,244:
	PHP (XML output) file sample.		PHP (XML output) file sample.

	~~This~~ php file will generate an XML ~~file showing~~ ID, STARTDATE and STARTLANGUAGE values of a survey.		The following php file will generate an XML view printing ID, STARTDATE and STARTLANGUAGE values of a survey.

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

Ben V: /* Import show data into a Google Drive Spreadsheet */

2016-02-29T13:36:50Z

Import show data into a Google Drive Spreadsheet

← Older revision		Revision as of 15:36, 29 February 2016
Line 1,242:		Line 1,242:


	PHP (XML ~~outout~~) file sample.		PHP (XML output) file sample.

	This php file will generate an XML file showing ID, STARTDATE and STARTLANGUAGE values of a survey.		This php file will generate an XML file showing ID, STARTDATE and STARTLANGUAGE values of a survey.

Ben V: /* Import show data into a Google Drive Spreadsheet */

2016-02-29T13:35:25Z

Import show data into a Google Drive Spreadsheet

← Older revision		Revision as of 15:35, 29 February 2016
Line 1,256:		Line 1,256:
	header('Content-Type: text/html; charset=iso-8859-1');		header('Content-Type: text/html; charset=iso-8859-1');
	header('Content-type: application/xml');		header('Content-type: application/xml');
	~~header ('X-Robots-Tag: none', true);~~

	// Fetch database credentials (much better outside the wwww root directory)		// Fetch database credentials (much better outside the wwww root directory)