We’re rewarding the question askers & reputations are being recalculated! Read more.
21

If you mean hidding the tab "Preview" in the ribbontoolbar of the experience manager you have to add that code in the "ext:ribbontoolbars" section of the configuration file, like this: <ext:ribbontoolbars> <ext:remove> <ext:extension id="PreviewPage"> <ext:apply> ...


20

Session preview bypasses the standard publishing mechanism. I found it the hard way too, that after "previewing" content my characters were wrong. Easily fixed if you know what to search for. The problem is that you need to tell the Java process on the delivery side to use UTF-8 encoding, which is usually handled nicely by the Deployer... but with Session ...


20

The log out is a little tucked away, you have to return to the 'dashboard' tab/view and in the left hand navigation the bottom link 'Exit', clicking that will close XPM and return you back to the website on the page you were editing.


16

I am going to answer my own question, as I got a lot of additional information from other sources and think its helpful to summarize it here. It is not at all possible to use Session Preview without the Ambient Data Framework as key to this working is the ability for your web application to switch between getting content/data from the normal staging storage ...


16

If you go to the SDL Tridion dashboard and then choose the Settings, under Inline Editing you will find the Session Preview Settings. Here you can disable the Session preview, which will disable the Update preview button in the Experience Manager view.


15

To have Footprint sets showing up in the Footprint Gallery in the Preview, you need to have your Staging website listed under "Website URLs" in the "Session Preview" tab of your Publication Target. You don't need to fill in an odata end point or any other field. Sometimes I make the mistake of specifying the website URL but then browsing my page through '...


14

You don't need to install SiteEdit 2009 to instal the new User Interface in Tridion 2011. The only prerequisite is to have installed the Hotfix Rollup HR1


14

Basically you need to add the XPM/SiteEdit markup yourself around that image, as you are using additional HTML to display your image (your img element). So you need something like: <div> <!-- Start Component Field: {"XPath" : "tcm:Content/custom:Content/custom:image[1]"} --> <img src="@@Component.Fields.image@@" tridion:type="...


13

