nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

In Context Edit

phenom

I have installed LiveSite 3.1.0 on Windows 2003. Now, I am trying to implement in-context-edit for a few pages. For testing purposes, I have created a component with only a string item and put it on a page. But when I try to view the page in the livesite runtime environment, I am unable to view the in-context-edit link which would enable me to edit the component directly on runtime environment. Also, is it possible to switch on/off the in-context-edit link on the livesite runtime environment?

Find more posts tagged with

Comments

mvusthipalli

Also, is it possible to switch on/off the in-context-edit link on the livesite
runtime environment?

-- The question is, let's say if the in-context edit is enabled in the component of a page which gets deployed to DEV, Staging and then PROD runtime servers, how would we handle not to have in-context edit on STAGING and PROD but only on DEV?

vpatel

I have installed LiveSite 3.1.0 on Windows 2003. Now, I am trying to implement in-context-edit for a few pages. For testing purposes, I have created a component with only a string item and put it on a page. But when I try to view the page in the livesite runtime environment, I am unable to view the in-context-edit link which would enable me to edit the component directly on runtime environment. Also, is it possible to switch on/off the in-context-edit link on the livesite runtime environment?

In-context-edit (ICE) works in the authoring/preview environment only. It is NOT meant to work in runtime for very obvious reasons.

With that said, there is a "edit this page" link that you can have on pretty much any page. This link will work in Authoring/Preview as well as Runtime. In Runtime, it will simply pull up the corresponding page in TS.

HTH!

mvusthipalli

Thanks VPatel......

miroperez

Actually you could do this with a little more component work. If you create a component based on the edit page component, then add an external to that component which interrogates the RequestContext.getMode() to determine if you are in runtime and puts the mode in the xml model. Then your xsl can look for the presence of this xml element value and output the button or not output the button depending on the value of the element. I've understood some customers have gone as far as checking for a user login and checking their role in runtime to determine if the button should be shown, but this is obviously very customer deployment specific.

Miro

phenom

Thanks Miro.

Interwoven/PageElement/PageEdit/InContextEdit.component adds another parameter (isInContextEdit=true) to the end of the query string. I did the same in my component. But when the link is clicked on the runtime environment, the edit mode does not change to 'In Context Edit'. It remains as 'Drag and Drop'. Anything else needs to be done for the additional parameter to take effect?

miroperez

Does it drive you back into Teamsite but you only are in drag and drop mode? Did you copy the component as is then modify?

vpatel

Thanks Miro.

Interwoven/PageElement/PageEdit/InContextEdit.component adds another parameter (isInContextEdit=true) to the end of the query string. I did the same in my component. But when the link is clicked on the runtime environment, the edit mode does not change to 'In Context Edit'. It remains as 'Drag and Drop'. Anything else needs to be done for the additional parameter to take effect?

Let me be clear that ICE would not work in LS. ICE only works on TS (preview end). This is by design and you don't want ICE working in LS. Even if you found an unsupported way to do this -- you probably don't want this.

OOTB Page Edit link works in TS as well as LS. However, you would probably want to enforce some restriction (i.e. only certain users can see that link, or only certain LS environments can have that link, etc.) on Page Edit link based on your needs. That part would have to be customized for your requirements. With that said, even this Page Edit link, behind the scene, will route you back to TS for editing. I believe Miro's earlier post also focuses on this Page Edit link in LS and NOT necessarily ICE in LS.

Do you have a clear understanding of this? Your question makes me think you are expecting ICE in LS runtime.

miroperez

Correct. There is no way to do ICE directly in LS runtime. The code to support it isn't even there. This is only available in TS/Sitepub. You can only redirect to TS/Sitepub which can invoke ICE once you are there.

phenom

Thanks vpatel. My assumption was that ICE was available in LS. But it isn't. Hence, I am trying to implement the Page Edit link within the LS (with some restrictions ofcourse).