configure.php file warning

[Sabkor]

Just wondering about this error, I browsed all the FAQ stuff and several of the threads on here about it. Attached here is my output from SSH:

shell2c25:/public/store/includes$ ls -l
total 124
-rw-r--r-- 1 .ca web 781 Nov 28 20:25 application_bottom.php
-rw-r--r-- 1 .ca web 4421 Nov 28 20:25 application_top.php
drwxr-sr-x 3 .ca web 4096 Nov 28 20:25 auto_loaders
-rw-r--r-- 1 .ca web 3905 Nov 28 20:25 autoload_func.php
drwxr-sr-x 5 .ca web 4096 Nov 28 20:25 classes
-r--r--r-- 1 .ca web 3211 Nov 28 22:50 configure.php
-rw-r--r-- 1 .ca web 2161 Nov 28 20:25 counter.php
-rw-r--r-- 1 .ca web 5909 Nov 28 20:25 database_tables.php
drwxr-sr-x 2 .ca web 4096 Nov 28 20:25 extra_cart_actions
drwxr-sr-x 2 .ca web 4096 Nov 28 20:25 extra_configures
drwxr-sr-x 2 .ca web 4096 Nov 28 20:25 extra_datafiles
-rw-r--r-- 1 .ca web 9218 Nov 28 20:25 filenames.php
-rw-r--r-- 1 .ca web 5092 Nov 28 20:25 form_check.js.php
drwxr-sr-x 3 .ca web 4096 Nov 28 20:26 functions
-rw-r--r-- 1 .ca web 5642 Nov 28 20:26 general.js
-rw-r--r-- 1 .ca web 111 Nov 28 20:26 index.html
drwxr-sr-x 2 .ca web 4096 Nov 28 20:26 index_filters
drwxr-sr-x 3 .ca web 4096 Nov 28 20:26 init_includes
drwxr-sr-x 4 .ca web 4096 Nov 28 20:27 languages
-rw-r--r-- 1 .ca web 2170 Nov 28 20:27 main_cart_actions.php
drwxr-sr-x 9 .ca web 4096 Nov 28 20:31 modules
-rw-r--r-- 1 .ca web 4607 Nov 28 20:31 spiders.txt
drwxr-sr-x 4 .ca web 4096 Nov 28 20:31 templates
-rw-r--r-- 1 .ca web 975 Nov 28 20:33 version.php
shell2c25:/public/store/includes$


As you can see, the configure file is read-only for all. However, I'm still getting the error that the file is writable. I used the ultra-secret method to disable the message, but was just wondering if someone would have any idea why this would happen? I was thinking of writing a temporary .PHP script that would actually try to write to this file and see if it gets overwritten or not (after backing it up of course).

General Information:
First time install, first time user
Zen Cart v1.3.7.1
PHP v5.2.4

[Ajeh]

On some servers, they do not read these correctly or report them back right ...

If you are absolutely positive that that file is safely locked down, you could remove the message (as you said you did) ...

You might try this:

First, backup the file, delete the file from the server ...

Load the file back to the server ...

via your Control Panel for your domain, change it to 444 ...

Or it could just be the way your host has PHP configured.

[Sabkor]

I think it must be some wierd PHP configuration... I'm not going to let it worry me, I think. I wrote the PHP script to attempt to actually write to the file and could not. Here's the script:

<?php
$filename = 'includes/configure.php';

if (is_writable($filename))
	echo "File appears to be writable<br>";
else
	echo "File is NOT writable<br>";
	
if (!$handle = fopen($filename, 'w')) {
    echo "Cannot open file ($filename)<br>";
} else {
	if (fwrite($handle, "Just a test") === FALSE) {
    echo "Cannot write to file ($filename)<br>";
	} else {
		echo "Success, wrote  to file ($filename)<br>";
	}
	fclose($handle);
}

$filename = 'includes/configure2.php';

if (is_writable($filename))
	echo "File appears to be writable<br>";
else
	echo "File is NOT writable<br>";
	
if (!$handle = fopen($filename, 'w')) {
    echo "Cannot open file ($filename)<br>";
} else {
	if (fwrite($handle, "Just a test") === FALSE) {
    echo "Cannot write to file ($filename)<br>";
	} else {
		echo "Success, wrote  to file ($filename)<br>";
	}
	fclose($handle);
}
?>

and here was the output:

File appears to be writable
Cannot open file (includes/configure.php)
File appears to be writable
Success, wrote to file (includes/configure2.php)


Looking at the actual files, it was able to write to the configure2.php that I created to test in that folder, but was not able to actually write to the configure.php file. So I'm guessing I probably have nothing to worry about, just some weirdness on the web-server end.

[lakotasouix]

You might try this:

First, backup the file, delete the file from the server ...

Load the file back to the server ...

via your Control Panel for your domain, change it to 444 ...

Or it could just be the way your host has PHP configured.

I had the same problem and this worked for me.

[Ajeh]

Thanks for the update that this method was able to help you as well ...

[time111]

without backing up, deleting from server, then reuploading, not require, just change permission from file manager in control panel to 444 and it will work.

~ Time