Relative URLs and Custom Content Boxes
Let me know if this sounds familiar. Maybe you’re a new or existing Extended Enterprise customer and you’ve just built a custom page and linked to it with a custom content box on another page. You’ve just copied and pasted the URL into the custom content box and clicked save and you’re filled with excitement. Next thing you know you got an email from someone saying they’re getting a 404 error when they access the page.
Or maybe you’re on pins and needles thinking about an upcoming change to your custom domain and you’re thinking “Oh no all of those URLs are going to break when we make the change”
Well strap in! You’ll love this trick.
But what if I told you don’t have to (and probably shouldn’t) use the full URL?
Instead of using the full URL you can actually use what’s called a “relative URL” to populate the URL field inside of a custom content box.
So using our example above:
https://university.docebo.com/pages/118/docebo_learning_analytics
Becomes:
/pages/118/docebo_learning_analytics
Why It Matters!
This is important because it future proofs your platform from any future domain changes as well as allows you to use the same page across multiple domains if you’re an extended enterprise client. It works because it will fill in the root domain of whatever domain the user logged into the LMS with which ensures they won’t see any of those pesky 403 or 404 errors
