11

As explained on the Tridion Practice project, you can easily add your own markup for SiteEdit (or Experience Manager for that matter). Basically all that is needed for SiteEdit to work is the correct markup around your Component Presentations and the fields you want inline editable. Add to that the Page markup and bootstrap script and your Page will be ...


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

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

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 ...


8

This scenario is covered in Bart's Having fun with Experience Manager, Page Regions and Widgets blog post on the Tridion Developer site. (See the section starting "The last subject I want to address is that at some point you will come to an item which has no visible element showing on the website") He suggests using CSS and JavaScript to expose the hidden ...


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

The comments all need to be inside of an encapsulating HTML element. Common use is a DIV element for Component Presentations and SPAN elements for fields. Example markup taken from the UI Update for 2011 documentation (requires login): <div> <!-- Start Component Presentation: { "ComponentID" : "tcm:2-635", "ComponentTemplateID" : "tcm:2-599-...


6

Find this section in your SiteEdit.config file (typically in C:\Program Files (x86)\Tridion\SiteEdit 2009\SiteEdit\Application\Configuration): <!-- ** Component Toolbar ** If @Visible is set to "false" the toolbar will not be available. Under <ButtonsVisibility> you can specify the availability of each button. --> <ComponentToolbar Visible="...


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 ...


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 ...


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" ...


5

In the Tridion Practice project on Google code there is a custom function source defined to aid in marking up your HTML for use with Experience Manager -> https://code.google.com/p/tridion-practice/wiki/TridionUI2012FunctionsForUseInHtmlTemplates Now this is a custom function source and thus meant to be used as Template Callable functions for inside a DWT ...


5

I am not sure if it is the cause of your issue, but having the BODY tag outside of the HTML tag seems very wrong. First step of getting SiteEdit to work is normally getting valid xhtml output. Also you will never see SiteEdit on port 88 (the direct URL of your staging site). If the SiteEdit proxy is installed on port 91, that is the URL you should access. ...


5

Experience Manager runs on top of the CME (Content Manager Explorer), so you can scale it out by scaling out the CME. Add more CME servers with XPM installed, make sure your XPM initialization javascript points to the load-balancer URL, and you should be good to go. I would recommend making a baseline measurement of how many concurrent users you can cope ...


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.


4

is @item a field in your component? Also, is this a TBB that's being executed in a CT for a component? Typically, if you're trying to access fields in a component, you want to tell that to razor by using @Fields @Fields.link You can also be more explicit by designating the the object: @Component.Fields.link Therefore, I'd think that this is what you ...


4

Check if the SiteEdit Application Pool is set to run as "Network Service" and that "Network Service" is configured as a valid impersonator. At the very least, the application pools for Tridion and for SiteEdit should run under the same user account. If you're using LDAP authentication then the whole thing gets a bit more complicated, but it's the same ...


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

"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

Click on “border view” to see if the borders appear. It could be that the elements have a higher Z index than the borders and floating over it or somehow the border is not wrapping correctly. Check to see if a faint grey border appears anywhere on the screen. That would mean its a shared item and you can not edit it without either localizing or clicking ...


3

The red border is indicating that SiteEdit thinks the Component Presentation is not available on that Page. This basically means there is a mismatch between the ID of the Page and the IDs of the Component and Component Templates as specified in your SiteEdit markup on the page.


3

Can you tell us what you have already tried please? This scenario sounds very similar to this: Make component link fields inline editable In particular see the reference to 'Making subfields of embedded multivalue fields editable' section of the online documentation (login required): http://sdllivecontent.sdl.com/LiveContent/content/en-US/...


3

It's a bit unclear what the issue is here. But I can say that you don't need or want the SiteEdit.js file to be there physically. On the PS side, you only want SiteEdit 2009 SP3. It is backwards compatible for the markup, and it will ignore the old request to the SiteEdit.js file as long as you keep that "UrlToHide" setting as the default. Hopefully that's ...


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

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

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

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 ...


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