When we get requests to forward site traffic to one domain, say www.example.com, we setup redirect that forwards all traffic to this domain. So all domains added to the site (exaple.org, example.net, etc.) and all their www subdomains, along with trial domain, will forward to www.exapmle.com.
This redirect rule causes a conflict with landing pages functionality, as domains are forwarded by web server before client request gets to CMS. Hence, custom landing will only work for domain everything is forwarded to.
It is obviously a conflict and we will work to resolve this by integrating domain forwarding functionality into CMS and/or Portal settings, making forwarding routes transparent and editable by partners.
Right now, if you have requested us to create redirect for your site in the past and having issues with landing pages functionality, the following can be done:
- We can disable redirect altogether, thus removing conflicts.
- We can change redirect to be more specific, forwarding only (for example, no pun intended) example.com to www.example.com and example.net to www.example.net. You’ll be able to use custom landings for www subdomains but not root domain, in this case. We can also only forward you trial domain to one of the live domains.
- You can wait for domain forwarding to be integrated in future releases, which probably will be the case for sites that only have one domain.
To recap: landing pages functionality is not at fault here, it’s a conflict with domain forwarding functionality that hasn’t been integrated or released yet, and that we setup on partner requests.
Hope this makes sense.