Home > .NET Framework, Ektron, Web Development > Ektron CMS400 7.0 issues with .NET Framework 3.5 SP1

Ektron CMS400 7.0 issues with .NET Framework 3.5 SP1

October 6th, 2008

After upgrading my development machine with Microsoft .NET Framework 3.5 SP1, I noticed a couple things. First, the installer also updated the .NET Framework 2.0 instance to Service Pack 2.

Second, my instance of Ektron CMS400 v.7.0.4.20 (which runs under .NET Framework 2.0) starting having problems. Specifically, I could no longer create library items in the workarea. Attempting to save a library item, for example, a hyperlink would cause the page to postback and the icon bar to disappear:

The postback page after attempting to save the library item

The postback page after attempting to save the library item

There is no error message, but viewing the library item list reveals that the item was not saved.

The culprit was the page /workarea/library.aspx. Viewing the HTML source of this page when attempting to “Add Library”, the form tag’s action attribute was:

library.aspx

… no querystring parameters; so when the page posts back in Ektron, it can’t save the library item and fails.

Viewing the same page on a system without .NET Framework 3.5 SP1 results in an action attribute like this:

 library.aspx?LangType=1033&action=AddLibraryItem&folder=98&type=images

Some background: As it turns out, the .NET Framework 3.5 SP1 installation changes the way the FORM tag’s ACTION attribute is handled. Prior to this upgrade, ASP.NET would ignore whatever you typed for the form’s action attribute in the markup. ASP.NET would instead render the action attribute to match the original page request. Starting with SP1, the action attribute is no longer ignored and will be rendered exactly as input.

Ektron, as it turns out, supplied an action attribute in the library.aspx form tag. Until the release of this Service Pack, it was ignored by ASP.NET.

Two possible solutions:

This may not be an issue in Ektron CMS400 7.5+, but users of v7.0 should be wary, even if they’re not planning on upgrading .NET Framework 3.5 SP1… Windows Update may upgrade you automatically around November of this year.

.NET Framework, Ektron, Web Development , , , ,

  1. Vladimir
    | #1

    Thanks a lot! I have been almost 2 days searching for this Ektron BUG.

  2. Steven Boynes
    | #2

    Thank you! I spent the better part of today with this issue on Ektron 7.5.1.41 in an Windows 2003 SP2 environment. When the server was upgraded from SP1 to SP2 the 3.5 version of the .NET Framework was installed and the 2.0 version becamse “Microsoft .NET Framework 2.0 Service Pack 2″. I had to totally remove the Framework and re-install .NET Framework 2.0 (Non SP2) – and now everything is back in working order.

Comments are closed.