upgrading to 1.2.0

Hangin' Around Joined: Apr 14, 2004 Posts: 26

hi

because in readme.txt of 1.2.0 version of sentinel, doesn't says about upgrading from 1.1.0 to 1.2.0, will we follow the upgrade "method" from 1.0.0 to 1.1.0 ?

Quote:

UPGRADING from Sentinel(tm) 1.0.0:
1) Upload all files and run nsnst.php .
2) From nsnst.php select the upgrade Sentinel(tm) 1.0.0 to 1.1.0 .
3) Goto Sentinel(tm) configuration and adjust your settings as needed.

or we don't have to overwrite all the old files with the new?

Thanks

New Member Joined: Jun 04, 2004 Posts: 13

I have overwritten all the files, copied over nsnst.php - then used the upgrade 1.1.0 tables to 1.2.0 tables option in there; it went all OK - upgrading is a breeze Smile

registered · Posted: Fri Jun 04, 2004 7:17 am

Sorry, you do the same things as from 1.0.0 to 1.1.0 but when you run nsnst.php you select the 1.1.0 to 1.2.0 option for upgrading.

Regular Joined: Aug 22, 2003 Posts: 84

Why is the .Httaccess file in NSN_Sentinel_120\html\abuse and not in
NSN_Sentinel_120\html\ Root?

only on Apache servers -------------> root/.htaccess (CHMOD 666)

Er, for us total noobs, I had replaced my .Htaccess in Root with the one supplied in version 1.

Is version 2 using it in the abuse folder?

www.pagename.com/abuse/.httacess ?
Confused

Also, Do I Have to upgrade?

I dont want to.

Laughing

Posted: Fri Jun 04, 2004 4:30 pm

The .htaccess file you are refering to is meant only to allow blocked ip to see the popups once they are blocked.

Site Admin/Owner Joined: Aug 27, 2002 Posts: 17088

Someone had asked me this in a PM also. Just for clarification, the one that comes with Sentinel™ is in the correct folder (abuse). Apache allows you to have individual .htaccess files in every folder, if you desire, for various levels of control. Sentinel™ will create or add to your root .htaccess only if you are blocking access at the server level.