New website VS old website domain behaviour

António Ramos

Posted on 21/06/2017 11:48:50

Hi,

We have a customer that developed a new website in the same solution but in a new different website (AreaID).

He had multiple sub domains (without setting in area domain area) that were opening the default website (AreaID = 1) and all was working fine.

After publishing the new website, all this unregistered domains in the website settings are still opening AreaID = 1.

There is any way to force all subdomains to open this new website? (wildcard or something in domain settings)?

Thanks for your help,

BR,

António Ramos

Replies

Nicolai Pedersen

Posted on 21/06/2017 15:08:31

Nope - you can disable areaid=1, then it will go to the next one.

António Ramos

Posted on 21/06/2017 15:14:18

Hi Nicolai,

Thanks for your answer. We had made a test in 8.9 and it throw 404. This is only for DW9 or should be also in DW8?

BR,

António Ramos

Posted on 26/06/2017 10:17:34

*bump*

Nicolai Pedersen

Posted on 26/06/2017 12:44:44

I do not understand your second question.

António Ramos

Posted on 26/06/2017 13:08:05

Hi Nicolai,

Sorry for the confusion. Let me try to explain better.

I made a test in DW8, where i disable the first website and by your logic in previous post, this should open first page of second website (next one) but instead had thrown 404 error.

My question is regarding your affirmation "you can disable areaid=1, then it will go to the next one". We tried in DW8 and this don't work. Is this logic available for DW9 and not for DW8? Or should both versions working with this logic?

Hope it's more clear,

BR,

António Ramos

Posted on 28/06/2017 16:17:18

*bump*

Nicolai Pedersen

Posted on 28/06/2017 16:24:43

It works like that on both DW8 and DW9. I have no issues with it.

You must be logged in to post in the forum

Developer forum

New website VS old website domain behaviour

Replies