Hi Joe,

Sorry for the inconvenience. You can fix this immediately by adding this on the ScriptLoader control in layout.master

IncludeAspTreeView="true"

This was caused by my efforts to reduce the amount of unnecessary javascript. I " thought" the TreeView only needed the javascript if it had the ShowExpandCollapse="true", so I backed it out by default and only added it if the TreeView was configured for ShowExpandCollapse and it seemed to work fine in most cases, but I didn't find this one.

It seems if the calendar does a postback with the treeview on the page it causes this error, so it only happens in skins that use a TreeView menu. In any case, I knew that such a change might have some side effect that I hadn't expected so I made sure there was an easy way to turn that script back on as indicated above.

Best,

Joe

Hi Joe,

I've tried both methods, the IncludeAspTreeView and replacing the mojoPortal.web.dll file. Neither has worked for me. This is a customer site that is not hosting with me. Their hosting is .NET 3.5 Medium Trust.

Thanks,
Joe D.
 

Hi Joe,

<portal:SiteMenu id="SiteMenu1" runat="server" UseTreeView="false"  HideMenuOnSiteMap="false" Direction="Horizontal" TopLevelOnly="true"></portal:SiteMenu>

<portal:PageMenu id="PageMenu1" runat="server" UseTreeView="false" Direction="Horizontal" DynamicDisplayLevels="0" />

<portal:PageMenu id="PageMenu2" runat="server" UseTreeView="true"  SiteMapDataSource="level3datasource" StartingNodeOffset="2" TreeViewShowExpandCollapse="true"  />

They only display the two page menus on their site (the skin is using css to hide the site menu). The original developer of this site really screwed things up and they have a entire section of pages under the root that aren't displayed on anything except the Site Map. The developers answer to this was to just hide  the site menu and create additional page menus. We are in the process of restructuring the site but it is going to take a while due to the severity of chaos. :-)

I just updated their site from 2.3.5.8 to 2.3.6.7 and I included all of the skin changes since then. I checked the items from before 2.3.5.8 and they appear to be in the skins they use.

Thanks,
Joe

Hi Joe,

No Joy. I made sure to copy the theme.skin App_Themes\default directory, as I did on upgrade.

Which script file is supposed to be included? Maybe I can track that down and make sure it is loading.

The TreeView in the menu is working, sort-of. Apparently, they didn't want the the expand/collapse buttons so they just deleted the images. I just set TreeViewShowExpandCollapse to false but that didn't help the calendar issue.

Thanks,
Joe

ps I've seen cases where the theme cache gets very stubborn and doesn't seem to clear when you edit the theme.skin file, sometimes it takes recycling the app pool to make it see those theme.skin changes.

Best,

Joe

Hey Joe,

Yes, I can change skins under .NET 3.5 Medium Trust.

There is a known error in checking the web.config for the default culture under medium trust but it is a handled error in code so it should be saying "swallowed error" in the log and it shouldn't break anything.

You can avoid that error by forcing a specific culture for the site like this:

 <add key="UseCultureOverride" value="true" />
  <add key="site1culture" value="en-US" />
  <add key="site1uiculture" value="en-US" />

then it would use those settings before trying Web.config

Hope that helps,

Joe

Hi Joe,

I removed the direct references to the scripts from the layout.master, uploaded the new files and it seems to be working correctly.

Thank you for your diligence. It is greatly appreciated.

Thanks,
Joe