10

Open the item and check the "Locked by" section on the Info tab. Then contact that person. If it's a system account, the item is likely locked by workflow and needs to go through the workflow process to unlock. If it's locked by a person who no longer works there, you'll need a Tridion Administrator to unlock the item for you.


10

The Session Preview database has the same structure (tables, etc) as the 'normal' broker database (Content Data store), but it should be a separate database. So your staging website uses 2 databases: one 'normal' broker database and one Session Preview database. See the docs for more information (login required): http://sdllivecontent.sdl.com/LiveContent/...


10

If you mean to add a thumbnail instead of the little icon which is displayed in the Component Template dropdown on the Insert Component Presentation dialog in a Page (see image below), then technically that is possible, but there are a few things I should mention. It is possible to change icons in a list using a UI extension/data extender, see ...


6

You can do it by adding configuration in your editor configuration file. You should add the configuration here: <extensions> <ext:editorextensions> <ext:editorextension target="SiteEdit"> <ext:editurls /> <ext:listdefinitions /> <ext:taskbars /> <ext:commands /> <ext:...


6

Within the SiteEdit editor, there's no such control as a field builder, but rather a set of Component Presentations and Fields, if you wan to set a value in an existing SiteEdit field (I guess within a Component Presentation where such field is editable...), first you need to make a selection, i.e. click in the field. Here are the available controls in the ...


6

The DD4T object cache by default checks for the last publish date of the underlying Tridion components and pages. The problem with Session Preview in Experience Manager is that it does not change the last publish date. This can cause your web application to cache the temporary content created during an XPM session, and use that even after the XPM session has ...


5

This is now resolved . The "Path" attribute value at the node "Host" node under /URLMappings/StaticMappings/Publications in the cd_dynamic_conf.xml was incorrect. Once that was set to the correct one the CSS rendered correctly.


5

It sounds like you're just "half" configured to use JMS as your cache invalidation provider (judging by javax.jms.JMSException). You should NOT use cache for the session preview webservice, as all this data is temporary and session specific anyway, so I'd start by changing your cd_storage_conf.xml to disable cache, then restart and try again.


5

SiteEdit 2012 (or actually the official name for it is: User interface update for SDL Tridion 2011 SP1, sometimes also mentioned as UI 2012) is the predecessor of Experience Manager (XPM in SDL Tridion 2013) and it basically is an extension on the CME. So when extending it, you don't need its configuration file, but you specify inside your Editor extension ...


5

This has everything to do with the different levels of caching built into the DD4T framework. The default caching strategy works as follows: -Page/DCP is requested and thus cached -The DD4T framework polls all the items in cache with a regular interval. This interval is configurable with this setting: <add key="CacheSettings_CallBackInterval" ...


4

As you've already discovered, the Experience Manager comment tags need to be wrapped with some HTML element per field in order that the UI can display them correctly and allow editing.


4

We had the wrong Publication ID in the SiteEdit_Config. Now its been corrected and problem solved.


3

Experience Manager is integrated with SDL Tridion 2013 so you won't need to do a separate installation. Also, from configuration perspective, XPM is much simpler as compared to Site Edit. Regarding site edit span tags, templates etc. they need to be changed. You can refer below link (login required) to see step by step process for setting up XPM: Experience ...


3

There can certainly be issues with XPM and other JS libs, in particular those that rely on heavy Ajax. The project that John is describing was actually full of JS issues (though most we're not XPM related). One of the issues for instance, when jQuery does an Ajax HTML load call, it strips off all HTML comments in the source page. Guess what?... It kills ...


3

We've done a lot of work with JQuery (and DOM manipulation) and a whole host of other JS libraries, and not experienced any technical issues. We've added XPM to an existing site in the past where page content was ajaxed into the main content window (the site was a 'monolith' style site and driven by a single page). In that instance we needed to inject a ...


3

I see in your screenshot you have a 403 error (http://en.wikipedia.org/wiki/HTTP_403). This is a security access error. It could be due to IIS security settings on the SiteEdit Proxy. It may also be security settings on your actual website. It's hard to tell just from the info you've provided, but take a look at the Event Viewer log in the CM, also IIS ...


3

"New Page" is only enabled once you configure "Page Types". Until then, Experience Manager has no idea what you mean with a "new page". Check the documentation topic for "Enabling the creation of new pages" and google "Alvin Reyes page types" for good tips and advice.


3

XPM (aka. SiteEdit) works by indexing the page for XPM markup to build a list of which Component Presentations are on the page. This indexing is done right after the HTML is loaded (similar to the onload event on the body). So the problem you are experiencing seems to be related to the additional information which you gave in your first comment. You load ...


3

Unfortunately, there are quite a few moving parts within Experience Manager (the new name for SiteEdit - The inline editor for SDL Tridion). Problems like this are often something within the configuration, infrastructure or templating. However, before you begin to embark on an indepth investigation, I'd recommend that you check some of the basics. For ...


3

While browsing through SDL Live documentation, just came across an article(login required) where the step by step solution given to change the icons of CTs & PTs in Experience Manager(XPM). Please check if it is useful!


2

I have added my view for SiteEdit as shown below and its working fine. Thanks to everyone for helping me. <ext:apply> <ext:view name="EditorView"> <ext:control id="MainToolbar"/> </ext:view> </ext:apply>


2

I believe these are 2 different issues. The reason why Update Preview button is always flashing is likely linked to the fact that something is missing when updating. Do you actually see updates after clicking on the button? You may also verify the steps Tridion takes when you click on that button. I outlined the actions in this answer on Stack Overflow. I ...


2

I haven't seen exactly this one, but something similar when my Session Preview Content Delivery Endpoint URL was misconfigured. Reading the error description I would guess your endpoint URL (the Session Preview oData service) is up and running, but it might have some other issues. I would checkout if you can manually browse that oData service and if that ...


2

User Interface update for SDL Tridion 2011 SP1 (also known as UI 2012) is working on top of your website, so whether you are using an MVC web application, ASP.NET webforms or plain old static HTML pages doesn't really matter. All you need to make sure is that the correct markup is written out for each Page, Component Presentation and Field you want inline ...


2

It looks to me as though your font is getting used, but is displaying the wrong output. The obvious suspect here is an encoding issue. Are you using UTF8 everywhere? I would suggest checking the configuration of the proxy site, and also the response headers to ensure they are correct. (Presumably in this case, "correct" means "the same as on the live site".)


2

So looking at your screenshot I'm assuming the problem you are referring to is that the border in XPM does not match the size of your image right? (in that case, it would be beneficial that you update your question and make the actual problem a bit more clear) The border as shown in XPM is generated based on the XPM markup and the HTML elements around that....


2

XPm is entirely new experience and provide lots of features, i will suggest to search blogs (this link is for ui-2012) but features are similar + XPM 13 has few new features like 'Switch Device’ Your old site-edit tags will not work, You have to include new OutOfTheBox TemplateBuildingBlocks in your Component template and in page template to generate new ...


2

If it is SiteEdit 2009 SP3, then apply following Hot Fix: SE_2.3.0.76375 - Cumulative Hotfix and try again. If it is SiteEdir 2009 SP2, then apply following Hot Fix: SE_2.2.0.83094 - Cumulative hotfix and try again. Hopefully it should resolve the issue.


2

Probably the Component Template that is linked to the schema that your component is based on is not enabled for Inline Editing. Check the checkbox and try again


2

Following are the list of Add-on products, compatible version and the hotfix requirements compatible with Tridion 2011 SP1. Refer HERE from upgrade documentation which details the add-ons that must be un-installed (WebForms) and upgraded before upgrading to Tridion 2011 SP1 HR1. If you proceed with upgrading to 2011 SP1 HR1 without upgrading or un-...


Only top voted, non community-wiki answers of a minimum length are eligible