Extra domains added to primary domain - issue

Hey guys,

So, looks like adding another domain to your parent domain and assigning a specific page to that new domain does not work.

Case in point:

  1. Added creative-dude.com to my a3creative-solutions.com partner portal as a secondary domain. https://prnt.sc/pewnvd

  2. Domain shows in my a3creative-solutions.com/admin

  3. I can assign a landing page to it, in this case the landing page is: /welcome
    https://prnt.sc/pewnat

  4. When I click into creative-dude.com it just takes me back to the a3creative-solutions.com landing page.

So, looks like this is not working…suggest removing this option until it works.

I have 2 sites I’ll be migrating over from BC that use this functionality, so I’ll have to wait until this is corrected.

Note, this was all done before 4.8.2 so assuming it would be fixed during this sprint, but it wasn’t.

Aaron

(I’ve got nothing as far as your technical concern here, but the fact that you own creative-dude.com is pretty neat.)

Hells ya! Someone needed to scoop that domain… lol!

1 Like

I have this working on one of my client sites, but have not been able to get it working on my own partner site. Not sure what the difference is… perhaps it’s a DNS thing?

@alex.n or @vlad.z do you have any news on this? Please see thread above.

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:

  1. We can disable redirect altogether, thus removing conflicts.
  2. 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.
  3. 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.

1 Like