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
In some cases we have links like "Cookie Settings" in the footer which trigger a "window.cookiehub.openSettings()" javascript function. At the moment we add those static instead adding them via navigation tree on the page settings tab and using an external link.
Proposed solution
It would be cool if we get a new option in the page settings tab for the page type "external link" so we can prefix the url with our own and not given https http or tel and mail... we want to add stuff like "javascript:window.cookiehub.openSettings();"
The text was updated successfully, but these errors were encountered:
I'm not sure if we want to support javascript: based Url in the CMS, as that could be critical from security side. What I could think about supporting maybe relative Urls or even some static Urls via an own provider.
In your case I would maybe even go with some hash based url example #cookiehub, but that would require support for relative Urls.
But I'm not sure if this really should be something a Content Manager should take care of or it even is more responsible of a Theme developer to always make sure that such Button/Link is always rendered in the Footer for GDPR reasons.
A workaround currently for such issue would be to Tag the specific page and then replace the url inside the code with the one you want.
Problem description
In some cases we have links like "Cookie Settings" in the footer which trigger a "window.cookiehub.openSettings()" javascript function. At the moment we add those static instead adding them via navigation tree on the page settings tab and using an external link.
Proposed solution
It would be cool if we get a new option in the page settings tab for the page type "external link" so we can prefix the url with our own and not given https http or tel and mail... we want to add stuff like "javascript:window.cookiehub.openSettings();"
The text was updated successfully, but these errors were encountered: