Sitecore
Lightning Tip: What to Do When Your Front End Website Opens in Experience Editor
April 04, 2018 Molly Zglobicki

Edit the sc_mode Query String Parameter in the URL

When you edit the display mode query string parameter value for sc_mode from “edit” to “normal” you can view the page you are currently working on as a user would. 

To do this, for example, you would change the following URL from: http://coriadev.coria.com/?sc_mode=edit&sc_itemid=%7bF2018DA8-BC… 
To: http://coriadev.coria.com/?sc_mode=normal&sc_itemid=%7bF2018DA8-BC… 

Similarly, if you were to truncate the URL and remove everything following “?sc_mode=normal”, you would be viewing the site homepage in normal mode (i.e. http://coriadev.coria.com/?sc_mode=normal).

 

Clicking the Close Experience Editor Icon

You can achieve the same effect by clicking the “Close” icon in the Experience Editor ribbon, as shown here:

Front end site

Note: if you don’t see the ribbon, click the arrow in the top-right to Toggle the Ribbon as shown here:

front end site 2

 

Ask your DevOps Team to Create a Separate Content Management Server URL

In non-production environments and smaller Sitecore installations it is common to be able to access Content Management and Content Delivery functionality from the same URL.  We find it helpful to use a second, unique URL for accessing Content Management. This will make it so that any cookie set by the Experience Editor does not affect the Front End website(s). To do this, the following steps will need to be taken:

1. Create a new DNS entry that points to the IP address of your Sitecore installation

(Ex: authoring.example.com)

  2. Ensure IIS binding for authoring.example.com in IIS Manager

(In the following image, wildcard bindings are used):

front end site 3

 

Now when you want to see your website you can use www.example.com when you are looking for your Front End Website and authoring.example.com/sitecore/login when you want to login and update your content in Sitecore.

Molly Zglobicki
Quality Assurance