I have a Maginot static profile set up to build articles in folders whose name is based on a customfield. The "folder" setting in the Maginot static profile looks like this:
- Code: Select all
/path/to/www/files/<Field: CustomField_medlemsnett_kategori>
CustomField_medlemsnett_kategori is a drop-down box with 4 possible values: Ã…rsregnskap, Protokoll, Regnskap or Info-skriv
Now, the problem is the following: I've set the chmod setting in the profile to 644. The profile builds php files, and they won't run on my webserver unless chmodded to 644. BUT, Maginot also changes the permissions on the folders themselves (rsregnskap/, Protokoll/ etc.) to 644.
This is a rather useless chmod setting for a folder, and inevitably, at the next full rebuild, leads to this:
- Code: Select all
An error has occurred. The exact description of the error is:
Unable to open /path/to/www/files/Info-skriv/Info-skriv_nummer_1.php. Permission denied at crcore.pl line 281.
Parahead? Anyone? How can I stop Maginot from chmodding the folders it creates to the same as the files?
[EDIT]: Of course, I've tried manually chmodding the folders to 755 - but Maginot keeps changing them back to 644.[/EDIT]