ALL WORKING EXCEPT... Parse error: parse error, unexpected '

New Member Joined: Nov 16, 2007 Posts: 6

Alright, got the NukeSentinel all installed, it is now writing the .staccess file okay, .htaccess is allowing me in, but...

When I click the NukeSentinel link in my SIDEBAR/left column which opens

and that is how it should be, until I click on the links.

When I click on "Display Blocked IP's" I get the following error:

Parse error: parse error, unexpected ')' in **path remove by admin**/modules/NukeSentinel/public/STIPS.php on line 19

AND

When I click on "Display Blocked Ranges" I get the following error message:

Parse error: parse error, unexpected ')' in **path remove by admin**/modules/NukeSentinel/public/STRanges.php on line 19

When I click on "Blocked Refering Domains" it does show me a list of blocked domains, but...

When I click on the "IP to Country" link, it gives me the following error message:

Parse error: parse error, unexpected ')' in **path remove by admin**/modules/NukeSentinel/public/STIP2C.php on line 18

I guess the question is... HOW DO I FIX THIS????

So far, that's the only problem I have found, everything else seems to work. Assuming the script actually does stop spammers. THAT has yet to be proven.

I'll assume it helps.

registered · Posted: Fri Nov 16, 2007 6:03 pm

ncochise, I removed your full path from your post. You NEVER want to give these out on the internet and we don't need them anyways.

You have posted this in the general NukeSentinel forum so I am not sure what version you are on. Hopefully the latest-and-greatest. If so, the author of NS will have to take a look at this. If I have time this weekend, I can check back here too and see if I can find the issue, but I need the NS version.

BTW, NukeSentinel is not "spam protection" per se. IMO, its main purpose is hack protection. However, yes, some of the blockers / tools can help also reduce different types of spam or harvesting or bad referrers other undesirable activities against your site. Just wanted to make sure you understood that from an expectations standpoint.

Posted: Fri Nov 16, 2007 6:17 pm

Found the FIX for the error addressed below.

When I click the NukeSentinel link in my SIDEBAR/left column which opens

and that is how it should be, until I click on the links.

When I click on "Display Blocked IP's" I get the following error:

Parse error: parse error, unexpected ')' in /**path removed by admin**/modules/NukeSentinel/public/STIPS.php on line 19

***THE FIX: Open the file named STIPS.php and on line 19

FIND THIS...

Code:

if (!isset($min)) { $min=0; } else { $min = intval($min); )

Change it to THIS...

Code:

if (!isset($min)) { $min=0; } else { $min = intval($min); }

and then SAVE the file.

(What you did was change the ) at the end of the line to })

NEXT

When I click on "Display Blocked Ranges" I get the following error message:

Parse error: parse error, unexpected ')' in /**path removed by admin**/modules/NukeSentinel/public/STRanges.php on line 19

***THE FIX: Open the file named STRanges.php and on line 19

FIND THIS...

Code:

if (!isset($min)) { $min=0; } else { $min = intval($min); )

Change it to THIS...

Code:

if (!isset($min)) { $min=0; } else { $min = intval($min); }

and then SAVE the file.

(What you did was change the ) at the end of the line to })

NEXT

When I click on "Blocked Refering Domains" it does show me a list of blocked domains, but...

When I click on the "IP to Country" link, it gives me the following error message:

Parse error: parse error, unexpected ')' in /**path removed by admin**/modules/NukeSentinel/public/STIP2C.php on line 18

***THE FIX: Open the file named STIP2C.php and on line 18

FIND THIS...

Code:

if (!isset($min)) { $min=0; } else { $min = intval($min); )

Change it to THIS...

Code:

if (!isset($min)) { $min=0; } else { $min = intval($min); }

and then SAVE the file.

(What you did was change the ) at the end of the line to })

****** That solved the problem for me. Looks like coder typos using ) when they should have been }

GOOD LUCK!!!!

Posted: Fri Nov 16, 2007 6:41 pm

Montego, thanks! I thought I changed all of those paths before posting... so much for my attention span.

I just installed yesterday the NukeSentinel_2514_66-81.tar.gz version of NS and integrated it into PhpNuke 7.8 with a 3.3 patch and after fighting with the .staccess issue, I finally got everything working except for the TYPOS I found in the code strings I posted in this topic.

Thanks again for your backup in stripping out those paths for me.

I thought I used the same FAUX path I used in the path below, but I guess I LOST TRACK and posted the REAL path.

Parse error: parse error, unexpected ')' in /mounted-storage/sdsdfsfs/sdsdfsdfs/www/MyNukeRoot/modules/NukeSentinel/public/STRanges.php on line 19

OOPS!!! I will keep an eye open for similar mistakes in the future.

Thanks to everyone for all the help!

At 53, none of this comes easy for me.

But I keep TRUDGING ALONG!

Posted: Sat Nov 17, 2007 5:02 am

I thought you had done it again before I read your last post.

In most cases you might as well remove everything before your nuke root, because it is not needed when debugging.

Posted: Sat Nov 17, 2007 5:27 am

It looks like Bob must of made some changes in the latest version because it works on 2.5.13., but not 2.5.14.

Posted: Sun Nov 18, 2007 6:37 am

Humm, I don't use the link in the modules list often. You can view everything that is leading to the error message from the NS admin panel ok. Just not from the modules link to NS.

Posted: Sun Nov 18, 2007 5:12 pm

Not sure if I will use the mod links accessed from the left admin column either, but... I like having ALL of the coding do what it is supposed to do, I'm kinda silly that way.

I don't know if the links to the same mods from inside the NS Admin Console use the same files I listed above with errors, so fixing the errors just made sense to me, in case they were called on by other areas within the script.

Not a coder... just an old man with a Nuke-generated-migraine.

Posted: Mon Nov 19, 2007 6:53 am

Bob is aware of this thread so it should get fixed in 2.5.15.

Thanks ncochise.

registered · Posted: Sun Nov 25, 2007 10:38 pm

Patched for 2.5.15