Announcement

Collapse
No announcement yet.

PROD pages links not being generated secure

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

  • Thanks Eric!
    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


    • this bug is biting me too! but I am thinking i need to reread the instructions
      http://www.miva.com/blog/how-to-conv...tore-to-https/
      because supposedly we don't need to worry about that setting.


      Last edited by kayakbabe; 04-17-17, 02:10 PM.

      Comment


      • The instructions say you don't, but you definitely do. All my developer needed to do was find the place in the database where that value is written (sorry, I'm not sure exactly where it is) and write the value as https:. Once that's done everything works as it should if you follow the rest of the directions.
        Todd Gibson
        Oliver + S | Sewing Patterns for Kids and the Whole Family

        Comment


        • Any update on this? I also have a site where Breadcrumb, Category and Product links are not output as https:. We also had to set the Site Configuration > Non-secure URL to Miva Merchant: > via the database. Merchant threw an error when trying to update. "LMN-VLD-00155: License is not transferable. Please contact your host provider"
          Ron Frigon
          The Web Dude at J. Rousek Toy Co.

          Comment


          • I'm almost certain this is in 9.7, so imminently at this point.
            Thanks,

            Rick Wilson
            CEO
            Miva, Inc.
            [email protected]
            https://www.miva.com

            Comment


            • Originally posted by Rick Wilson View Post
              I'm almost certain this is in 9.7, so imminently at this point.
              Do you know if this is going to involve a coding change or will what is already in place work as needed? In other words, has that URI Management URL Prefix issue being resolved to where https can be entered as needed?
              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


              • No coding changes required, if you have the store settings set to use https this will just work. Just to clarify this but only impacts stores using Legacy SEO settings. If you're using URI Management converting to https works without any issue.
                Brennan Heyde
                VP Product
                Miva, Inc.
                [email protected]
                https://www.miva.com

                Comment


                • Originally posted by Brennan View Post
                  No coding changes required, if you have the store settings set to use https this will just work. Just to clarify this but only impacts stores using Legacy SEO settings. If you're using URI Management converting to https works without any issue.
                  This little ditty is still hanging around. Could it have anything to do with the site using the Sebenza Category Template Manager? It's using the CTGY page <mvt:item name="category_listing" /> token which uses the &mvte:product:link; token. That same token works fine on the PLST page.

                  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


                  • It's VERY likely that the Category Manager has no way of getting the correct value for the page link via the &mvt:product:link; token. In fact, I'd be surprised it could.

                    You could probably just insert:

                    Code:
                    <mvt:assign name="l.uri:store_id" value="g.Store:id" />
                    <mvt:assign name="l.uri:screen" value="'PROD'" />
                    <mvt:assign name="l.uri:page_id" value="0" />
                    <mvt:assign name="l.uri:cat_id" value="0" />
                    <mvt:assign name="l.uri:product_id" value="l.settings:product:id" />
                    <mvt:do file="g.Module_Feature_URI_DB" name="l.have_uri" value="URI_Load_Item_Canonical( l.uri, l.settings:canonical_uri )" />
                    And then use: &mvt:canonical_uri:uri; in place of the &mvt:product:link; (Check the variables loaded into the array as I really don't know what Category Manager uses.

                    Oh, and use this to point out why they need to ditch things like Category Manager.
                    Last edited by Bruce - PhosphorMedia; 06-20-19, 01:23 PM.
                    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