Hello everyone,

I've a database prefix in my DB and config file

'Enq_'

My server keeps reporting

mod_fcgid: stderr: PHP Notice: Use of undefined constant 'Enq_' on row 40 configfile

How to fix this?

Can I update the database so thats there is no prefix and keep this empty?

I can't keep it empty now because then it won't recognize the database and ask to roll out the tables in the DB

Thanks

Rem

Please put the complete content of you config file. Surey some broken things.

(remove the password).

Denis

hi denis,

This is my config file (db part)

$databaselocation = 'localhost'; // Network location of your Database - for odbc_mssql or mssqlnative use the mssql servername, not localhost or IP
$databasename = 'name of db'; // The name of the database that we will create
$databaseuser = 'name of user'; // The name of a user with rights to create db (or if db already exists, then rights within that db)
$databasepass = 'password db’; // Password of db user
$dbprefix = 'enq_'; // A global prefix that can be added to all LimeSurvey tables. Use this if you are sharing
// a database with other applications. Suggested prefix is 'lime_'

Thanks for looking at it

Rem

It's an old version of LimeSurvey ? Rigth ?

But here, i think we can't help : Use of undefined constant 'Enq_' on row 40 configfile
I think it's not the config file of LimeSUrvey, but a config file somewhere in your host/server.

Denis

Denis
It's a old version

But in the error log I see this?


Use of undefined constant enq_ - assumed 'enq_' in /var/www/vhosts/domainname/httpdocs/enquete/config.php on line 40, referer: www.domainname.nl/enquete/index.php


So in my folder "enquete" where the installation of LS is done, gives the error

You have enq_ somewhere in your config.php file without quote.

Look at ir, it's not a LS issue.

Will have a look Denis.
Thanks!

If you can't find the problem take the original config.php file and try adjusting it again.

Also note that changing the prefix at the config.php file of a running system will not lead to your DB being updated but will probably cause a DB connection problem.