Limiting NukeSentinel's Protection

Posted: Tue Apr 25, 2006 7:54 pm

Hey all,

I'm trying to setup a few subdomains running non-Nuke scripts and the one I was playing with last night had an "admin.php" file included with it that NukeSentinel was blocking me from. This isn't even part of PHP-Nuke. It's in it's own folder 2 layers deeper than Nuke.

Short of renaming the files, is there any way to limit NukeSentinel to just the root directory's files?

Actually the more I think about it now, the more it doesn't make sense......mainfile.php was not even running. NukeSentinel should not have even been called upon. I was accessing the script directly 2 folders deeper than Nuke. No Nuke files were even running but yet I was being prompted by NukeSentinel.

Any ideas?

registered · Site Admin Joined: Jun 04, 2004 Posts: 6437

Not really, since the .htaccess directives you're probably using go all the way down.

However, if you're using version 7.6 or higher, you can easily rename your Nuke admin.php file - make sure to change the config.php (I think that's where it is). Not sure what you'd need to do in Sentinel before that, but you might need to manually change the .htaccess file, too.

Posted: Wed Apr 26, 2006 5:18 am

Weird. Ok, thanks.

And I tried that renaming the admin file trick a while back and everything blew up. Smile

registered · Posted: Wed Apr 26, 2006 6:35 am

As kguske is eluding to, you might try in the directory down deeper, where you have the other admin.php, adding a .htaccess file with something like:

allow from all

And then see if that helps it.

Posted: Wed Apr 26, 2006 8:39 pm

Good point, montego. That might be easier than renaming the admin.php file from Nuke...