There is no change required for on-page editing to work. You most probably have differences in your environments (content, access rights etc) that is causing this, or maybe some script error or something.

In the DXC environment, can users see content in the page tree? Please provide more details about where the 2 editing experiences diverge. Also please provide version information.

Thanks Mattias for replying.

We have compared access rights and checked for any script errors. But there is no difference between the two environments.

Hi Bob,

Users are able to see, update and create content without any issue. According to our research, there is only one change between the two environments that DXC environment is 64 bit operation and the local environment is 32 bit operation. We are using 10.10.1.0 version for both the environments.

Thanks!

Hi Saurabh.

We have done a ton of on-premise and DXC Service solutions, where no configuration changes were required to enable the on-page editing. Moving between 32bit and 64bit should not make a difference for this functionality, unless you see any raised errors. Please try these action items:

1. You can be sure that no access-right settings are disabling the editing by checking for a "lock" icon.

2. Like other, I would recommend to look at the Browser Console, as it would quickly reveal any Javascript errors, which may prevent the authoring experience from loading correct. If you see anything that could be the cause, try and turn on the debug flag for DOJO.

Update your Episerver.Framework.config with this:

3. You should check your application logs to see if any Episerver Web-APIs are throwing errors, preventing the authoring components to load.

Let us know how it goes. 

/Casper Aagaard Rasmussen

Hi Casper,

Below is the error we found in DXC environment. We don't know if this is the cause for this.

MessageHub.js:96 WebSocket connection to 'ws://xyz/EPiServer/Shell/socket/endpoint/' failed: Error during WebSocket handshake: Unexpected response code: 200

[Pasting files is not allowed]

Hi Saurabh.

Thanks for sharing that error message. 

Have you tried disabling the use of Web Sockets in Episerver, for the sake of testing if this is causing your authoring interface to malfunction? You can also validate the steps outlined here, as they are required for Web Sockets to work.

https://world.episerver.com/documentation/Items/Developers-Guide/Episerver-CMS/9/User-interface/websocket-support/

/Casper Aagaard Rasmussen

Hi Casper,

Thanks for your reply!

In the link given by you, there are 2 steps to get WebSockets working.

1. <system.web> <httpRuntime targetFramework="4.5" /> </system.web>

We have targetFramework as "4.5.2". We guess this should not cause any issue, should this?

2.  <appSettings>

      <add key="ValidationSettings:UnobtrusiveValidationMode" value="None" />

     </appSettings>

This is already as it should be.

We pushed this change to DXC environment but the WebSocket error still persists.  

Next we will try to disable the WebSocket and check.