SmartTarget and Profiling and Personalization are not the same although at a very very basic level it may appear you can force them to do the same thing.
Profiling and personalization will allow you do display specific Component Presentations (attached to the page) to be displayed on the page if the profile logic is met.
SmartTarget integrates with the ...
Via core service you can retrieve PublishTransactionData object, which contains all info about transaction itself:
PublishTransactionData transaction = (PublishTransactionData)Client.Read(transactionID, new ReadOptions());
PublishTransactionState transactionState = transaction.State;
DateTime transactionStateChange = transaction.StateChangeDateTime;
To avoid overloading the CM server with heavy import/export jobs, there is a configurable cap on the number of import/export processes that can run concurrently.
The default configuration allows only one concurrent process, but this can be changed in Tridion.ContentManager.config
Couldn't find any documentation, but this is the setting you want ...
The LoadFlags differs a lot than say the ListBaseColumns enumeration, in that its actually a flag based property and not just a standard enum. While ListBaseColumns allows you to choose only ONE of the options, the LoadFlags lets you add mix and match by choosing one or many of the options.
When you create a new ReadOptions(), the LoadFlags property is set ...
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() ...
No, it is not OK - unless they use the exact same configuration files, including storage locations.
I've done this before by mistake, and only noticed what happened when I saw XPM tags in the live website. Basically, whichever deployer starts first will load the configuration into memory, and this stays on.
If you have different configurations - which you ...
SDL documentation at this link states:
A text value that is unique across the BluePrint and that can be used to associate an external resource to the Keyword, for example a
So I guess this answers your question. :) Main idea behind keywords is to classify content across publications with same ID. Therefore, changing its key is not ...
When you get errors like this, it's probable that the dd4t version you are trying to install is built against a different version of the contentdelivery dll.
You can either rebuild the dd4t solution with the tridion dlls you are using (download the source, set the references to your contentdelivery dlls, and build, or you can add the following in your web....
The reason that you get the namespace is because DWT outputs XHTML by default.
I've usually just done the cleanup using a custom "find and replace" TBB as you've mentioned in your question. However, I believe Default Finish Actions has a TBB called Cleanup Template which cleans out the namespaces. So try this first.
Unless you're trying to implement really granular permissions (more on that in a minute) it makes more sense to handle this on the check-out event instead. The rudimentary issue that I see - and this also applies to implementing granular permissions (e.g., treating check-in and check-out as two separate permissions) - is that by the time the check-in event ...
TCM URIs are not guaranteed to be the same across systems (quite the opposite, in fact). They are basically assigned in the order you create items. So sometimes, items might have the same URIs because they are created by the system at installation time -- but you cannot rely on it.
Anyway, what you want to do is ask the system for the Schema ID. For that, ...
I sense that what you're trying to do is replace some invalid characters while publishing. You would typically do this on the Package.Output variable, not on the Component itself. Output is the text that gets published as part of the Component Presentation.
You typically don't want to modify the Component while publishing it. Before is fine, after is fine, ...
By default SDL Tridion 2013 SP1 is not setup to be fully HTML 5 compliant (this is also still the case for Web 8 for that matter). You can extend the RTF field to allow HTML 5 tags, and this can be specified in the file TcmXhtml.Config at the path [Tridion]\web\WebUI\Core\Controls\FormatArea\TcmXhtml\
Depending on how you exactly want it to behave you can ...
"Waiting for publish" means that the item was successfully added to the queue but no publisher service picked it up yet. Why can this happen?
Your publisher has other tasks that are keeping it busy right now. Change the publishing queue filters to see actions for all users (defaults to showing only YOUR actions)
Your publisher service stopped running (more ...
Another way of doing this would be to write a number of mvc html helpers that would use the smarttarget query api to fetch promotions etcetera.
The flow would be something like
get parameters from the html helper (promo name, nr of items, region name,...)
construct a smarttarget query
send a query and receive xml with results. I believe the results are tcm ...
Found it, not sure if this will help anyone else as I am sure that it probably isn't an actual problem for more experienced tridion users. But the id of the person who kicked off workflow was found using
For anyone else stuck with this, here's the solution.
Oracle 12c introduces multitenancy. With this architecture the Tridion Content Delivery database must be set up in the pluggable database rather than the container database that is the default when you first connect via sqlplus.
To switch to the pluggable database you will need to log in "sys as sysdba" ...
It appears that having a keyword field in the metadata of a component causes this problem after HR1.
Hotfix CME_2013.1.1.88649 available https://www.sdltridionworld.com/downloads/hotfixes/SDL_Tridion_2013_SP1_HR1/index.aspx fixes the issue.
yes this can indeed be the case. We had same issue and contacted SDL support for fix. Why this indeed is the case, we have no answer. I suggest you contact them just in case to verify.
Thank you for contacting SDL Customer Support.
From the error message, it seems that there is already a reference to
the record on the broker ...
The problem with multiple doctype declarations can be caused by some standard mvc view behaviour.
In your mvc project, you can define a _viewstart.cshtml file. In here, you specify the default mvc "master page" (called "layout page") to use.
This layout page will be outputted around all of your views that don't specifiy a custom layout.
you can specify a ...
Sounds like you're using the Tridion 2013 providers which come with that template.
You should run the following commands from the Package Manager Console:
Then in the DD4TNinjectModule class, change the using statement to match the provider. Lines 11 and 12.
// TODO: Change this ...
You need to ensure that you have first selected the correct frame in the console. It defaults to 'top frame' but you'll want to choose e.g. Dashboard.aspx. You'll know it's the right one when it helps you with code completion :)
The sdl.com corporate website has an integration with Marketo. Here are some details from a functional point of view:
Marketo forms are presented on the Tridion webpage in an iframe. The form is created in Marketo, which results in a Marketo form url. With a manual action the Marketo form url is added to a Tridion form component. This component ...
Have you installed Hotfix TT CM_2013.1.0.88313 - Cumulative hotfix? This fixes an issues when you have more than one person in the TRUSTEES table.
Remove the <Tridion Root>\bin\.ez20ck file to be sure and restart everything
Are you sure it's not your cd_licenses.xml which has expired also?
I would start by asking what the benefit is of this technology change? Is it just that the client has a preference for these technologies? In which case I would use the same response as if a client asked me if they could create their Tridion driven website using PHP: You could, but is it worth the effort? And more importantly have you carefully considered ...
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 ...
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.
We had the same issue. I have fixed it by modifying the TCM54 config file. It is a one time change and it works very well. I did this in Dev environments and life is much better for all Developers post this change :) I did not do in other environments since it impacts all users because I have set max age to the bare minimum value and then schemas are not ...
You cannot access the request object directly, as cartridges are web-application-agnostic (i.e. the .NET request object is very different from the JSP one). Instead, you can access the headers and other parameters from the ClaimStore passed into your methods.
The ADF automatically extracts the variables from the request and adds them as claims. For a list ...