Here's an interesting new hurdle in my DNN adventure.

On any page but the home page, If I try to change the page settings, nothing happens, and I get this in the console:



This is the file-
Telerik.Web.UI.WebResource.axd?_TSM_HiddenField_=ScriptManager_TSM&compress=1&_TSM_CombinedScripts_…:6

That's an indication that there are javascript and/or jQuery errors on the page. Do you see any of those in the console?

Is the 404 error associated with a URL? If so, what is it?

You can try going to Admin, Site Settings and look in Advanced Settings, Usability. Uncheck the box to enable popups. Does that allow you do edit Page Settings?

I already have popups enabled. Here is a screenshot of the console, that may explain better.

http://grab.by/DY5W

I was actually suggesting that you turn off popups to see if that is an issue.

I can't tell a lot from the image, except that there is a lot of red!

Is there 2sxc stuff on these pages? You might read Mettler's blog entry on debugging. Fiddler might help you understand why you are getting the 404 errors.

Well, I tried to update the settings on that page again today and it worked just fine. There wasn't any 2sxc stuff on that page. I made NO changes between the time it didn't work and it did.

Nevermind - I thought it was working, but the change I made did not stick. And now the same thing is happening where I click Update and nothing happens.

One more think to try would be to apply a Gravity skin to that page and see if the problem persists (and don't forgot to check the new page for javascript errors). That might let you narrow it down to the skin.

Well it won't let me change the skin either apparently. Trying to do it with SQL but can't figure out what table determines what skins are assigned to what pages. EDIT - I found it.

I changed the Skin to Gravity and still can't update settings. Same errors in the console.

Also turned off popups and still getting same errors.

Is this only that page, or are the problems on other pages? (If it's the one page, what module might be causing it? You could delete modules one by one until the problem goes away -- since they are in the Recycle Bin, you can restore them easily.)

I kind of did the opposite of that.

I made a new page, and one by one added modules from a page that is affected by this settings issue.

I had no issues changing settings on my test page UNTIL I changed the parent page of the test page TO the affected page.
...BUT one of its sibling pages works fine.

I also have been testing different pages all over the site. (Too many to test all of them.) Assessment & some of its children are ok, same with Curriculum. Professional Learning page is OK, but none of its children work. I can't see any rhyme or reason to this.

(The test page is under Research & Eval... all R&E's children do NOT work, except Reports, which does work.)

Yikes.

Since you have some pages that work and some that don't work, I'd suggest staring at the EventLog and the Console to see if you can find something that's different between the two sets.

This issue of parent pages confuses the heck out of me. The only difference that I can thing of is that the affected pages appear differently in the menu with and without a parent. Perhaps there is some javascript/jQuery affecting the pages when they have parents?

OK, I think I fixed it.

In the page settings, I noticed the page name for one of the non-affected pages did NOT end in .aspx.
But in one of the affected pages, it did end in that extension.

I remembered having updating something under Advanced URLs in the Site Settings recently. I went there and unchecked Page URL concatenation and that removed the extension from the page name, and I was able to save page settings.

Hnmmm. Are you using Evoq? Are you using a custom URL provider, or an Evoq one?

Under Host Settings it says Evoq Content. 7.3.4.

These are our advanced URL settings:
http://grab.by/E2bo

Doesn't seem to have any custom URL providers.

As an Evoq customer, you should be entitled to technical support directly from DNN Corp, too.

The page you posted is specific to Evoq. So, you should be able to ask them about it.

For completeness, though, what did you change on the page to make things work? I would have thought that the option for URLs without the .aspx extension would work just fine. If not, you probably should report this to DNN Corp and see if they can fix it for you!

I just unchecked that Page URL Concatenation box.