It should load the selected theme files. So, if a user selects the Foundation4 theme instead of your store's theme, it should use the Foundation4 theme files.


No, that's not how it should be behaving. Do you see the new template when you change the store theme to use the Foundation4 theme?

When you copied the theme files did you ensure you changed the namespace and the path to the code behind file?

I just did a fresh install of BVC 2015 locally and noticed the same behavior. After some time, it would also put my account back to the store template.

Edited by user Friday, April 24, 2015 10:52:41 AM(UTC)  | Reason: Not specified

Multiple browsers, cleared cache etc, fresh install and current site.

Is this also why the personalized theme will use the default theme's files instead of overriding them? I can deal with the personalized theme falling back to the default theme at the end of the session, but I can't work on the personalized theme because it's pulling its files from the default template.

We noticed in our current theme, any page in the page folder is not working. It's still pulling from the root of the site. Anyone else notice that?

I believe that is the purpose of the new architecture, so you can keep the stock integrity of the store and override selected files in your theme folder.

Maybe im getting confused. These are pages located in my root, like the error pages and custom pages. I'm not creating entirely new pages in my theme... rather copying ones that already exist like above, which would be altering stock code, correct?

I copied my custom.aspx and custom.aspx.vb to my theme pages folder and made a few changes. When I went to the site, it was still pulling from the root, not my pages folder in my theme.

So I looked at my error.aspx pages as well... Actually, it was already there from the upgrade Aaron. Anyways, I noticed the root error.aspx page and the theme>pages error.asxp were different. I should see my theme one correct?

Root error.aspx


<div class="main">
<div class="row">
<div class="small-12 columns">
<h1><asp:Literal ID="HeaderLiteral" runat="server"></asp:Literal></h1>
<div class="errorcontent">
<asp:Literal ID="ErrorContentLiteral" runat="server"></asp:Literal>
</div>
</div>
</div>
</div>



Theme>Pages error.aspx



<h1><asp:Literal ID="HeaderLiteral" runat="server"></asp:Literal></h1>
<div class="errorcontent">
<strong>The page you requested was not found, and we have a fine guess why.</strong>
<ul>
<li><asp:Literal ID="ErrorContentLiteral" runat="server"></asp:Literal></li>
<li>If you typed the URL directly, please make sure the spelling is correct.</li>
<li>If you clicked on a link to get here, the link may be outdated.</li>
</ul>


<H3>What can you do?</H3>
<p>Have no fear, help is near! There are many ways you can get back on track with MedSupplier.com.</p>
<ul>
<li>Use the search bar at the top of the page to search for your products.</li>
<li>Go to our homepage by <a href="/" title="MedSupplier.com">clicking here</a></li>
<li>Use the menu bar above to find the category or product you are looking for</li>
<li>Call customer service at 1-800-335-3774</li>
</ul>
</div>



http://www.medsupplier.com/error.aspx is pulling from the root error.aspx page, not the theme>pages error.aspx

Edited by user Tuesday, June 2, 2015 10:45:57 AM(UTC)  | Reason: confusion

Error.aspx is a special page because it handles server errors. For this reason it cannot be overrided. There's really no reason to override Custom.aspx because we added templating in BVC 2013; just create a new template (or override an existing template in your theme).

You also cannot override the SqlPatch.aspx page, though I can't imagine why you'd want to do this.