Welcome, Guest
Username: Password: Remember me

TOPIC: new config files in version 2.0+

new config files in version 2.0+ 1 year 9 months ago #92834

  • lorenzov
  • lorenzov's Avatar
  • OFFLINE
  • Fresh Lemon
  • Posts: 6
  • Karma: 0
hi guys

hi guys, i have a quick query and i don't know whether it is a bug or not. i was used to limes 1.92 and the structure/options of the config.php there.

i have just done an installation of limes 2.0+ and after looking at the config files it looks like the samples config are not clear with the docs not helping much, therefore maybe you can help me clarify things.

in the latest build
- the config-defaults has the same format as the old 1.9 distribution
- the config-sample-mysql looks identical to the config.php created after installation

from the comments in the files ithink i understood that the new options should be added to the array in the config.php where the config array is set, i.e. lines 61-70
// Use the following config variable to set modified optional settings copied from config-defaults.php
	'config'=>array(
	// debug: Set this to 1 if you are looking for errors. If you still get no errors after enabling this
	// then please check your error-logs - either in your hosting provider admin panel or in some /logs directory
	// on your webspace.
	// LimeSurvey developers: Set this to 2 to additionally display STRICT PHP error messages and get full access to standard templates
		'debug'=>0,
		'debugsql'=>0, // Set this to 1 to enanble sql logging, only active when debug = 2
		'shownoanswer' => 2,
		'memory_limit' => '64',
		'maxemails'    => 100,
		'defaulthtmleditormode' => 'inline'
	)

but it doesn't look it is doing anyhing

is this something not yet implemented or am i looking in the wrong places?

many thanks! (and happy to add this info for those upgrading in the wiki)

lorenzo
The administrator has disabled public write access.

new config files in version 2.0+ 1 year 9 months ago #92943

  • DenisChenu
  • DenisChenu's Avatar
  • OFFLINE
  • Moderator Lime
  • Posts: 6551
  • Thank you received: 869
  • Karma: 257
Hello,

Some of config-default.php are now in global LimeSurvey setting.

It's shownoanswer, shownoanswer,maxemails,defaulthtmleditormode .

For memory_limit, think it work, but maybe a bug or your hoster don't allow you more memory.

Denis
The administrator has disabled public write access.

new config files in version 2.0+ 1 year 9 months ago #92945

  • lorenzov
  • lorenzov's Avatar
  • OFFLINE
  • Fresh Lemon
  • Posts: 6
  • Karma: 0
hi Denis, many thanks for the reply. so, where are the 'global settings' now? are my code and location correct?

the default config only has these two, the rest is what i added, but not sure whether the format is correct:
'debug'=>0,
'debugsql'=>0, // Set this to 1 to enanble sql logging, only active when debug = 2

thanks

lorenzo
The administrator has disabled public write access.

new config files in version 2.0+ 1 year 9 months ago #92952

  • DenisChenu
  • DenisChenu's Avatar
  • OFFLINE
  • Moderator Lime
  • Posts: 6551
  • Thank you received: 869
  • Karma: 257
Your code and location are correct.

For global seting, in survey admin : 1st menu bar.
The administrator has disabled public write access.
The following user(s) said Thank You: lorenzov

new config files in version 2.0+ 1 year 9 months ago #92955

  • lorenzov
  • lorenzov's Avatar
  • OFFLINE
  • Fresh Lemon
  • Posts: 6
  • Karma: 0
brilliant thanks, i actually didn't see at all the icon with the global settings!

one thing to report is that if these are coded in the array in the config (i.e. when one is upgrading from an older version), the front-end doesn't actually pick them up. it is easy to fix by manually changing them, but perhaps it should be flagged in the upgrade info.
The administrator has disabled public write access.

new config files in version 2.0+ 1 year 9 months ago #92965

  • DenisChenu
  • DenisChenu's Avatar
  • OFFLINE
  • Moderator Lime
  • Posts: 6551
  • Thank you received: 869
  • Karma: 257
lorenzov wrote:
one thing to report is that if these are coded in the array in the config (i.e. when one is upgrading from an older version), the front-end doesn't actually pick them up. it is easy to fix by manually changing them, but perhaps it should be flagged in the upgrade info.
Good information.

But some config are already in database in 1.92, 1.92 take the config.php.

Then we need for each global config:
- Find it's in database,
- if not : find if it's config.php and take it from this.

Please, can you do a bug report ?

Denis
The administrator has disabled public write access.
Moderators: ITEd
Time to create page: 0.209 seconds
Donation Image