🦋 on page target (product CTA, tag CTA, layout) change behavior for targets without "/"

[Tirodem]

Currently, on layout, tag CTA and product CTA (and any widget link) :

• if I'm on a CMS page ( {site}/{slug} ) :
  • if my target is /target, the link will be to {site}/{target} , that is OK
  • if my target is target, the link will be to {site}/{target}, that is OK
• if I'm on a page with another level on URL construction ( {site}/{path}/{slug} ), like cart, or product page :
  • if my target is /target, the link will be to {site}/{target} , that is OK
  • if my target is target, the link will be to {site}/{path}/{target}, that is KO ❌

For exemple, link from product page to CMS page news that is normally on {site}/news will be {site}/product/news and will lead to 404 error.

For now we can bypass the issue by adding 100% of the time the "/" at the begin of the link target, but I think it's better to have the same behavior, either you fill the / or not.

⚠️ Don't make a hard fix will force-adding a "/" in the link construction) otherwise it'll break the links already setted with "/".
What we need to do here is :

• if the target is slug : link might be {site}/slug
• if the target is /slug : link might be {site}/slug (beware of the {site}//slug effect)

[coyotte508]

We can force it in the admin UI, before sending to the backend.

Only allow full URLs (https://externalbootik.com) or urls starting with / are allowed.

It's not complex

[Tirodem]

@AmadouAgiltoo to check when you have time, I'm not sure it's still a thing