Experience Manager is the product formerly known as the SDL Tridion User Interface (UI) update, formerly known as SiteEdit. You can find information on Tridon World for UI Update (https://www.sdltridionworld.com/downloads/documentation/UIU4SDLT2011SP1/index.aspx) if you have access, as well on SDL Live Content (http://sdllivecontent.sdl.com/LiveContent/...


13

Credit on this solution goes to Eric Huiza. Here's an Extension Method for the Publication Target that reads the Application Data to check if the target is SiteEditEnabled: public static bool IsSiteEditEnabled(this PublicationTarget target) { try { if (target == null) return true; ApplicationData appData = target....


12

If Session Preview is turned off from the Dashboard, then the Update Preview button becomes disabled. As a user, this is inline with my expectation.


12

Some tags are written out automatically, for example if you use the RenderComponentPresentation() method it will output the markup for a component presentation, and if you use RenderComponentField() it will output the markup for a field. New in 2013 SP1 are the FieldStartMarker(), FieldValueStartMarker(), FieldEndMarker() and FieldValueEndMarker() ...


12

You need two DB Broker DB - It is configured in httpUpload and your Delivery website Session Preview DB - it will be used by Session preview service and this service is consumed by XPM. No separate db for XPM. This db will also configured in storage config of your website. HttpUpload and Odata.svc would be separate websites


11

Difficult question. In principle, in 2011 SP1 HR1: NO. In certain cases it will work but what you need to do is to forward the XPM token from the staging site to the CD WebService and to have the Session preview claim processor activated on it. Hope this helps.


11

I have seen a similar issue to this in an IIS based .NET application - to work around it I wrote an HTTPModule which detected directory requests and re-wrote them to ../path/index.aspx This module is only installed on the staging server for obvious reasons. You may be able to write similar functionality as a Java Filter to work around the problem, ...


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


11

You should upgrade your existing Default Templates by opening Template Builder, choosing Tools | Create Default Building Blocks from the menu, and selecting the parent folder for the "Default Templates" folder in the relevant parent Publication. For instance, if your default templates are in "Building Blocks\Templates\Default Templates", you need to choose "...


11

If there is no XPM markup at all, it is very likely that the example website is thinking that you are not on a Staging website. When publishing the Settings, there is a flag published, so the Website can distinguish when it is running on staging and generate the XPM markup. To generate this flag the TBB's rely on the publication target name. This means that ...


10

The error might be a red herring in this case, as the stack trace is from the UGC Data Extender. You may have a problem with UGC - perhaps missing configuration or an incomplete installation. Check the UGC log or the Event Viewer for more details on the issue.


10

Make sure the Filter (for java) or the HttpModule (for .net) are correctly configured in your web.xml/web.config These will be the ones that makes the Ambient Data Context available for your websites .Net (web.config): <add name="Tridion.ContentDelivery.AmbientData.HttpModule" type="Tridion.ContentDelivery.AmbientData.HttpModule" /> Java (web.xml): ...


10

SDL Tridion World (https://www.sdltridionworld.com) contains all the documentation for installing any SDL Tridion product including UI 2011. You will need a login to access this part of the website. If you don't already have access, then support should be able to set you up with a login. This is the link to the UI 2011 documentation which contains all the ...


9

JNDI cannot currently be used for "storage wrappers" as you state, so the solution is not very easy - unless all your environments are using the same wrapper database - which is not such a crazy thing, after all this database only has temporary data in it. The way I'm dealing with it right now is with post-deployment scripts that modify ##variables## in the ...


9

I was troubleshooting an Experience Manager installation today, and had the same symptoms, but no obvious other error messages. In the end the issue was not having correct Host element(s) set up in the cd_dynamic_conf.xml of the staging website, corresponding to the staging website domain and port. Check you have something like: <Publication Id="3"> ...


9

Session Preview works off the Session Preview Broker DB and inherently through the Session Preview Odata service. Despite your "code" components being regular CPs on a regular statically published page, when in Session Preview mode pages and CPs go to the session preview broker db and get served up via odata. So you should check the mime type settings of ...


9

There's a hotfix for that... (this is fixed in SP1). If you're on SQL Server (I think with Oracle it is exactly the same fix), run this on the preview database: IGNORE THIS, SEE UPDATE 2 UPDATE Now that I think of it... run this on all your Content Delivery Databases... UPDATE 2 Fixed with cumulative hotfix CD_2013.0.0.86156


9

XPM is intended to work with any tag, yes. The caveat is that it should be supported by the browser as a container element (and be valid in the context it is in). So basically, if you test it in the various browsers and the borders show up in the right place and you don't get any weird JavaScript errors, you're good to go.


9

You probably need to look through InlineFormatArea.js and the Format Area Action commands (executeFAAction) You'll see that when in XM the necessary functions are called cross domain using the $xdm object. You will see functions such as this.applyBold this.applyItalic this.applyHTML the former two call off to applyTagFeature whilst the the latter, you're ...


9

This error occurs when the message size limits in the CD web service configuration are too strict. During XPMs fast track publishing process (part of the session preview mechanism) the CM cannot publish the binaries (i.e. images) on your site. Possibly one of the images on the page is too large to be published to the CD Web Service. Check the web.config of ...


9

When rendering your SiteEdit ComponentPresentation command, you need to use the json attribute "IsRepositoryPublished" : true. Add this command above the div that will contain your DCP. For the page command use tcm:0-0-0. Finally, at the bottom of the page add the reference to the XPM Bootstrap.js URL.


9

It might be one the components on the page type that is causing the issue. Are there any predefined components defined on your page type? If you open up the page type in CME and check the component presentations. Each component presentation has its own page type settings. Here you can define a folder for components that you clone (each time you create a new ...


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