As usual I try to keep up with SDL Tridion product as best as possible. Pretty excited that SDL Tridion 2013 SP1 came out this week!
Just wanted to try it out today installing the basic Content Manager portion and see what has changed.
Here goes!
STEP 1
Choose what feature you want to install. Looks like "Context Expressions" is something new here
STEP 2
Installing the missing prerequisites (nothing changed)
STEP 3
Enter MTSUser Account (nothing changed)
STEP 4
Connect to database. In addition to the normal SQL user, you can actually use Windows Authentication now!
STEP 5
This step is optional but we use SDL WorldServer for our translation services. There's a new selection called SDL BeGlobal which is a new SDL automated translation service that's hosted in the cloud.
STEP 6
Installing SDL Tridion (nothing changed)
STEP 7
Select your license file (nothing changed)
STEP 8
Get ready to install (nothing changed)
STEP 9
Installing......
STEP 10
DONE!!
Upon first access, I am quite impressed! I am immediately greeted with a dynamically spinning "Loading" page.
Here's the home screen of the completely new dashboard in Tridion 2013 SP1
Finally, here's the new content explorer screen.
Overall, I am quite impress with this version of Tridion. Good job R&D team!!
Yesterday I experienced a strange issue where the publication property cannot be accessed due to the following error:
The item tcm:0-167-65568 does not exist
Seems like this group ID was somehow removed or corrupted.
Good thing, there is a solution to purge the application data tied to this publication.
Out of the box, Tridion comes with a tool in the Tridion\bin folder called "PurgeAppData.exe". Using this tool we can purge old app data specific to permission, translation configurations, workflow, etc....
By going into CMD, and doing a PurgeAppData.exe list command, I can see all the app data in the CM.
The one I wanted to purge in this scenario is the tm:Rights app data.
The command would be: PurgeAppData.exe purge:tm:Rights
After purging, I can now access the publication property again =)
Today we had a requirement where the publication path need to include a "-" for all locales. For example, we will need the publication path of an English site to have "en-US" and not "en_US"
However, by default, Tridion CMS does not allow for this to work. When trying to add a "-" you will get the following error:
Here's the work around:
Open \Tridion\bin\cm_xml_usr.xsd
Modify the <xsd:simpleType name="FilePath"> element to include "\-" in the XSD Pattern.
You will now see the following:
Restart Tridion COM+
Now you should be able to add a "-" to the Publication Path!
In order to make modification to the Tridion MMC Snap-in such as the database settings, your user account will need access to the TridionRsaKeyContainer.
Ever get this annoying "Access is denied" error when you tried to add yourself to the TridionRsaKeyContainer? I have plenty of times.....
I always thought that the original Administrator account who did the Tridion installation can grant this access. But what if the original user account that was used was deleted or the employee left the company? Then you're screwed........ ok, that's not true!
Here's a way around it with the use of Microsoft PSTools
Playing around with Windows PowerShell today. As usual, the first thing that people learn is the infamous "Hello World" program. So I tried scripting an array of string in PS (plus color!)
Today marks the first day of me learning about the Tridion Core Service! First let's step through how to connect (remotely from the server as a client)
Open Visual Studio and create a new Windows Console project
Add Tridion.ContentManager.CoreService.Client.dll as a reference in the solution
Add Systems.ServiceModel and System.Runtime.Serialization as a reference in the solution
Make sure the project is running .NET Framework 4.0
Create an app.config file with the content from Tridion.ContentManager.CoreService.Client.config and update the netTcp_2011 address with the appropriate server IP
<?xml version="1.0"?>
<configuration>
<system.serviceModel>
<!-- Default/example WCF settings for Core Service. These settings should be copied into the host application's configuration file. -->
<bindings>
<!-- Default Core Service binding settings are provided here. These can be used as a starting point for further customizations. -->
using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using Tridion.ContentManager.CoreService.Client;
namespace CoreService
{
class Program
{
static void Main(string[] args)
{
// Connecting to Core Service
var client = new SessionAwareCoreServiceClient("netTcp_2011");
client.ChannelFactory.Credentials.Windows.ClientCredential = new System.Net.NetworkCredential("administrator", "tridion");
Console.WriteLine("Connected to CoreService with user " + client.GetCurrentUser().Title);
Console.Read();
}
}
}
