I’m following the instructions here on static colleciton page navigation.
The suggested method avoids “link to page” and recommends instead to create an action, navigate to > collection page. And according to the tutorial, that’s all what’s needed for the navigation to happen. No need to enter the parameter.
The item from which the navigation is happening is itself coming from that same static collection list. When clicked it’s supposed to take you to the collection page (details page of the collection item)
The test workflow button supposedly works. But clicking on the item doesn’t seem to work in the preview mode or production. In the preview mode, the left log panel shows successful action but nothing happens on the page. In production, nothing happens on screen too and no errors are logged in the console.
@jptrinh Hey Jean Philippe, I’ve tried to do it with the link property but couldn’t figure out how to choose the relevant page to show from the collection since you have to choose the index of the list items (hard coded). Is there a way to send the user to the relevant collection item’s page?
Can you illustrate when you say hard coded?
I had a collection list, and for each of the repeated item, was a link that pointed to a Static page collection. So I didn’t need to indicate the current item index.
Yes. Using the link approach, I too don’t find a way to choose the actual item that the user will navigate to. So I’ve selected collection page and that’s it.
However when I use the link approach I’m always taken to the top result in the static collection (independent which of the items is clicked on).
@Joyce It’s been a week since I’ve been waiting on this and I’m still unsure if this is a bug or not. But followed the instructions and tried a dozen workarounds and it’s not working. Mind taking a look and sharing what you think it might be?
As an alternative to the direct link to a static collection page, you could use the the ‘Navigate to’ module in a workflow and utilise the path option.
The one downside to this is that it won’t work in the editor, but will work in the live version.
You want the path bound to be whatever you have bound to the URL selection of the static page:
@matthews thanks Matthew, your internal url path approach works. But still don’t understand why the other straightforward ways to link to a collection page are failing.
Same problem, here - if you treated this during an office hour, could you link the youtube video?
It seems to be a bug (the straightforward option to “link” to a “collection page” should precisely do what is says ;-)) but maybe there’s another explanation?
thanks @davhad !
In the meantime, I reported it too, and received the answer that it’s a limitation of weweb: with the “link to > collection page” we can only go to the a record of the same collection we are currently in…
Mmm… So do you mean we can only link from a collection page item to another item from the same collection?
If this is intentional or a framework limitation (don’t see how…) then maybe this should be reflected in the editor. Otherwise it still stands out to me as a wrong implementation which could use a fix
Indeed, only in the same collection (but even that didn’t work, so i don’t bother with that “link to collection” option anymore).
Yes, it really seems like they had to stop that feature while doing it.
Anyways, just so you know, my workaround for the collection pages is to
in my backend DB, create 3 column
create a slug column
create a collection path column (with the constant formula of the name of the collection)
create a complete slug column (/collection_path/slug)
in Weweb
create a variable for the domain url
and everytime I want to link to a collection page,
I set “Link to URL” (and not collection) and bind it
select my variable “domain url”
add the item “complete_slug”
It takes a bit more time, but not that much more.
And it only works in production, but at this point, I’d better create a subdomain to test it out, so…
but thanks for the initiative!