Parse error: syntax error (…) wp-config.php on line 35 – how to solve it?
-
Hi,
I’ve I got 1 WP site and I wanted to test making backup copies for WP. I have SQL file and normal files downloaded to my hard drive from my WP website.
To test making WP copies I used those files to make a one copy on my local server and one copy on my on web server. It works fine on local server, but I have problem with web server.
After I changed ‘wp-config.php’ and the URL in ‘wp-options’ Table I got an error:Parse error: syntax error, unexpected ',' in /profiles/t/to/tom/tom1/MyWebPage.com/wp-config.php on line 44
I know this means something is wrong in ‘wp-config.php’ file in line 44, but I don’t know what to do with it.
Here is the content of my wp-config.php file (I put ‘x’ in table name, user, password, host to hide data):
<?php define('DB_NAME', 'x'); define('DB_USER', 'x'); define('DB_PASSWORD', 'x' ); define('DB_HOST', 'x'); define('DB_CHARSET', 'utf8mb4'); define('DB_COLLATE', ''); define('AUTH_KEY', 'st>YRiR+K2!{Z!N%-P/evR7-o>KKDS%$81S3N!NnG<[39oYVhxm!+c}t[(2:~hki'); define('SECURE_AUTH_KEY', '|S|:0x=zlpP )ieIm?0^tc/iMxFG-,[TxVjPe+[Hkd*z<|.-;c+4FsD3Y|-z@7'); define('LOGGED_IN_KEY', '+a.Ugfpn%5h(W[0)Q|WH_1bg}gY!6.<code>YwgHPdbg</code>pn}j@(IM~rz+NGFCXGx%5~XR'); define('NONCE_KEY', '~7<w(p3q^6&P}0fc=ApvjYhiv?wJc6zQ2Ct|*{t%rIv,=/|{F1mlWne3>=a+jGe'); define('AUTH_SALT', 'f/E{pZ}xBt]_J+?D;%L-v9]aU[[{OXi)4_d&xy_Vw@&8|WQo/#7b^%#R_Zo88U&'); define('SECURE_AUTH_SALT', '()VFE*UMi<h=1yk(h0cjMjmPMz/sL- F]NK^ZTBEIpr l-x}dhg)M{mU4Ivf6i~>'); define('LOGGED_IN_SALT', 'X<code>$qRmP?xHu/</code>fh|Rc9qu0(H3:6]&&/aD6KP(z7Qc3)XOe}kzo4z?f.2PCzoX$&K'); define('NONCE_SALT', '-L!n0yG[tjR%^&AL2}Kpov%gZL%~T-1 <65op(Y=bhob+<EnGorZHKV9(Ib=&NH'); $table_prefix = 'wp_'; define('FS_METHOD', 'direct'); define('WP_DEBUG', false); if ( !defined('ABSPATH') ) define('ABSPATH', dirname(__FILE__) . '/'); require_once(ABSPATH , 'wp-settings.php');
Anyone can help? Sorry about the way the code looks, but I can’t change it.
- The topic ‘Parse error: syntax error (…) wp-config.php on line 35 – how to solve it?’ is closed to new replies.