I posted this in a different forum, but it really is more fo a bug than a design issue.
We have an existing site to which we are adding Sitefinity, and we have run into some issues relating to nested master pages. We have the following issues:
1. If there is a ContentPlaceHolder
in a child master page with the same name of one in the parent master page, attempting to save, change Edit Modes, or add any controls while editing the Template of the child master page will fail with a duplicate name error. I have temporarily changed the names to work around this issue.
controls in child master pages that reference a ContentPlaceHolder
control in the parent master page that is inside the <head>
element of the <html>
document, causes a viewstate error when editing the Template of the child master page. If finally discovered the work-around below:
|<asp:Content ID="Content1" ContentPlaceHolderID="SiteHead" runat="server">
| <asp:ContentPlaceHolder ID="head" runat="server"><!-- Content placeholder for SearchMaster head --></asp:ContentPlaceHolder>
controls in the <head>
section of the <html>
document on a master page, causes the Template Editor to render poorly as it attempts to display a section for this control that is off page. For us, it tries to render the editor box for this in the upper left hand corner of the page, but its only about 10 pixels wide. If I max the browser window to full screen (1920x1200) the area is much larger, but the Edit Mode and Theme controls are messed up or not visible.
Here is the message from the viewstate error:
Failed to load viewstate. The control tree into which viewstate is being loaded must match the control tree that was used to save viewstate during the previous request. For example, when adding controls dynamically, the controls added during a post-back must match the type and position of the controls added during the initial request.
On another note, we use the styleSheetTheme
attributes of the pages
element in the web.config to define the default theme, but we were forced to set both to "" in the ~/Sitefinity/web.config as it caused those pages to render incorrectly. While it fixed the Sitefinity pages, it causes our Templates/Pages to render incorrectly unless we specify a theme in the editor. Since this must be dynamic and controlled by our code, I need to know what setting a theme actually does. FYI, we use styleSheetTheme
more often than the theme