Announcement

Collapse
No announcement yet.

Image 'Main' > UATR vs UATM

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

  • Image 'Main' > UATR vs UATM

    UATR


    UATM


    Can anyone tell me why I can't get the main image on UATM but can on UATR?

    I verified that all the Items are the same except that UATM also has upsell_attr_mult

    I tried copying the code for image display which works on UATR

    Code:
            <mvt:do file="g.Module_Library_DB" name="l.success" value="ImageType_Load_Code('main', l.settings:imagetype)"/>
            <mvt:do name="l.success" file="g.Module_Library_DB" value="ProductImage_Load_Type(l.settings:product:id, l.settings:imagetype:id, l.settings:imagetype)"/>
            <mvt:do name="l.success" file="g.Module_Library_DB" value="Image_Load_ID(l.settings:imagetype:image_id, l.settings:imagedata)"/>
    
            <mvt:if expr="NOT ISNULL l.settings:imagedata:image">
                <img src="&mvte:imagedata:image;" alt="&mvte:upsale:name;" title="&mvte:upsale:name;" style="float: left; display: inline; margin: 0px 10px 0px 20px;">
            <mvt:else>
                test: main image not found
            </mvt:if>
    tried duplicating the templates and other things but they seem to be rendered totally different.

    Thanks.



  • One thing to check are the page items - do both pages have the same page items assigned, especially with regards to images?
    M.A.D.* since 1997

    http://www.scotsscripts.com

    *miva application developers

    Comment


    • Look the same except that UATM has one extra item which is upsell_attr_mult

      The only other difference I see is that on checkout the page for multiple upsell items first goes to OUSM which then hands it off to UATM - not sure if that is relevant.

      Comment


      • Standard Debug Routine:

        Insert evals of the return var after each API function call

        Rename the "name" on the function call to something logical (i.e., g.LoadImage, g.ImageLoad, etc) and eval them right after the function as well. Might also want to double check that you are getting, using the right ID.
        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


        • Like Bruce said.

          For these:

          <mvt:do file="g.Module_Library_DB" name="l.success" value="ImageType_Load_Code('main', l.settings:imagetype)"/> <mvt:do name="l.success" file="g.Module_Library_DB" value="ProductImage_Load_Type(l.settings:product:i d, l.settings:imagetype:id, l.settings:imagetype)"/> <mvt:do name="l.success" file="g.Module_Library_DB" value="Image_Load_ID(l.settings:imagetype:image_id , l.settings:imagedata)"/> Are you certain each of those ids and other variables being used to call the functions have values? Try checking them by doing things like: &mvt:imagetype; &mvt:imagetype:id; etc... check each one to make sure it actually has some value. There may be something in the code, before this stuff, that sets some of those variables.
          M.A.D.* since 1997

          http://www.scotsscripts.com

          *miva application developers

          Comment


          • It looks like at the imagetype and imagedata have the value 'main' and '4' but nothing else. The image values for the product that qualified them for the upsell are visible.

            imagetype =
            upsale:name =
            imagedata:image = main,Main,4,
            imagetype:id = 4
            imagedata =
            product:id =
            item:product:image = graphics/00000001/ATEP-30087.jpg /* this was the required product qualifying them for the upsell */
            product:image =
            group:product:image = graphics/00000001/ATEP-30087.jpg

            Comment


            • the product:id = {nothing} is an issue since that's the id you are feeding the find image function....so, i actually looked at a sample Multi Upsell and you should be using:

              l.settings:upsold_product:id

              unless you change the iterator...in which case, change it back and use upsold_product cause there might be collision issues.
              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

              This website uses cookies to identify visitors, track visitors to our website, store login session information and to remember your user preferences. By continuing to use this site you agree to our use of cookies. Learn More.

              This website uses cookies. By continuing to use this site you agree to our use of cookies. Learn More.

              Accept