Announcement

Collapse
No announcement yet.

Category Title Image not displaying with specific Alternate Display Page

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Category Title Image not displaying with specific Alternate Display Page

    I created a new Alternate Display Page template and assigned it to the category but it's not displaying the Category Title Image.

    I had made sure that I added it mvt:if

    Code:
    <mvt:if expr="l.settings:page:code EQ 'CTGY' OR l.settings:page:code EQ 'CTGYSIZE' OR l.settings:page:code EQ 'CTGYALTTHUMB'">
                            <mvt:if expr="NOT ISNULL l.settings:category_title:image">
                                <img class="column whole h4 page-title" src="&mvte:category_title:image;" alt="&mvte:category:name;" title="&mvte:category:name;" />
                            <mvt:else>
                                <h1 class="column whole large-np page-title">&mvt:category:name;</h1>
                            </mvt:if>
    The CTGY and the CTGYSIZE Alternate Display Pages work just fine.

    I thought that the body ID might have been a problem, so I tried changing it to id="js-CTGY" from id="js-&mvte:page:code;" - that didn't help either. I have also double checked that page code and even tried changing it to see if that was the issue. There is nothing different in the Page template field of the CTGYALTTHUMB. It is the same as the CTGY template field.

    This is extremely baffling. The dev site is behind a password protected directory so it's not readily available for looking at.
    Leslie Kirk
    Miva Certified Developer
    Miva Merchant Specialist since 1997
    Previously of Webs Your Way
    (aka Leslie Nord leslienord)

    Email me: [email protected]
    www.lesliekirk.com

    Follow me: Twitter | Facebook | FourSquare | Pinterest | Flickr

    #2
    Hi Leslie,

    The first two things that come to mine are:
    • Is the category code spelled consistently?
    • Is there an image uploaded for the title?

    The other thing you might try is to change the IF statement to be:
    Code:
    <mvt:if expr="'CTGY' CIN l.settings:page:code">
    Matt Zimmermann

    Miva Web Developer
    Alchemy Web Development
    https://www.alchemywebdev.com
    Site Development - Maintenance - Consultation

    Miva Certified Developer
    Miva Professional Developer

    https://www.dev4web.net | Twitter

    Comment


      #3
      Yup and yup. These are the two items I triple checked. The field works just fine for the other two templates, so it baffles me.



      Leslie Kirk
      Miva Certified Developer
      Miva Merchant Specialist since 1997
      Previously of Webs Your Way
      (aka Leslie Nord leslienord)

      Email me: [email protected]
      www.lesliekirk.com

      Follow me: Twitter | Facebook | FourSquare | Pinterest | Flickr

      Comment


        #4
        Originally posted by Matt Zimmermann View Post
        Hi Leslie,

        The other thing you might try is to change the IF statement to be:
        Code:
        <mvt:if expr="'CTGY' CIN l.settings:page:code">
        Question, if this is the preferred method, why isn't it implemented more universally throughout the ReadyThemes? The line of code right after this particular snippet is:
        Code:
        <mvt:elseif expr="l.settings:page:code EQ 'PROD' OR l.settings:page:code EQ 'ORDL' OR l.settings:page:code EQ 'OCST' OR l.settings:page:code EQ 'OUS1' OR l.settings:page:code EQ 'OUSM' OR l.settings:page:code EQ 'UATM' OR l.settings:page:code EQ 'UATR' OR l.settings:page:code EQ 'OSEL' OR l.settings:page:code EQ 'OPAY' OR l.settings:page:code EQ 'INVC'">
        Just sayin'



        Leslie Kirk
        Miva Certified Developer
        Miva Merchant Specialist since 1997
        Previously of Webs Your Way
        (aka Leslie Nord leslienord)

        Email me: [email protected]
        www.lesliekirk.com

        Follow me: Twitter | Facebook | FourSquare | Pinterest | Flickr

        Comment


          #5
          CIN (case insensitive) is considerably more CPU intensive as both cases of each letter has to be checked. If you are certain of a variable value, then IN is faster. In fact (though we are talking milliseconds, if you are not sure, or the variable is coming from outside the system (i.e., a url) then using "'xxxx' IN tolower(g.variable)" is still faster.
          Bruce Golub
          Phosphor Media - "Your Success is our Business"

          Improve Your Customer Service | Get MORE Customers | Edit CSS/Javascript/HTML Easily | Make Your Site Faster | Get Indexed by Google | Free Modules | Follow Us on Facebook
          phosphormedia.com

          Comment

          Working...
          X