This problem is somewhat related to the "No such file or directory" message. It is actually a message originating from Perl and not Coranto itself, but Coranto provides a framework for dealing with files and the specific line that tries to open the file is located at that line in that file (the actual line number can differ depending on Coranto version). The thing is that it isn´t really that line of code that has some kind of error in it, or any other line of code either for that matter, it is just that the file that Coranto is trying to open doesn´t have the right privileges to be opened by the user running the script.

And by "the user running the script" I don´t mean the user that is logged into Coranto, but a user account on the physical server that the webserver is running under. That can either be the same user you use when you FTP to the server or a more generic user like "www", depending on how things are set up at your specific server.

The root of this problem is probably caused by the chmod settings not being what they should be, so FTP to your server and verify what the chmod settings currently are for this file. The procedure to see the privileges for a file is different amongst the FTP clients, so you have to refer to the documentation for your specific program, but look for a column named Rights or view Properties for the file or something similar.

Normal settings would be something like 777, 755, 700 or 666. Depending on if it is the same user that you FTP to the server as that also is executing Coranto or if it is a more generic user like "www" you need to have read/write privileges for both the Owner and the Group. If in doubt, ask your host what chmod settings a file that must be read by a webscript should have. A common problem is that you have uploaded a file to the server and the chmod settings are set to only allow read/write for the Owner, so that when Coranto executes as "www" it accordingly doesn´t get access to files.

If you know that the file having this problem is being generated from Coranto when doing a full rebuild you could try and delete the file (make a backup of it first!) and then do a full rebuild to see if the file is recreated with the appropriate owner and chmod settings.

If you still can´t figure out why this file can´t be opened post a message in the forum, stating that you have read this document and explain what measures you have taken thus far to pinpoint the problem.