Skip to main content

Why does a link inside custom content or custom notification not work?

  • Updated

This behavior occurs when using a URL with https (with the “s” at the end) that matches the instance, causing the editor to convert it into a relative path and the link stops working properly.

Reason for the behavior

When customizing content or a notification from the platform editor:

  • If a URL with https is entered that corresponds to the same instance
  • The editor detects that it is an internal URL
  • And automatically replaces it with a relative path

As a result:

  • The link may stop working properly

How to fix it?

To avoid this behavior, it is recommended to:

  • Enter the URL using http:// (without the trailing “s”)

For example:

http://instance.takesecurity.com/

This way:

  • The editor interprets the URL as external
  • It does not replace it with a relative path
  • The full URL is maintained and the link works properly

Considerations

  • This behavior depends on the content editor
  • It only happens when the URL matches the instance
  • It does not affect external URLs from other domains

💡 Best practices

  • Use http:// when linking to your own instance
  • Verify links before publishing content
  • Test the links in a testing environment

Related to

Related articles