Forums / Developer / Failed writing to override.ini.append.php.tmp

Failed writing to override.ini.append.php.tmp

Author Message

Eirik Alfstad Johansen

Thursday 13 July 2006 2:52:11 am

Hi,

I have a site (v. 3.7.5) where I'm unable to add new template overrides from within the admin interface.

When I try to do so, no template is added to the list. However, if I browse the override/templates folder of the site design associated with the selected siteaccess, I can see that the file is created. This must mean that there's some problem writing to the override.ini.append.php.

Also, if I manually add the text that's supposed to go into override.ini, and then try to delete the override from the admin interface, the actual template file is deleted, but the text in override.ini remains, and I get the following error msg (loosly translated from Norwegian):

===
The overrides could not be removed

The file override.ini could not be edited due to inadequate access to the file.
===

The file permissions are 777, so there should be no problem there.

However, when I turn on debugging, I get an interesting additional msg:

===
Error: eZINI
Failed opening file 'settings/siteaccess/main/override.ini.append.php.tmp' for writing
===

Where does the .tmp extension come into play? I've seen the override.ini.append.php being duplicated and a tilde (~) added to the file name before, but never "tmp".

Any ideas are greatly appreciated. Thanks in advance !

Sincerely,

Eirik Alfstad Johansen
http://www.netmaking.no/

Patrick Kaiser

Thursday 13 July 2006 4:33:00 am

have no clou why the .tmp file is created..
but - although this is obvious - have you checked if the webserver has the right to create (new) files within the settings/siteaccess/main/ directory? check the permissions of the ../main/ folder.

best regards,
patrick


Best regards,

Patrick

Eirik Alfstad Johansen

Thursday 13 July 2006 5:24:35 am

Hi Patrick,

[quote]
but - although this is obvious - have you checked if the webserver has the right to create (new) files within the settings/siteaccess/main/ directory? check the permissions of the ../main/ folder.
[/quote]

Yes, one would think that would be obvious. :)

You are, of course, entirely correct. Changing permissions for the main/ dir resolved the issue.

Thanks for clearing up my confusion !

Sincerely,

Eirik Alfstad Johansen
http://www.netmaking.no/