I ran across an interesting API library deep in the Ektron API framework that allows you to pull the actual localization tag (e.g. en-US, en-GB, etc.) for the current language type id of the site (e.g. 1033, 2058, etc.). Previous to this, we had to create our own associative, key/value pair XML file that stored the relationships. Since I could only find a single reference to this library on the Ektron site, I hoping this information proves useful to others. Enjoy.

// get and instance of the current site API object
Ektron.Cms.SiteAPI sAPI = new Ektron.Cms.SiteAPI();
// retrieve the language date for the current site API instance
Ektron.Cms.LanguageData ld = sAPI.GetLanguageById(ContentBlock.LanguageID);
// assign the localization tag
string langTag = Ld.XmlLang;

While prototyping a custom DMS asset handler today I managed to locate actual instructions on configuring your own QuickLink handlers for specific assets. However confusing it may be that these instructions were found in the “Users Manual”, I am just glad I was able to locate it fairly quickly.

Updating Default Template for Multiple Quicklinks

WARNING! This procedure is only necessary if Link Management is set to false in your web.config file. If if Link Management is set to true, Ektron CMS400.NET automatically updates the template within the quicklink when content is moved. See your system administrator for help with the web.config file.

NOTE This action can only be performed on quicklinks. When content is moved in Ektron CMS400.NET, its quicklink does not get changed. After it is moved, you need to update the default template called in the content’s quicklink. To update the default template for one or more quicklinks, follow these steps.

1. In the library, access the quicklinks folder containing quicklinks you want to update.
2. Click the Update Quicklinks button.
3. The Update URL Link Template Quicklinks screen is displayed.
4. Check the quicklinks you want to update. NOTE Check the box in the table header to select or deselect all.
5. In the To: text field, enter the name of the template you want to apply to the selected quicklinks. Last User to Edit Last user that made changes to the quicklink or form. Last Edit Date The date the quicklink or form was last edited. Date Created The date and time the quicklink or form was originally added to the Ektron CMS400.NET library. Field Description Library Folder Ektron CMS400.NET User Manual, Version 7.5 155
6. Click the Update Quicklinks button to update the changes. A confirmation message is displayed.
7. Click OK to continue. The selected quicklinks are updated to use the specified template.

These instructions can also be found in the Ektron User’s Manual

Note to self: do not use a virtual directory for the AssetManagement DMS folder when configuring Ektron web sites.

I learned this the hard way (again) today while trying to figure out why my DMS assets were not uploading properly. After a couple of hours (and a night of sleep) and setting up a completely new instance of a bare bones Ektron CMS that functioned properly, it finally dawned on me that perhaps one of the various virtual directories were causing the issues. Apparently, the AssetManagement folder cannot be virtual or it throws off their file upload processor (at least for v7.01).

I believe they have fixed this with the latest version (I hope.)

Let this be yet another learning lesson and hopefully assistance to anyone else running into this similar issue.

I have been architecting, designing, and programming Ektron CMS400.NET web applications for over a year now. Though not an expert, I feel I am to the point I can actually add value to other programmers/architects who may be running into similar issues as I have. This is my first snippet of advice.

When developing custom action pages for the built in Ektron forms, remember to set the Page directives as specified in the Administrator Manual.

page 312

If your site is using URL Aliasing, the action page’s header must include the following:
EnableEventValidation="false" EnableViewStateMac="false"


Apparently when you set the EnableViewStateMac attribute to true, the encoded and encrypted view state is not checked to verify that it has not been tampered with on the client. Otherwise .NET will not persist the Viewstate from the original .NET form to the action page specified in the Ektron form.

Though disabling the EnableEventValidation attribute may be necessary, I don’t see any real reason since the page that is handling the postback shouldn’t have any controls on it in the first place. However, in the event it does, the page’s validation must be turned off else the postback handler will not validate the form post.