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.


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

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

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


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


8

If you are using Razor Mediator to build your layout you can use its built-in function IsSiteEditEnabled. The Razor Mediator v1.3.3 documentation has the following example. @if (IsSiteEditEnabled) { <div>Component Title: @Component.Title</div> }


8

It is not really supported to modify the CSS files which come out of the box. But I think it would be possible to override the classes you want to modify by adding a stylesheet which is meant to skin the user interface. Details of this you will find in the documentation topic Skinning the Content Manager Explorer (requires login). I'm not really sure if ...


8

I'll try to answer some of the questions I saw: Since we can set up additional claims, then this could include any other data an organization has on a given visitor, right? Anyone can add any claim to the ADF and it can have pretty much any value. So yeah, go nuts. The docs mention Footprints map to ADF keys. How are keys related to claims? The "...


8

My guess would be that when you are creating a new page based on page type in XPM, XPM is actually cloning/copy and paste the type and then updating it with the appropriate values. Recommend subscribing to CopyEventArgs to confirm. Update Creating a new page in XPM using a Page Type should fire CopyEventArgs, however, copy operation is done on system, and ...


8

It probably is because of html validation in your browser. <span> cannot contain block elements, like <div> or <p>, and changing the element used by Experience Manager in the "Enable Inline Editing" Template Building Block should solve this (you can use a div for instance).


8

There's Angular, and then there's Angular. If you're going the full SPA route, then you definitely will want to look into leveraging the Content Delivery WebService (or a custom variation of this if you're inclined to maintaining large code bases yourself) and use a library like JayData to provide you the data access layer. Write a couple of simple ...


8

If you are sure that the syntax in the config files is correct, then this is most likely a browser cache issue. Actually, this was exactly the issue as per my question above. Once the browser history and data was cleared, the new custom Footprint was loaded in the GUI. As basic as this issue sounds, this did take some additional time to troubleshoot. ...


8

OK - Looks like for XPM or style="SiteEdit2012" you can just go with an empty SiteEdit_config.xml file: <?xml version="1.0" encoding="utf-8" ?> <siteEdit enabled="true" style="SiteEdit2012" tridionHostUrl="http://xxx.xxx.xxx.xxx"> <contextPublications/> </siteEdit> This enabled XPM without having to implement a <...


8

So to me this looks like it's supposed to be a JSON object: Start Region: { title: "MainContent", allowedComponentTypes: [ { schema: "tcm:6-195-8" template: "tcm:8-288-32" } ], maxOccurs: 10 } Except for one thing -- you missed a comma between the schema and template. Will fixing that make it work? Really just pulling this out of ...


8

The problem is caused by the closing tag at the start of the Razor template. Removing this tag fixed the issue. It makes sense that this is breaks XPM as it either terminates the component area early or prevents the XPM editor from properly parsing the entire DOM for the component presentation.


8

Finally I have resolved my issue, the problem was a configuration in the Publication Targets. I created 2 similar Publication Targets (Previsualization and PrevisST), both had the same webservice_preview url,and both use the same URLs to access but only PrevisST had filled Targeting layer. When I tried to modify my page from XPM, the default target selected ...


8

Have you referenced the assembly (in the GAC) within your Tridion.ContentManager.config file? For example: <razor.mediator cacheTime="60" extractBinaries="true" adminUser="DOMAIN\AdminUser"> <namespaces> <!-- ... --> </namespaces> <assemblies> <add assembly="RazorSample.Test, Version=1.0.0.0, Culture=...


8

There are two parts to this answer. The first was pointed out by Jonathan Williams, I was missing the assembly reference in the razor.mediator configuration <razor.mediator cacheTime="60" extractBinaries="true" adminUser="DOMAIN\AdminUser"> <namespaces> <!-- ... --> </namespaces> <assemblies> <add ...


8

XPM itself does not require any Content Delivery DLLs, it works based on the bootstrap Javascript which injects HTML on your staging site. The content is edited directly in the CM through the XPM editor on the CM. Only for Session Preview you will need to enable the Ambient Data Framework. And if you publish pages (aspx files) to disk in a web application ...


8

There's a frame that's used to clear cookies set by Experience Manager. se_blank.html is set as the source of that frame. If it returns a 404, everything should still work, but it's important that the response comes from the correct domain so that Experience Manager has access to the right cookies. Credit should go to Peter Kjaer for the explanation on an ...


8

For starters on Web 8, the XPM button is on the top right, and the CME URL in your pages is coming from a configuration file, which is generated when you publish the Publish Settings Page in the _System Structure Group. When you are using Web 8 Topology Manager (the default setup), this URL will be read from what is in your Topology Manager under Content ...


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