You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello.
Now that we can disable URL-Alias for some content-type, I think we could benefit from having certains content-type alias not bein editable (ie, only generated).
Why is it needed?
The base idea of using URL-Alias is to be able to have your frontend router agnotic about URI, giving more power to the adminitrator to create pages. It also mean using a single endpoint to retrieve all (or almost all)your content-type
Sometimes though, for specific pages, it could be useful to enforce a specific layout on router side, while maintaining the single endpoint. This would also give the strapi administrator the information about the URL on frontend.
Ex: Having a list of tag with generated URL only (/tags/[slug]) would correspond on frontend side to a specific component (/tags/[slug].vue using nuxt 3 for instance) which would do some more complex behavior than a single page, displaying several articles related to the tag.
Suggested solution(s)
Adding another checkbox on content-type options to prevent Alias edition.
Disclosure
I used to maintain the "custom-link" plugin available on strapi marketplace but I don't have enough time right now to work on it right now. I guess I should focus on trying to improve this one instead.
The text was updated successfully, but these errors were encountered:
Hi @Norbz, I reviewed your request, and I can confirm that this can be achieved using the plugin settings. If you leave the checkbox blank the user will not have the url alias sidebar.
Enabled is displaying the sidebar, see setting below.
If you can confirm that this resolves your issue, I'll close this issue.
Feature request
Summary
Hello.
Now that we can disable URL-Alias for some content-type, I think we could benefit from having certains content-type alias not bein editable (ie, only generated).
Why is it needed?
The base idea of using URL-Alias is to be able to have your frontend router agnotic about URI, giving more power to the adminitrator to create pages. It also mean using a single endpoint to retrieve all (or almost all)your content-type
Sometimes though, for specific pages, it could be useful to enforce a specific layout on router side, while maintaining the single endpoint. This would also give the strapi administrator the information about the URL on frontend.
Ex: Having a list of tag with generated URL only (/tags/[slug]) would correspond on frontend side to a specific component (/tags/[slug].vue using nuxt 3 for instance) which would do some more complex behavior than a single page, displaying several articles related to the tag.
Suggested solution(s)
Adding another checkbox on content-type options to prevent Alias edition.
Disclosure
I used to maintain the "custom-link" plugin available on strapi marketplace but I don't have enough time right now to work on it right now. I guess I should focus on trying to improve this one instead.
The text was updated successfully, but these errors were encountered: