I have Exchange post on this but that was becoming too much of a discussion so moving over here.
I upgraded a site (actually more than one) from 6.2.4 to 7.0.5. After the upgrade everything appears fine - site is operating and editing (going into edit mode and pulling up the edit in html modules) appeared to work.
The next day my client went to the site and added a page (he is an admin) after adding the page he was not able to get that page to enter edit mode. I logged in and as host was not able to get that page to enter edit mode. All other pages created before the upgrade were able to go to edit mode. I changed to the ribbon bar for the sake of getting it working for him.
I would really like to have a consistent appearance and operation across all my sites for this client so I want to solve this issue.
I have checked that it was not a javascript issue. No errors are being shown. The site is running in .NET 4.
I have compared the web.config to a site that operates correctly (it was installed as a DNN7 site from the start) and there are a few differences that are maybe notable.
In the site that does not work I have http errors section
<httpErrors errorMode="Custom" existingResponse="Replace">
<remove statusCode="404" subStatusCode="-1" />
<error statusCode="404" prefixLanguageFilePath="" path="http://legacycommunityhealth.org/Home.aspx" responseMode="Redirect" />
</httpErrors>
In the working site I do not have this
--------------------------------------------------------------------------
In the working site I have
<staticContent>
<mimeMap fileExtension=".mp4" mimeType="video/mpeg" />
</staticContent>
This is not in the site that does not work
----------------------------------------------------------------------------------------------------
In the site that does not work this line
<add name="Services" type="DotNetNuke.HttpModules.Services.ServicesModule, DotNetNuke.HttpModules" />
is above
<add name="FormsAuthentication" type="System.Web.Security.FormsAuthenticationModule" preCondition="" />
and in the site that does it is below that same line.
Could any of these web.config issues be the culprit?