Important Notice from AspDotNetStorefront
It is with dismay that we report that we have been forced, through the action of hackers, to shut off write-access to this forum. We are keen to leave the wealth of material available to you for research. We have opened a new forum from which our community of users can seek help, support and advice from us and from each other. To post a new question to our community, please visit: http://forums.vortx.com
Results 1 to 9 of 9

Thread: 9.0 left catagory

  1. #1
    brianperry is offline Member
    Join Date
    Sep 2005
    Posts
    41

    Default 9.0 left catagory

    were can you edit the look of the left catagori nav that

    <aspdnsf:EntityControl ID="ctrlEntityCategory" runat="server" Header="<%$ Tokens:StringResource, AppConfig.CategoryPromptPlural %>"
    EntityType="Category" MaxMenuSize="<%$ Tokens:AppConfigUSInt, MaxMenuSize %>" />

    creates

    we are trying to get rid of the ">>" on the sub menu

  2. #2
    brianperry is offline Member
    Join Date
    Sep 2005
    Posts
    41

    Default anyone?

    anyone know where this is?

  3. #3
    MMay is offline Junior Member
    Join Date
    May 2007
    Posts
    13

    Default

    i could use an answer to this as well.

  4. #4
    Mike The Last Boyscout is offline User
    Join Date
    Nov 2008
    Posts
    254

    Default

    Its located in the /Web/App_Templates/Skin_1/XmlPackages/ folder.

    The file you'll need to edit is rev.categories.xml.config.

    The line responsible for those marks is:

    HTML Code:
    <span class="catMark">&gt;&gt;</span>&#160;

  5. #5
    brianperry is offline Member
    Join Date
    Sep 2005
    Posts
    41

    Default tryed that

    we already tried that and it didnt work

  6. #6
    Mike The Last Boyscout is offline User
    Join Date
    Nov 2008
    Posts
    254

    Default

    Oops! My bad. In v9.0 the menus are handled via controls, not XML packages.

    If you go into your template.master file, then find and change this line:

    <aspdnsf:EntityControl ID="ctrlEntityCategory" runat="server" Header="<%$ Tokens:StringResource, AppConfig.CategoryPromptPlural %>"
    EntityType="Category" MaxMenuSize="<%$ Tokens:AppConfigUSInt, MaxMenuSize %>" />

    with the following in red:

    <aspdnsf:EntityControl ID="ctrlEntityCategory" runat="server" Header="<%$ Tokens:StringResource, AppConfig.CategoryPromptPlural %>"
    EntityType="Category" Bullet=" " MaxMenuSize="<%$ Tokens:AppConfigUSInt, MaxMenuSize %>" />

    That should do the trick! You can also replace the spaces with another character if you wish.

  7. #7
    brianperry is offline Member
    Join Date
    Sep 2005
    Posts
    41

    Default nice

    that makes it easy, is there any way to filter these? so on different masterpages we could show only categories that apply to that department?

    Books
    xxx
    xxxx

    etc.

  8. #8
    VibeCommerce is offline Member
    Join Date
    Dec 2006
    Location
    Grandville, MI
    Posts
    63

    Default

    Since the new control has hard coded HTML in it, we cannot use it in most cases. Here is what we did instead - this is just for your reference, it's a working example but could be improved certainly.

    1. Add a tag to template.master in place of the aspdnsf:EntityControl tags that output these new menu controls:

    Code:
    <asp:Literal ID="leftNavCat" runat="server" Text="<%$ Tokens:XMLPACKAGE, vibe.categories.xml.config%>" />
    You can change the name of the xmlpackage or ID, this is just for reference.

    Then make sure you have the following xmlpackage in your XmlPackages folder.

    NOTE: this xmlpackage still works for parent level menus, but because a lot of the v9 XMLPackage System / Runtime information is now missing or changed, some of these tests simply fail because that data is not there anymore
    I'm hoping that will be changed because there was some useful data there that made developing xmlpackages on the fly very easy. For example, /root/System/PageName no longer shows the actual underlying file name like showcategory.aspx, but instead it shows c-1-test-cat.aspx, which is already available in several other places.

    Code:
    <?xml version="1.0" standalone="yes" ?>
    <package version="2.1" displayname="Categories" debug="false" includeentityhelper="true">
        <PackageTransform>
            <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:aspdnsf="urn:aspdnsf" exclude-result-prefixes="aspdnsf">
                <xsl:output method="html" omit-xml-declaration="yes"/>
    
                <xsl:param name="CategoryID">
                    <xsl:choose>
                        <xsl:when test="/root/System/PageName = 'showmanufacturer.aspx' or /root/System/PageName = 'showsection.aspx' or /root/System/PageName = 'showdistributor.aspx' or /root/System/PageName = 'showvector.aspx' or /root/System/PageName = 'showgenre.aspx'">0</xsl:when>
                        <xsl:when test="/root/System/PageName = 'showcategory.aspx' and boolean(/root/QueryString/categoryid)">
                            <xsl:value-of select="/root/QueryString/categoryid"/>
                        </xsl:when>
                        <xsl:when test="(/root/System/PageName = 'showcategory.aspx' or /root/System/PageName = 'showproduct.aspx') and boolean(/root/Cookies/lastviewedentityinstanceid) and /root/Cookies/lastviewedentityname = 'Category'">
                            <xsl:value-of select="/root/Cookies/lastviewedentityinstanceid"/>
                        </xsl:when>
                        <xsl:otherwise>0</xsl:otherwise>
                    </xsl:choose>
                </xsl:param>
    
                <xsl:param name="AncestorID">
                    <xsl:for-each select="/root/EntityHelpers/Category//Entity[EntityID = $CategoryID]">
                        <xsl:value-of select="ancestor::*/EntityID"/>
                    </xsl:for-each>
                </xsl:param>
    
                <xsl:param name="ParentID">
                    <xsl:for-each select="/root/EntityHelpers/Category//Entity[EntityID = $CategoryID]">
                        <xsl:value-of select="parent::*/EntityID"/>
                    </xsl:for-each>
                </xsl:param>
    
    
                <xsl:template match="/">
                    <h3>Browse By Category</h3>
                    <ul>
                        <xsl:apply-templates select="/root/EntityHelpers/Category/Entity" />
                    </ul>
                </xsl:template>
    
    			<xsl:template match="Entity">
                    <xsl:param name="eName" select="aspdnsf:GetMLValue(Name)" />
    
    
                    <li>
                        <a href="{concat('c-',EntityID,'-',SEName,'.aspx')}">
                            <xsl:if test="EntityID = $CategoryID or descendant::Entity/EntityID = $CategoryID">
                                <xsl:attribute name="class"><![CDATA[active]]></xsl:attribute>
                            </xsl:if>
                            <xsl:value-of select="$eName"/>
                        </a>
    
    
                        <xsl:if test="count(child::Entity)&gt;0 and (EntityID = $CategoryID or descendant::Entity/EntityID = $CategoryID)">
                            <ul>
                                <xsl:apply-templates select="Entity" />
                            </ul>
                        </xsl:if>
                    </li>
                </xsl:template>
    
            </xsl:stylesheet>
        </PackageTransform>
    </package>

  9. #9
    omairkha is offline Member
    Join Date
    Aug 2011
    Posts
    89

    Question

    Hi,

    My problem kind of relates to what is being discussed here.

    We have one product category which is basically a "services" page that does not have any products but describes the additional services offered and provides a quote request form for the customers to complete and submit. This page was created as a stand-alone page which uses the same master page.

    Where can I edit left category box to add a static link to this page?

    Thanks!