PROD pages links not being generated secure

[lesliekirk]

Thanks Eric!

[kayakbabe]

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.

[oliverands]

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.

[Ron Frigon]

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"

[Rick Wilson]

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

[lesliekirk]

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?

[Brennan]

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.

[lesliekirk]

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.

[Bruce - PhosphorMedia]

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:

<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.