Unable to open .../news/. Is directory at crcore.pl line292

[steve bozz]

OK, here's another plea for help. I am now running 1.11 and the new error looks like this.

Basically, this error doesn't effect ANYTHING, it's just a nuisance. It looks like it's trying to call up a directory with a trailing slash. No where in my coranto settings is this set up to do so. So there must be something in a file somewhere that needs to be changed to stop looking for this directory. Obviously this line 292 is a starting point.

Can anyone point me to where I should be making some edits, where line 292's variables refer to?

I want to get rid of this so my contributors don't freak out when submitting things.

Also please see the following threads for other suggestions that I have tried:

http://coranto.org/forum/viewtopic.php? ... highlight=
and
http://coranto.org/forum/viewtopic.php? ... highlight=

Thanks for your help

An error has occurred. The exact description of the error is:
Unable to open /home/www/rockzone/news/. Is a directory at crcore.pl line 292.

If this error indicates a problem that you don't know how to solve, see the Coranto documentation and FAQ. If these resources don't help, make a (detailed!) post to the Coranto Forum.


--------------------------------------------------------------------------------

USEFUL INFORMATION

Perl may have generated the following error: Is a directory
Perl Version: 5.006
Script Version: 1.11
Script Build: 36
Script RC: 0
Script URL: http://www.rockzone.com/cgi-bin/coranto/coranto.cgi
@INC:
/usr/lib/perl5/5.6.0/i386-linux
/usr/lib/perl5/5.6.0
/usr/lib/perl5/site_perl/5.6.0/i386-linux
/usr/lib/perl5/site_perl/5.6.0
/usr/lib/perl5/site_perl
.
/home/rockzone/www/cgi-bin/coranto
Script Location (Method 1): coranto.cgi
Script Location (Method 2): /home/www/rockzone/cgi-bin/coranto

ENVIRONMENT VARIABLES
QUERY_STRING:
SERVER_ADDR: 216.71.167.210
CONTENT_TYPE: application/x-www-form-urlencoded
HTTP_ACCEPT_LANGUAGE: en-us
SERVER_PROTOCOL: HTTP/1.1
HTTP_CONNECTION: Keep-Alive
HTTP_REFERER: http://www.rockzone.com/cgi-bin/coranto/coranto.cgi
REMOTE_PORT: 33481
HTTP_USER_AGENT: Mozilla/4.0 (compatible; MSIE 6.0; Windows 98; Q312461; .NET CLR 1.0.3705; .NET CLR 1.1.4322)
HTTP_ACCEPT: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/vnd.ms-excel, application/msword, application/vnd.ms-powerpoint, application/x-gsarcade-launch, */*
GATEWAY_INTERFACE: CGI/1.1
HTTP_HOST: www.rockzone.com
SERVER_SOFTWARE: Apache
SERVER_ADMIN: webmaster@rockzone.com
REMOTE_ADDR: 68.198.89.152
SCRIPT_NAME: /cgi-bin/coranto/coranto.cgi
SERVER_NAME: www.rockzone.com
HTTP_ACCEPT_ENCODING: gzip, deflate
DOCUMENT_ROOT: /www/rockzone
REQUEST_URI: /cgi-bin/coranto/coranto.cgi
REQUEST_METHOD: POST
CONTENT_LENGTH: 150
SCRIPT_FILENAME: /www/rockzone/cgi-bin/coranto/coranto.cgi
PATH: /usr/local/bin:/usr/bin:/bin
SERVER_PORT: 80
HTTP_CACHE_CONTROL: no-cache

MESSAGE: Unable to open /home/www/rockzone/news/. Is a directory at crcore.pl line 292.

[cerberos76_]

this looks tp me a setting problem. You must have a profile which is trying to write a file using an empty field. Are you using Maginot? If so, check VERY carefully one by one your profiles and the field that is set as the filename.

If you are absolutely sure, then simply make a NEW installation of the coranto program, start posting news from this blanck version and see if the error repeats. If not (as I think) then start adding addons to this new installation one at a time and retry building. If still works start adding styles and profiles etc... You will see when and where is the error!

[steve bozz]

OK, all the settings are fine.
This *is* a new installation to try and get the bugs out. I got the errors once when I tried to add headlines to a profile, then I chmoded things back to 777 and all was well. When I added archives to another profile, things were back to errors and I haven't seen a regular working coranto since.

Apparently the behavior that is occuring is the following.

I'll CHMOD the /news directory to 777, and all the files inside to the same permission. Then I'll run a regular rebuild and I just get my usual error. If I run a FULL Rebuild I get the following:

Unable to open /home/www/rockzone/news/EpVluyVVEykMPeorpN.php. Permission denied at crcore.pl line 292, <FH> line 2.

When I go to check my permissions, I get Permission Denied when entering the /news directory. I have to reset the permissions back to 777.

What the @#$ is going on here?

Steve

[steve bozz]

and support chimes in with this:

Response: Hello,

When does the directory permission changing actually happen? It sounds like it occures when you are running this script, and it changes the permission of the news directory to 666. There is nothing running on our end that would purposely change the permissions on your news directory to 666. I also noticed alot of your ikonboard directories in the cgi-bin are chmod'd to 666. Does it in any way link to the news directory? I hate to say it, but it sounds like a script problem, as it has to be the one changing permissions.

If you need my further assistance, let me know.

Regards,
Yuri
Support

[Lawrence]

Hey guys, are you using Maginot by any chance??

I think Maginot changes file permissions to 666 when it creates a file for a news item, so if it is used in conjunction with my email addon ( which prevents it from creating the file, a known bug but near impossible to fix right now ), it's possible the chmod command is Maginot is being passed the directory name ( due to the above conflict ) and changing it's permissions.

Just a idea, anyways

[cerberos76_]

Hi,
my suggestion was to try it out with a clean install and NO addons... so to be sure the script works first and then enable addons one at a time to find the problem out.

If you are sure your problem is the 666 permission, than check inside maginot lines like:

chmod(0666, "....

and change to:

chmod(0777, "....

[steve bozz]

thanks for the maginot code change idea.. that has fixed one of the problems related to permissions. but still the same error. i guess i'll have to try a third re-install and try making a headline or archive profile... that's what seems to have caused this problem