A couple things worth clarifying here.
You can have spaces, special characters in your product codes if you turn off "Strict Validation for Codes" as mentioned above.
If using URI management, Miva uses the slugified product name by default so it will remove any spaces and replace them with dashes for the name field. This also allows you to change the product codes without the need to URL redirects since the URL is not changing.
If the URL was changing (either you change it manually or you update the product name) Miva does have the option to create a new URL and automatically create a 301 redirect to the new URL that got created. This feature is set to "never" by default, but you can go into URI Management and configure how the URLs behave on product update. Just be careful how you use it because typically you don't want your URL changing often.
lesliekirk your situation sounds a bit different as you are not using URI management already. Your best bet would be to upload a spreadsheet of the old URLs (current structure) to create 301 redirects in URI Management after you generate the new URLs you want (you could also keep the same URL structure you have today by doing this same things but upload them as canonical URLs) As long as you don't have parameters in the URLs this will work great.
If you coming from old style Miva long links that does contain URL parameters, your only option is to build a .htaccess file of the old URL to the new URL for each product/category.
Announcement
Collapse
No announcement yet.
Allow Dots, Slashes and Spaces in Miva Part Numbers
Collapse
X
-
I'm sure by now you've figured out how to turn off the "Use Strict Validation for Codes" but I am going to hijack your thread because I now need to figure out how to help a store that has nothing but product codes with spaces in them. It is preventing the usage of the URI Management and now the store owner wants to make some changes to the product codes (they still have spaces in them) and wants to be able to redirect the old product code to the new one. Can this even be done using the old hand crafted .htaccess file (I can hear David screaming "nooooooooooo...").Originally posted by joseibarra View PostI'm sure someone will share the reason that Dots, Slashes and Spaces are not allowed in Miva Product Codes.
We are a reseller and carry products from 100+ different manufacturers and many use Dots, Slashes and Spaces in their part numbers.
Bigger problem, even if the store converted to spaceless Product Codes, it would still need to have the old spaced codes redirected.
How is this going to be handled?
Leave a comment:
-
Appreciate the ideas of which I will investigate.
I had already toyed with the idea of using a Custom Field (SKU is already used) so I think I will pursue that...
One manufacturer has part numbers like this which have a space and a slash:
Q-20-2D SCANNER/EMV
I think the Custom Field, modify the Product Display Layout page will work just fine.
Leave a comment:
-
Slashes are pretty much reserved on the internet to designate folder hierarchy in navigation. I haven’t seen a manufacturer using slashes in something like 20 years. I feel for ya Jose.
Leave a comment:
-
Yes, BUT. Make sure you are using URI Managment. You can't have a URL like /mm5/merchant.mvc?Screen=PROD&product_code=this/product/rocks.Originally posted by dreamingdigital View PostTry toggling this setting in the Domain settings part: "use strict validation for codes" checkbox.
Otherwise use the SKU field or anything else for your actual product code and modify the H1 tag display to have that custom field value instead. There are numerous ways around this.
Or, a URL like "/this/product/rocks.html". i mean you can, but it won't get you to the product you want.
Leave a comment:
-
Try toggling this setting in the Domain settings part: "use strict validation for codes" checkbox.
Otherwise use the SKU field or anything else for your actual product code and modify the H1 tag display to have that custom field value instead. There are numerous ways around this.
- 1 like
Leave a comment:
-
joseibarra, I have been lobbying for product code field validation on the forums for years to avoid those and other problematic characters used in URLs.Originally posted by joseibarra View PostI'm sure someone will share the reason that Dots, Slashes and Spaces are not allowed in Miva Product Codes.
We are a reseller and carry products from 100+ different manufacturers and many use Dots, Slashes and Spaces in their part numbers.
When we have to add those we have chosen to convert all the Dots, Slashes and Spaces to dashes so they can then be imported.
But shoppers using search engines are not going to replace the Dots, Slashes and Spaces in the part numbers they seek with dashes.
We added a Custom Field we populate and display it on the Product Detail page in a separate place but since we can't get that into the H1 Product Code we feel we lose shoppers.
Eventually the search engines might will pick up our Custom Field but it seems all our competitor sites are able to get the Dots, Slashes and Spaces into their H1s so Internet searches are probably going to our competitors instead of us - if we even show up at all.
Maybe there is some trick to it or some special coding that would do the job but it would be easier if Miva allowed Dots, Slashes and Spaces in Product Codes.
Create and/or use a product UPC custom field and use said field in your product page template HTML title, meta description, and h1-h6.Last edited by William Davis; 02-13-22, 07:29 AM.
Leave a comment:
-
Allow Dots, Slashes and Spaces in Miva Part Numbers
I'm sure someone will share the reason that Dots, Slashes and Spaces are not allowed in Miva Product Codes.
We are a reseller and carry products from 100+ different manufacturers and many use Dots, Slashes and Spaces in their part numbers.
When we have to add those we have chosen to convert all the Dots, Slashes and Spaces to dashes so they can then be imported.
But shoppers using search engines are not going to replace the Dots, Slashes and Spaces in the part numbers they seek with dashes.
We added a Custom Field we populate and display it on the Product Detail page in a separate place but since we can't get that into the H1 Product Code we feel we lose shoppers.
Eventually the search engines might will pick up our Custom Field but it seems all our competitor sites are able to get the Dots, Slashes and Spaces into their H1s so Internet searches are probably going to our competitors instead of us - if we even show up at all.
Maybe there is some trick to it or some special coding that would do the job but it would be easier if Miva allowed Dots, Slashes and Spaces in Product Codes.Tags: None
Leave a comment: