This is caused by a bad line of code that is missing code like } or ;
The parse error always occurs 1 to X lines below the wrong code.
For example, a file named test.php
PHP:
$dbname='test' $uname='foo';
On line 1 it's missing the ; so the error message says
This warning is caused due to how PHP is setup on the server.
PHP is setup to disallow remote connection.
A lot of hosts block the "connect to server" features since there are a lot of badly scripted files.
If someone uses such bad scripts it could open security holes which are mentioned all over the place.
We can't fix it since it's server related.
What you can do is one of the following options:
- turn off the feature in cpg-nuke
- ignore the message
- switch hosts
Please enable cookies to post on this site. If you feel you have reached this message in error please refresh the preceding page once and post again
This could be several things:
A) There's a wrong cookie domain and path setup
B) Server admin has setup php.ini to auto-register a session.
You can check this thru the following script
PHP:
<?php error_reporting(E_ALL); session_name('CMSSESSID'); session_start(); session_register('installtest'); if (!isset($_SESSION['installtest'])) $_SESSION['installtest'] = 0; $_SESSION['installtest']++; echo 'This page is accessed: '.$_SESSION['installtest'].' time(s)';
Then a notice should be shown
Quote:
Notice: A session had already been started - ignoring session_start()
C) session.save_path is not accessible (open php.ini to fix)
D) Somehow you're not allowed to write to the session.save_path so:
Open config.php and find
[php]//session_save_path('/home/SOMETHING/tmp');[/php]
Change to something like
[php]session_save_path('/home/SOMETHING/tmp');[/php]
Be sure /home/SOMETHING/tmp is writeable (chmod 777 if necesary)
E) Editing incorrectly can result in "headers already sent" errors which cause problems for cookie handling.
This could happen if, for example, a file was edited and saved with a Byte Order Mark, which could easily occur when editing our files in Windows Notepad. Use Notepad 2 or any other true code editor with UTF-8 support. Note: in Notepad++ (3.8) you must not choose the format "Encode in UTF-8". You must choose "Encode in ANSI" combined with "UTF-8 without BOM".
All content of this website is copyrighted by the Creative Commons NC-SA
The logos and trademarks used on this site are the property of their respective owners We are not responsible for comments posted by our users, as they are the property of the poster. Our server runs on a P3 1.2GHz with 512MB RAM with no accelerators
This page generated in 0.118 seconds with 8 DB Queries in 0.0162 seconds Memory Usage: 1.5 MB
Interactive software released under GNU GPL,
Code Credits,
Privacy Policy
