Tridion Stack Exchange is a question and answer site for Tridion developers and administrators. It only takes a minute to sign up.
Sign up to join this community
In order to configure Experience Manager, you add a SiteEditURL to the parameters of the "Enable inline editing for Page" TBB. This refers to your content manager server in a specific environment. Obviously, you don't want your production site to be referencing your development system, and this is not something that by default the content porter would be expected to take care of.
What is the best way of managing this?
You don't have to specify the SiteEdit URL as a parameter on the TBB. You can simply have a common TBB push a value into the package with the same name, loaded from wherever you like - a config file, or more practical in scaled out scenarios, a environment specific configuration component.
The Get System Components TBB on Tridion World can be used to do this, just make sure you have a component with XML field name matching the SiteEdit TBB parameter name.
The best thing I've found to do is to wrap this TBB in a Compound TBB and use the latter in all your CTs instead of adding the former directly.
e.g. call this wrapper something like "Enable Inline Editing Config Wrapper". You would then set your SiteEditURL inside the wrapper and the setting would therefore persist across all templates that use the wrapper.
So when it comes to DTAP, you only have to maintain/change the SIteEditURL in one place after content porting.
I like to have configuration files on my server - for a static publishing solution you could store the values in the contentmanager config files, or in a dd4t solution it could be in the extended classpath in a properties file.
