Menus don't get skinned with Artisteer template

A place for discussion about skinning and design. Before posting questions here you should review the documentation about creating skins.

This thread is closed to new posts. You must sign in to post in the forums.

10/13/2011 9:29:54 PM

Finnur

Total Posts 34

View Posts

Menus don't get skinned with Artisteer template

I am running mojoPortal 2.3.6.6 MSSQL

I am using an Artisteer 3.0 website or blog template set up with a horizontal menu under the page header and a vertical menu on the left side. The Artisteer sheet setting is fixed width 3-column. I use the generated template with the artisteer-30verticalmenu1 skin.

After I disabled the mojoPortal CSS caching everything looks more or less as it should, except for the menus, they seem to be rendered without any style.

Does anyone know why this happens. Could there be some conflict between the Javascript usage of mojoPortal and the Artisteer skin?

10/15/2011 2:56:13 PM

Finnur

Total Posts 34

View Posts

Re: Menus don't get skinned with Artisteer template - problem solved

Problem solved - and it did not involve any Javascript.

Adding the property
RenderArtisteer="true"
in the portal:mojoMenu and portal:mojoTreeView sections in the theme.skin file solved the problem.

This seems to be necessary for mojoPortal to render the correct HTML for use with the artistreer css.

I looked at few of the other mojoPortal artisteer skins and they also were missing this property.

Also note in the portal:mojoTreeView section is a property defined as LiNonRootExpnadableCssClass="" which looks like a spelling error. I have not yet noticed any problems because of that however.

10/16/2011 2:06:30 PM

Joe Audette

Total Posts 18439

View Posts

Re: Menus don't get skinned with Artisteer template

Hi Finnur,

RenderArtisteer is not a property on mojoMenu nor mojoTreeView, perhaps the theme was cached and touching the file cleared the cache.

During upgrades we only update the skins under /Data/skins we don't touch skins under /Data/Sites/[SiteID]/skins so old Artisteer skins in the site specific skin folders may not have the latest updates.

This is what we have in artisteer-30verticalmenu2 in theme.skin as of the current version (2.3.7.0)

<portal:mojoMenu runat="server" SkinID="SiteMenu"
RenderContainerCssClass="true"
ContainerCssClass="art-nav-outer"
RenderImages="false"
UseMenuTooltipForCustomCss="true"
RenderCustomClassOnLi="true"
RenderCustomClassOnAnchor="false"
RenderLiSelectedCss="false"
RenderAnchorSelectedCss="true"
UlCssClass="art-hmenu"
LiCssClassWithChildren=""
LiCssClassWithoutChildren=""
LiSelectedCssClassWithChildren=""
LiSelectedCssClassWithoutChildren=""
LiChildSelectedCssClass=""
LiParentSelectedCssClass=""
AnchorCssClass=""
AnchorSelectedCssClassWithChildren="active"
AnchorSelectedCssClassWithoutChildren="active"
AnchorChildSelectedCssClass=""
AnchorParentSelectedCssClass=""
InnerSpanMode="Artisteer"

<portal:mojoTreeView runat="server" SkinID="PageMenu"
ContainerCssClass="art-vmenublock"
ExtraMarkupMode="Artisteer"
RootUlCssClass="art-vmenu"
RenderLiCssClasses="true"
RenderAnchorCss="true"
LiCssClass=""
LiRootExpandableCssClass=""
LiRootNonExpandableCssClass=""
LiNonRootExpnadableCssClass=""
LiSelectedCssClass="active"
LiChildSelectedCssClass="active"
LiParentSelectedCssClass=""
AnchorCssClass=""
AnchorSelectedCssClass="active"
ExpandDepth="-1"
ShowExpandCollapse="false"
PopulateNodesFromClient="false"

and in layout.master the menus are configured like this:

<portal:SiteMenu ID="SiteMenu1" runat="server"
UseTreeView="false" HideMenuOnSiteMap="false" DynamicDisplayLevels="0"></portal:SiteMenu>

<portal:PageMenu id="PageMenu1" runat="server" UseTreeView="true" IsSubMenu="true" TreeViewShowExpandCollapse="false" />

You are right about the spelling mistake, I noticed it myself, the problem is if I fix it then it will probably mess up some skins when people upgrade and I try to avoid doing that.

Best,

Joe

10/16/2011 4:34:16 PM

Finnur

Total Posts 34

View Posts

Re: Menus don't get skinned with Artisteer template

Yes, I stand corrected, removing this from the theme.skin file, restarting the IIS server, refreshing the browser cache and everthing still worked correctly.

Still this seems odd as I really did copy from the \Data\skins folder rather than the /Data/Sites/... from the mojoPortal 2.3.6.6 download.

Caching issues aside, using Artisteer with mojoPortal is a great experience. Now I feel fully in control of how my web sites look like. Trying out new designs can be done in minutes rather than hours before.

Previously I would start with some of the supplied mojoPortal skins and modify them, but that was a slow and cumbersome process, slowed down by my limited knowledge and experience of working with HTML and CSS. Working in ASP.NET Web Forms applications and Silverlight is not much help with that.

You must sign in to post in the forums. This thread is closed to new posts.