and at this point I can't blame them. I have two portals for the same person on one site (discountasp.net) running 4.3.7. No fancy skins at this point. The main problem is the second portal is nearly inoperable for maintenance. Deleting modules, trying to add modules, almost anything that requires a submit no longer works.

I've tried everything I know to trace the problem, but no joy. Using netscape I can get more information, but no real clue. It always errors on "Object doesn't support this property or method". It was suggested that this is a skin problem, but the skin is just DNN Grey at this point. Using Netscape I see it's the theForm.submit it's complaining about, but I can't figure out why it's only this ports (I have about a dozen on various places, this is the only place I see this).

Since the other complaint was the glacial speed of the site, I pulled it down to my test server and upgraded it to 4.4.1 hoping maybe the other problem would go away. No joy. I can't delete any modules to determine the cause because the deletes fail with the same error.

This site is for a political campaign and the clock is ticking. Another campaign working is familiar with LAMP sites, and wants to move the domains to a LAMP provider because he's convinced about everyone on the campaign DNN is a piece of crap because even simple things aren't working.

So far I've tried different skins, a 4.4.1 upgrade, all other manner of debugging with multiple browsers. Nothing will budge this problem. I'm at a loss.

The URLs are:

www.danbesse.org (works fine)

www.danbesse2008.org (doesn't work, see email page for typical example).

both are portals on the same site, same database, etc.

Thanks you very much for your help, since I'm about to upgrade several other sites to DNN 4.4.1 I'll keep that in mind. Can I assume that sites that aren't using the default skins are safe from this?

However, I struck gold in a different way and have discovered after many, many, many, iterations what the problem was. This fix was a bit ugly.

One of the joys, and not so joys of DNN is it allows you to create sites that are user maintained. Anyone that has had to clean up pages after someone copy/pasted from a Word document into Text/HTML knows what I'm talking about. (I'd really like Remove All Formatting, to actually remove all formatting).

In any case, a well meaning campaign worker set up a donation program via PayPal and copied the PayPal donate button that was generated on the PayPal site into a Text/HTML module that was on every page. My assumption is a reference to this button was pulling down a script that messed up the DOM on the page and since it displayed everywhere is messed up ALL pages (except admin, which didn't have this displayed). Now fixing this was problematic because Edit Text didn't work either. I ended up opening the database directly in SQL Manager and deleting the row for that module in the Html table.

Wango bango everything started working again after only about two weeks of head scratching. I tracked this by manually hammering one module at a time from the database tables on a copy of the site. Not for the faint hearted, and certainly not for a live site.

I thought I was being safe by not giving them admin capabilities by setting up a "site maintainers" group that only could edit module content. That does mean I have to step in to add modules, pages, etc. I didn't anticipate the potential impact of allowing that edit capabilities on a module that displays on all pages. Lesson learned the hard way.