Rank: Member
Joined: 5/24/2004(UTC) Posts: 4,147
|
I've removed all themes except the new custom themes from a store which will launch soon. Now I'm getting the attached error: Code:Parser Error Message: The file '/BVModules/Themes/Bvc5/Default.master' does not exist. This doesn't seem right; what if I don't want the BVC5 theme available for users who want to switch themes under their account, for example, if I wanted to make a high-contrast theme available? Any way around this without modifying the masterpage reference on every .aspx file in the store? I thought the masterpage was assigned by the selected theme application first before defaulting. Edit: Oops, forgot attachment. File Attachment(s): ParserError.htm (7kb) downloaded 1 time(s).You cannot view/download attachments. Try to login or register. |
|
|
|
|
Rank: Member
Joined: 3/1/2006(UTC) Posts: 1,142
|
sorry, it has to do with the way in which asp.net compiles the pages. You can override a masterpage at runtime, but the masterpage has to be set at design time in order for visual studio to not completely poo all over itself. We picked the bvc5 theme as the base theme. In fact, in some parts of the code we use the bvc5 theme as the "fallback" theme in case parts of a new theme are missing. In the base of most pages we have a GetSafeMasterPage call which looks for a masterpage in the current theme and if it isn't found then it returns the masterpage for the bvc5 theme. |
Justin Etheredge Senior Software Engineer BVSoftware |
|
|
|
Rank: Member
Joined: 5/24/2004(UTC) Posts: 4,147
|
Do you think there might be a case here for setting a default fallback theme via the admin? And/or not using a theme at all for this, just reference a default master page or two in the root so that VS doesn't blow up?
That would allow us to clean out the Themes folder for both admin and users without getting an error in the browser. |
|
|
|
|
Rank: Member
Joined: 3/1/2006(UTC) Posts: 1,142
|
Well, we would still have to have default master pages for most every master page in the application, and allowing the user to set a fallback theme doesn't really help unless we can guarantee that the theme is complete. The idea was the a customer could create a new theme and not have to override all of the master pages. But if they specify a theme as the fallback which itself is missing items, then the mechanism would fail spectacularly. Another potential solution would be to have a separate theme folder somewhere that would be the base bvc5 theme, that we could use as a fallback, but wouldn't show up in any of the lists. We will look into this and see if it might be a possibility for a future release. |
Justin Etheredge Senior Software Engineer BVSoftware |
|
|
|
Rank: Member
Joined: 5/24/2004(UTC) Posts: 4,147
|
OK. Yeah, that's what I meant by having some default master pages in the root that the rest of the pages could reference for the sake of Visual Studio, and to keep from blowing up if the themes folder were empty. |
|
|
|
|
Forum Jump
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.