Dizkus

Here is what is happening:

I have two installs of pn750 in separate subdirectories - one for productions and one that I use for dev and test.

On the 22nd March at about 6pm Pacific, I started getting "page
unavailable" errors for PostNuke admin pages. I was making some changes to the test install
when "page unavailable" for about half the admin options started
occuring.

I was modifying a copy of pnDefault>master.htm and I added a line to see if I could automatically add trace info to my page source.

so at




I added in





After replacing the file master.htm, I got these page unavailble errors


my test:
1) click on admin in the main menu
2) click on any of (to name a few) comments, downloads, polls, weblinks...
(admin pages appear)
3) click on any of (to name a few) autolinks, xanthia, typetool, ratings and
the "page unavailable" messages occur

so I restored the original master.htm file, but the errors still occur.

I ran settings and changed the theme to extralite... still have admin page references giving "page unavailable"

so I uninstalled my test pn750 with fantastico and reinstalled fresh to a new directory.. went back to my test and still had the errors for the same admin pages

so had the hosting support team look in logs - this is what they reported

[Tue Mar 22 15:14:35 2005] [error] [client XXX.XXX.XXX.XXX] Invalid method in
request \\x80g\\x01\\x03

also, the same issue is appearing in my other pn750 install "production" but these changes were not made there to master.html

what i do not understand is why the fresh install of PostNuke did not fix this
and why the issue also appears in another separate install of PostNuke in a
different directory (production).... argh. this is not a multisite

I also downloaded the swiss knife and changed the default template.. no joy

outa ideas, bentsteal needs help please

here is the stack versioning

Operating system Linux
Service Status Click to View
Kernel version 2.4.28-grsec
Apache version 1.3.33 (Unix)
PERL version 5.8.4
PHP version 4.3.9
MySQL version 4.0.22-standard

I deleted all rows from the nuke_theme_tplsource table where the skin_id was created around the time of the issue start and wala... she is okay now.

Still don't understand why issue occured in both sites. Cache?