I have a very simple set-up with a static page showing a (static) collection of items.
I have 3 items in the collection (item #1, item #2, item #3)
I linked each item to its detail page aka static collection page as shown below:
Everything works fine until I apply user filters on the items.
Let’s say I apply a filter that selects only one of the 3 items (let’s say item #3)
Then, the link from this item to its detail page goes wrong. It is losing its connection to the proper static collection page; when I click on it, it goes to the detail page of item #1.
It looks like a bug to me.
PS: I don’t want a workaround like linking to an explicit URL; it doesn’t work in my case for reasons out of this topic.
Thanks Broberto!
Yes I can fix this in the back-end, but it will add complexity to the set-up and I want to keep it simple.
I would like to understand how things work on the front-end and whether this is a limitation or a bug.
I will ask support as you suggest.
As I said in the initial post, linking to an explicit URL (as in the workaround) doesn’t work for me.
It reloads the app and messes up with existing app load workflows.
I am sure you’ve got good reasons for this, but from my window, relying on indexes instead of IDs sounds like a terrible idea.
I understand you’re prioritizing dynamic collections, but I sincerely hope you plan to fix this asap, as it is becoming a roadblock in my project.
Exactly like in the linked workaround.
Binding a backend slug to the item detail page.
It kinda works, but reloads the app (URL are meant for external links if I recall)
Yes, sure, but going from a web page to another on the same SPA shouldn’t need a workflow action (Internet is made of links, right?).
This workaround is not satisfactory, and if the root cause is not corrected in a timely manner, I will not be encouraged to go much further with Weweb.
