#dominoforever | Product Ideas Portal

Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.

For more information and upcoming events around #dominoforever, please visit our Destination Domino Page

Handling of added url parameters like ?fbclid=

If a public website is powered by domino, it is often wished, that urls shared to social media, i.e. facebook. But this plattforms sometimes add url parameters to an url, if this is clicked. Facebook i.e. adds often ?fbclid=xxxx. This causes an error on the domino side. See also https://www.mindwatering.com/SupportRef.nsf/webpg/0857F020A5D9B04F85258524001BF3AE

The workaround is, to build all urls with ?open at the end, but that makes the url worst readable and it isn't possible in all cases. For instance, the domino blog template doesn't do that.

Domino should handle url parameters, that are no domino commands without throwing an error. I could be a database setting, if this parameters should throw an error or not.

Otherwise that is a big disadvantage to use domino as a server for public websites.

  • Guest
  • Jul 7 2021
  • Needs Review
Domino
  • Attach files
  • Guest commented
    16 Mar 06:04pm

    I agree it should be handled gracefully.


    I fixed it by adding this code in my head:


    (function() {
    var param = 'fbclid';
    if (location.search.indexOf(param + '=') !== -1) {
    try {
    var url = new URL(location);
    url.searchParams.delete(param);
    history.replaceState(null, '', url.href);
    location= url;
    } catch (ex) {
    // pass
    } }
    })();



    Theo Heselmans

  • Guest commented
    16 Mar 11:42am

    it's e.g. an issue with the blog template. Currently my workaround is a redirect to the root host URL.

Related ideas