Are you using a collection list to display your data on the page that you want to link from? That is what I would recommend.
If so, when you link to a page like you are in the editor, WeWeb will send along a query string parameter with key = pageCollectionIndex. This will identify to the editor what data to populate the page with.
I’m not sure what that location.href will do in the editor. Haven’t tried that to an internal page.
Thanks for the reply! I didn’t think to do that, and your idea should work except for a possible bug. When I filter or sort a static collection, the “pageCollectionIndex” uses the new location in collection list as the query. So if I filter the collection to match the organization of the event, it will always go to , even if it should go to . See it in action below:
That does work better for the ascending, but that is still a problem for two reasons:
When I filter the static collection list with user input, by “State” for example, the index numbers change.
I don’t think sorting the static collection solves the original issue, how to link to another static collection item, because the collection list has to be filtered to one result and that will be index . I don’t see any way to filter the static collection with at the collection level when loading the page.
Hmm, I don’t see that option for a static collection. In either case, I’m worried that filtering the static collection that way will affect other users. If one user filters by State at the collection level, won’t the other pages be removed for everyone?
Unfortunately, it seems like linking directly to a static collection page is not ready. Perhaps custom code would fix, but that may not work in the editor. I have switched my site from static to dynamic and back to static, looking for the best solution, and this is another roadblock.
Thank you for your reply and action on this! I may just wait and see if it gets traction on the roadmap because I am waiting on a few more features before launching (need rich text in forms, want xano social auth). Static collection lists and pages seem to load much faster, and SEO will be vital for a new public site.