Developer forum

Forum » CMS - Standard features »  "No layout selected" when using Visual Editor

"No layout selected" when using Visual Editor

Adrian Ursu Dynamicweb Employee
Adrian Ursu
Reply

Hi guys,

We have noticed that the "No layout selected" message is displayed even if the layout is selected on the website settings.

The problem seems to be related to the use case where we have multiple websites with different domains and the admin is using the visual editor.

If you open the admin interface from the domain of the website 1 (HTTP://website1/admin) and you try to edit website 2 using Visual Editor, you get the "No layout selected.." message.

If you open the admin from website 2(HTTP://website2/admin) and you try to edit website 2 using the same Visual Editor, it works.

I see a lot of benefits from letting the users manage multiple websites from the same interface without having to logout/login on a specific domain (the way it was before the visual editor). Can this be accomplished even for setups using different domains for each website?

I have tried this in both 9.9.x and 9.10.x versions.

Thank you,

Adrian


Replies

 
Kim Søjborg Pedersen
Reply

Hi Adrian,

Did you ever find a way to solve this?

 
Adrian Ursu Dynamicweb Employee
Adrian Ursu
Reply

Hi Kim,

No. I have to make sure that I have a domain set on each website and that the Admin interface is opened from that domain. Otherwise it does not work. I am sure this is not the right solution for the issues but until I get a better solution, I have to make it work :)

Adrian

 
Kurt Moskjær Andersen
Kurt Moskjær Andersen
Reply

I've had the same problem with a website running DW 9.9.8.

I've reported it to Dynamicweb and was told that it was fixed in 9.12.

My workaround is to require SSL in the backend and make sure that the checkbox with "The selected domains can only access this site" is not checked, in the website settings of the main website.

This can lead to other issues though, I know :)

--
Best regards
Kurt Moskjaer Andersen

 
Tim Koster
Reply

Sorry, bit late. 

We've run into this exact issue, but adding the website domain from which you're accesing the backend to the domains of the website which you want to use the visual editor for has fixed the issue for us (at least untill the consequences catch up).

 

You must be logged in to post in the forum