This issue has occurred since I upgraded my server from redhat 6.2 to 7.2.

I ran into lots of permission errors, and after fixing about a dozen of them (permissions set wrong), I came across this one, on the first links directory it tries to build (on 'Build All').

------

CGI ERROR
==========================================
Error Message : unable to open category page: /home/httpd/html/links/pages/Humor_and_Parody/index2.html. Reason: Permission denied
Script Location : /home/httpd/cgi-bin/links/admin/nph-build.cgi
Perl Version : 5.006

-------

Now, I checked in Humor_and_Parody, and index2.html didn't exist, only index.html. The directory has proper permissions, 777, as do the /home/httpd/html/links and links/pages directories.

Then I checked nph-build.cgi, and found out the script shouldn't even be trying to open any index2.html files. It should only be trying to open index.html.

So, all the permissions are fine, and it shouldn't even be trying to open that file in the first place, and even when I create the file and change it to 666 permissions it STILL gives that error, I'm compeltely baffled.

Anyone got any ideas? Help!! :)

Did you try this command?

chmod -R 666 /home/httpd/html/links/pages

It seems that you have change the permission of the index file but the directory contains that file.

Cheers,

Dat

Programming and creating plugins and templates
Blog

Yes, all the files AND the directories have proper permissions, all the directories are set to 777.

Have you applied any MODS or code hacks to your LINKS 2.0?
========================================
Buh Bye!

Cheers,
Me

No, none at all.

Try replacing your nph-build.cgi script with the original one that came with the Links 2.0 download.
========================================
Buh Bye!

Cheers,
Me

It is the original. It's never been modified, hacked, or changed in any manner.

Really?

Have you used index2.shtml as your index file in the links.cfg file? Because index2.shtml should not appear unless you configured it in the links.cfg file -OR- if you have hacked the nph-build.cgi script.
========================================
Buh Bye!

Cheers,
Me

That's exactly what's so bizarre, it's defined as index.html in links.cfg. Hell I even threw a line into nph-build.cgi right before it comes to that error, defining $build_index as index.html and it still tried to open index2.html.

It's so bizarre and frustrating exactly because of this. It makes no sense. And not only that, all the permissions are set correctly. Argh.

The problem was that the error reported was inaccurate, the file without proper permissions was 'more2.html' not index2.html.

Thanks for your help, everyone.