Problem opening to News Articles

Regular Joined: Aug 15, 2006 Posts: 66

So... it seemed to be working fine.

7.6 patched with NukeSentinel(tm) 2.5.02

I did a new install of the programmes and I then restored the database from my previous site which was a 7.5 by checking the fields before uploading each table individually.

Tested the site, had a few hickups but got those sorted. Test again and was able to click on the news, open and read.

Today I get home and click on the news and I get this message from my firefox browser:

Quote:

Firefox has detected that the server is redirecting the request for this address in a way that will never complete.

* This problem can sometimes be caused by disabling or refusing to accept cookies

So, I disabled cookies but still the same issue. Also tried explorer, however the pages just keep trying to open to no avail.

any suggestions? or should I just rebuild the module? I've checked SQL and all looks fine.

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

Haven't seen that before. I'd clear the cache and all cookies and try again.

Posted: Fri Aug 25, 2006 6:49 pm

I've done that already without any change to the result.

Posted: Fri Aug 25, 2006 7:41 pm

I did a general search on the net for the error - weren't many exact matches but those few appear to point at a problem with the php.ini file or .htaccess.

I've emailed my host server and they are looking into it as well for me.

Posted: Sat Aug 26, 2006 9:29 pm

Well I think my host server fixed it, because over night the problem has gone away. I'm waiting for them to respond, so once I know what they did, I'll share incase others ever have this problem.

registered · Posted: Sun Aug 27, 2006 6:45 am

Thanks Tina. Definitely let us know.

Posted: Wed Aug 30, 2006 5:18 am

Apparently they did nothing. The problem has occured again and is occuring at a specific time in the evening. They are looking into it still though. Think it could be the mod_security module in apache.

Posted: Sat Sep 02, 2006 4:24 am

I've still got this problem, but I have found a postnuker who had the same issue. They fixed it up by enabling support for the "legacy" modules - I'm just wondering if anyone has a clue how I transpose this fix to phpnuke?

Posted: Sat Sep 02, 2006 10:35 am

Sorry, haven't a clue what they mean by "legacy modules".