| Author |
Message |
nukeIT
New Member
Joined: Jun 04, 2005
Posts: 1
|
 Posted:
Sat Jun 04, 2005 12:59 pm |
 
|
PHPNuke 7.6
Sentinel 2.2.1
Upon installation I changed the name of my Nuke admin.php file hoping it will add an extra layer of security but I didn’t realize how much of an extra layer of frustration it would also create. Nuke is working great but trying to install Sentinel has been quite a challenge.
The problems I am having may or may not be related to the admin.php name change.
Can someone tell me exactly what I should modify in Sentinel when changing the name of Nuke’s admin.php? I think I've renamed everything correctly but I want to eliminate the renaming issue before going on with my debugging. |
|
|
|
|
Raven
Site Admin/Owner
Joined: Aug 27, 2002
Posts: 16987
Location: Kansas
|
| Posted:
Sat Jun 04, 2005 1:28 pm |
|
If you are using NukeSentinel(tm) with admin blocking on there is no need or purpose served in renaming $admin_file. Name it back and make it easy on yourself  |
|
|
  
|
|
Manuel
Regular
Joined: May 28, 2005
Posts: 90
|
| Posted:
Sun Jun 05, 2005 6:02 am |
|
and in nuke 7.6 if you change the $admin_file you will find many errors in administrations because FB forget to add this vars and there is still admin.php !
|
|
|
 |
|
|
|
|
|
![[Valid RSS]](http://www.ravenphpscripts.com/images/valid-rss.png "Validate my RSS feed"){kind=small}
:: 
::
