Component presentation border on my page is showing it as non-editable. Content-Border is showing as gray. It was editable earlier. I have verified the html of page and found no change. Can anyone suggest what may be the cause of the issue? Markup of page is as below:

<section class="main" role="main">
    <figure id="ball-box" class="widgetContainer">

  <!-- Start Component Presentation: {"ComponentID" : "tcm:33-1690", "ComponentModified" : "2014-07-30T16:49:20", "ComponentTemplateID" : "tcm:33-1675-32", "ComponentTemplateModified" : "2014-05-06T19:23:41", "IsRepositoryPublished" : false} -->

<figcaption id="homeWidget" class="homepage widget">
        <!-- Start Component Field: {"XPath":"tcm:Content/custom:HomePageWidget/custom:Header[1]"} -->
        Component content 1
        <!-- Start Component Field: {"XPath":"tcm:Content/custom:HomePageWidget/custom:Description[1]"} -->
        component content 2

        <a href="/Services/" class="learn-more"><!-- Start Component Field: {"XPath":"tcm:Content/custom:HomePageWidget/custom:Link[1]/custom:LinkText[1]"} -->component content 3</a>


<!-- Page Settings: {"PageID":"tcm:33-1671-64","PageModified":"2014-07-25T17:35:32","PageTemplateID":"tcm:33-1673-128","PageTemplateModified":"2014-04-23T15:03:59"} --><script type="text/javascript" language="javascript" defer="defer" src="http://cmsurl/WebUI/Editors/SiteEdit/Views/Bootstrap/Bootstrap.aspx?mode=js" id="tridion.siteedit"></script>;
  • 1
    Maybe the component is checked out by someone else?
    – Nuno Linhares
    Commented Aug 4, 2014 at 11:47
  • Hi Nuno, I can see, component is not checked out in CMS. But, I can see lock while component presentation is rendering on the page in site edit UI. Actually, earlier have done other work too on this page which I now rolled back. But found that now my component is showing non-editable. Please suggest.. Thanks. Mukesh Commented Aug 4, 2014 at 11:51
  • It is possible that the component is localised at a lower publication and checked out there, hence the lock you're seeing. Commented Aug 4, 2014 at 12:06
  • Thanks Nickoli, But the publication I am working on is the lowest one and I have verified that it is not localized or locked anywhere.. Commented Aug 4, 2014 at 12:26
  • 1
    What does it say if you click on the padlock? Usually Experience Manager will try and offer an explanation. Commented Aug 4, 2014 at 12:40

1 Answer 1


I have got the answer of my question. Below is the steps I have analyzed and corrected to resolve the issue:

  1. BluePrint context setting in CMS was not correct.
  2. Although it was correct in my SiteEdit_config setting file.

I have corrected that and all are working now.

Below is little bit more explanation:

Actually, my component was ccraeted and coming from parent publication(suppose P) and was used in page of the child publication(suppose C). In my blueprint context setting, context for component was configured as C.

Earlier I was thinking that experience manager reading context setting from SiteEdit_config file, which was already correct. But later found that it is reading setting from blueprint context setting.

I have configured blueprint context for component as parent publication(P) and now everything started working.

I hope the issue and resolution is clear now..

Thanks. Mukesh

  • Can you explain a bit more what you did to resolve the issue so someone else with a similar issue can be helped too :)
    – user219
    Commented Aug 4, 2014 at 13:07
  • Hi jarnohenneman, I have provided more detail around issue and it's resolution. I hope now it will be more understandable. Commented Aug 4, 2014 at 13:22
  • 1
    you are mentioning a SiteEdit_config settings file, I'm assuming that is the one from DD4T? When using DD4T you indeed have to make sure that both your DD4T configuration on your website and the XPM configuration in the CMS are both valid and matching. Commented Aug 4, 2014 at 16:12
  • 1
    +1 to Bart's comment, I tagged the question with DD4T. It's important to note that SiteEdit_config only applies for DD4T and the context isn't really an issue by itself. Though using a Parent Publication for Component context is typical, the real issue is either the mismatch in configuration or possibly one of the more typical reasons for locked items (no scope, no permission, item edited by someone else, workflow, etc). Commented Aug 4, 2014 at 20:38

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.