6

We are using SDL Web 8 and DXA 1.6. When we go to CME -> Sites (from left navigation) and select any site that is supposed to show the website with XPM (i.e with blue pen icon at top right corner), it is not showing in my case.

Can any one please let me know what configuration I need to do here?

Adding more info: We have two prod cms. One is SSO enabled other is non-sso. For sso enabled cms site edit is working ie when we go to CME -> Sites (from left navigation) and select any site it is showing the blue pen icon for site edit. But for non-sso that icon is not coming.

  • Adding more info: We have two prod cms. One is SSO enabled other is non-sso. For sso enabled cms site edit is working ie when we go to CME -> Sites (from left navigation) and select any site it is showing the blue pen icon for site edit. But for non-sso that icon is not coming. – user2803 Nov 28 '18 at 12:55
  • Can you confirm that the (Staging) CD Environment of both CMSes have a Preview Service Capability registered? – Rick Pannekoek Nov 29 '18 at 19:59
1

As Nick says, there could be lots of reasons why the XPM icon is not showing.

If it were me, then I'd start by checking whether the Page Settings HTML comment and the XPM (a.k.a. SiteEdit) JavaScript tag appears in the source of the published page. For example:

<!-- Page Settings: {"PageID":"tcm:9-259-64","PageModified":"2016-08-04T14:43:31","PageTemplateID":"tcm:9-264-128","PageTemplateModified":"2016-10-18T12:37:03"} --> <script src="http://[CMEURL]/WebUI/Editors/SiteEdit/Views/Bootstrap/Bootstrap.aspx?mode=js" id="tridion.siteedit">

If they are present, then you may want to check the details (IDs, URLs, etc.) and the console tab in Chrome Developer Tools for any conflicting errors.

If they are not present then you'll need to investigate further. You may want to start by looking at Bart's answer here: https://tridion.stackexchange.com/a/15100/71

Adding some more details of what you've already looked at to the ticket would also help too.

  • We have two prod cms. One is SSO enabled other is non-sso. For sso enabled cms site edit is working ie when we go to CME -> Sites (from left navigation) and select any site it is showing the blue pen icon for site edit. But for non-sso that icon is not coming. – user2803 Nov 26 '18 at 12:16
  • @user2803 - That is useful information for anyone else looking to help. Can you add it to your original question too please? – Jonathan Williams Nov 26 '18 at 12:31
1

At the very basic surface, a Tridion system has 3 core nodes: CM, DXA Staging (Preview) web app, and DXA Live web app. XPM should be set up on the Staging web app, not the Live. So make sure you're hitting the Staging instance.

If the above doesn't solve your issue, as far as what configurations you need to make, there is more than a handful of them. So it's not a simple answer. You're going to have to get some technical training on this because there are a lot of concepts and moving parts that make it all happen. Start out by carefully studying the docs and trying things. Here is the chapter specific to XPM, but you'd need to already have a strong grasp of the other Tridion concepts and configs before diving into XPM configs: https://docs.sdl.com/LiveContent/content/en-US/SDL%20Web-v1/GUID-E7D54121-70A2-4FA6-A516-8ADB8E45AC13.

  • The explanation of the 3 parts of the system and link to configuration help answer the question. If the offer for help is free (as in beer), just post them here otherwise a disclosure can help explain your affiliation per the Q&A model. – Alvin Reyes Nov 24 '18 at 13:22
1

Although there are indeed a lot of moving parts to XPM, it should actually be quite simple to get it to work with DXA, because it has built-in support for XPM.

As Nick mentioned, XPM is typically only enabled on “Staging” and DXA determines whether XPM should be enabled or not by checking whether the CD Environment has a Preview Service Capability (assuming you are using Topology Manager based publishing).

You can check the _all.json file in BinaryData\{PubID}\config to see whether it determined it is a “Staging” (XPM enabled) site or not.

If it is XPM enabled, you should automatically get XPM markup in your output if:

  • Your Page Views use @Html.DxaPageMarkup()
  • Your Entity Views use @Html.DxaEntityMarkup() and optionally @Html.DxaPropertyMarkup()

Note that these HTML helpers are not only used for XPM markup, but also for Semantic markup (RDFa), so it’s always a good idea to sprinkle your Views with this markup.

  • yes we are using Topology Manager. Can you please tell me exact folder path of _all.json? And this file will be on CD server, right? – user2803 Nov 28 '18 at 13:11
  • The file should be on your “presentation server”, i.e. the server which hosts your DXA Web App. I already mentioned the path (which is relative to where your DXA Web App is deployed). – Rick Pannekoek Nov 28 '18 at 19:41
  • It is not working. The DXA Web App is common for both sso and non-sso cms. I can only do xpm on sso enabled cms. But in non-sso cms xpm is not working. I want to enable it in non-sso cms as well. – user2803 Nov 29 '18 at 10:41
  • A single DXA Web App for multiple CMSes? That's interesting... can you elaborate on your setup and what determines which CMS should be used? – Rick Pannekoek Nov 29 '18 at 10:58

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

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