If you put 2 identical titles into the admin datagrid (so the first column), both of them are correctly displayed in the databound table. But if you click on any of the two, only one and the same is always displayed on the Item page.
Shouldn´t this item field be unique, to create unique URL´s?
indeed, fields that are used to compose a URL should be unique.
this is one of the primary guidelines for creating valid dynamic pages.
you can read about it more here:
so - it’s not a bug - it’s just something to keep in mind when creating dynamic pages and their URL patterns.
hope this helps…
Thank you for answer. But there is something I do not understand. If I have a site with second hand goods, and I have category identifier and a description, nothing else, how do I guarantee uniqueness?
Example:
Category: Smartphones
Description (input by seller): Samsung S7 Edge
There might be many more people who want to sell their S7 Edge, typing the same description, so they would all get the same URL. Or, shorter, how do I guarantee uniqueness if uniqueness is not available in the real world (there are many S7´s Edge out there, or IKEA book cases). I read thru the article again, but I can´t see the answer.
Thanks for any help you can give me.
just add the ID field to the URL pattern.
so your URLs will look like this: “…/{category}/{_id}”
IDs are guaranteed to be unique.
That would work. But then:
“…/{category}/{_id}”
would return exactly the same result as:
“…/{_id}”
or am I mistaken? In other words, the moment you add a unique key, all prefixes are superfluous?
P.S. Greatly appreciate the Saturday support.
yes, once you have _id there it’s already unique and other prefixes are superfluous.
it’s up to you if you want to keep them there to make the URLs look nicer.
Now I get it, thanks Ziv. Might I suggest that this info is added to the article
https://support.wix.com/en/article/making-dynamic-page-urls-unique
for I doubt this is immediately clear to everybody. It also means that an external link to an item (=from another site or a bookmark) containing a prefix will return a 404 error once any prefix description has changed (in our example if a user changes his description to “Samsung S7 Edge /32GB” and the only way to prevent this is not using prefixes in the first place, but only the _id. It would result in less readable URL´s, but it prevents 404 errors (or at least an empty collection) if coming from an outside link.
Thanks Giri,
I’ll ask our tech writers to add it.