Hi, I used a collection page to display different properties. On my editor the URL path of one variant is displayed as https://website.com/brand_new_modern_single_attached_house_and_lot_for_sale_in_fortunata_para_aque
However, on my published site it shows as https://website.com/_93869/
Is there a way I can display the URL displayed on the URL path of the editor on my actual page?
Hi @Walds!
That shouldn’t be happening. Could you share a link to the editor so we can have a look?
Thanks!
Joyce
Hi @Joyce!
Thank you for responding. Here’s the link: Editor - WeWeb
attached is a photo of what it looks like in the editor.
Thank you!
Walds
My pleasure 
Mmm ok, I’m wondering if it may be the format of the slug.
Could you try with a slug that looks like this brand-new-modern-single-attached-etc instead of underscores?
Alright, we’ll try adding a new column for the paths.
Thanks!
Cool, thanks! Let us know if it solves the issue or not. If it doesn’t, I’ll take another look
Hi @Joyce, I’m still having the same problem with the URLs.
We already created a slug column for the urls.
However, it still appears as random numbers on the published pages.
Hi @Walds 
Mmmm I just had another look and can’t figure out what might be going wrong. I’ve forwarded your question to the tech team.
We’ll get back to you as soon as possible
Hi @Walds
I made this small change to your “meta” collection:
Adding the result key means WeWeb is now getting the array of items you need, not an object containing the array. This enables the Collection Page to work more fluidly.
When you’re ready, can you re-publish your site and let me know if this solved the issue with the slugs?
Cheers!
Thank you so much @Joyce! It works perfectly now.
Where do we do this change? I have the exact same problem.
Hi @yunus
Where can you add the “Result key” to ensure you are getting a list of items from the API instead of the entire object?
It’s in the “Configuration” step when you setup a REST API collection:
Does that help?
Interestingly, I am using Airtable and don’t see such options. Any ideas?
And I am using Static Collection as my data will not be changing after the build.
My homepage is my listing page, and from there every item is connected (tried URL with parameter and workflow with parameter) to a page > Report 2 (in this instance).
Both options work fine when previewed on WeWeb, but broken when published.
URL seem to break the linking, and workflow one doesn’t work when the site is published.
URL link to takes the page to a link with random id (see image), not sure where that number is coming from.
It is definitely related to my URL path, but couldn’t crack the rationale. When it is a collection page URL paths are not editable at all, I need to recreate the collection page by copying it to edit the page name.
Below some of the elements related to the explanations.
Are you using a static collection page as well?
Very silly question but what is a static collection page? Not sure how to set up different types of collection pages.
No worries, that’s something were we want to rework the UX in our product.
Static collection pages get prerendered and generated during build time (better for SEO), while dynamic ones are generated frontend side when a user goes to them.
You’ve got the full explanation here: How to use the Pages | Weweb documentation
