I have created a new theme called ThemeX for example.
I have created the theme, stylesheets, etc. and placed them in the App_Themes folder. No problem there.
I have selected the new theme in the Admin section of the system. No problem there.
The new theme is properly utilized on any page that uses the Root.Master. No problem there.
The web.config file still contains a theme specification of DarkOrange.
Now for the issue...
I created a new master page called Root2 (for example). This master page is a "base" master page.
In the code-behind file I modified the "public partial class" statement with the result shown below...
namespace NopSolutions.NopCommerce.Web.MasterPages
{
public partial class BackRoot : BaseNopFrontendMasterPage
{
protected void Page_Load(object sender, EventArgs e)
{
}
}
}
The web.config file still contains a reference to the DarkOrange theme.
I built a detailed page (call it DetailPageUsingRoot2 for example) that uses the new "Root2" master page.
When I display that page in the browser, it still uses the DarkOrange theme.
The default.aspx page properly uses the new theme.
When I put a link on the default.aspx to DetailPageUsingRoot2.aspx, it is displayed using the Dark Orange theme.
If I change the web.config theme section to the new theme, everything displays in the new theme.
There must be some kind of "hook" that I am missing in my new Root2.master page that does not load the theme selected in the Admin section.
I must be really stupid to not figure this out on my own, but could you please you tell me how to get the selected theme to display on my Root2.master-related paged regardless of what the web.config file contains for a specified theme?
Thanks in advance!
Lynn