We inherited a solution that consists of a number of sites build with MVC. The solution has been upgraded to 10.2(.1) and we have added a new headless site using SXA and JSS. So we have a dozen "regular" sites and 1 SXA site.

We noticed that we have an issue in the experience editor when using the navigation bar in the SXA site. Apparently the site resolving is not correct on that part as it links to the first non-SXA site it can find.

enter image description here

The url when the editor opens is like /?sc_mode=edit&sc_itemid=...&sc_lang=en&sc_version=1&sc_site=portal. But when we then use the navigation bar to go to another page we get an error because the sc_site parameter in the url is wrong: /site1/?sc_mode=edit&sc_itemid=...&sc_lang=en&sc_site=site1&sc_ee_fb=false.

When we manually change the sc_site parameter the page works.

How can we get the navigation bar to use the correct site?

1 Answer 1


We checked the SXA site manager first and that seemed all ok.

We patched the <siteResolving> config section to include all mvc sites and have them resolve after the SXA site(s). This works and shows in the SXA site maneger, but it does not solve the issue.

What did solve the issue is adding a targetHostName in the site definition of the SXA site. After doing that, suddenly the site resolving in the navigation bar was ok.

To be honest, I didn't have the time yet to investigate why this is the case. But as it solved an annoying issue for us I decided to share it here as it might help someone else. Or maybe someone actually knows why - please share if you do, I am still curious ;)

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.