Version 8.6

Released: June 28, 2012

Important upgrade information (Read this first)

Important Upgrade Information (Read This First)

  • The Ektron 8.6 search feature set was enhanced to address a number of concerns related to 8.5 deployment limitations, performance, and index integrity.
    • Communication was streamlined to minimize possible points of failure.
    • Query services were isolated to avoid SharePoint performance constraints and ease deployment.
    • Indexing processes were updated to consolidate the property creation process and ensure index field uniqueness.

    For these reasons, Ektron 8.6 requires search components to be upgraded to 8.6. Version 8.5 search components are not compatible with CMS sites running version 8.6. CMS sites running version 8.5 cannot share a Search Server instance with CMS sites running version 8.6.

  • Security trimming of search results is not supported in the FAST Search for SharePoint 2010 search provider.
  • Integrated search mappings are not supported in the templated search controls (UI) with the FAST Search for SharePoint 2010 search provider. You can achieve this functionality via the search API instead.
  • The refinement criteria and response data structures in the 8.5 preview release of the FAST Search for SharePoint 2010 search provider are not compatible with those available in version 8.6. If you are upgrading from the FAST preview release to version 8.6, any code referencing the old data structures will result in an error. You must update this code to use the new classes.
  • The Ektron Search Server Service is not installed on the Ektron server as part of the base installation. It is only installed on a search server when the EktronSearchConfiguration.exe file (installer for Ektron search components) is run on the server.
New Features

New Features

Digital Experience Hub (DxH) (Licensed separately)

Digital Experience Hub (DxH) (Licensed separately)

Ektron Reference > Using the Digital Experience Hub

You can connect to external systems, share data and content with third-party applications, and automate business processes throughout the enterprise. When DxH is installed and connected to Ektron, an administrator can add connections to these third-party applications.

  • SharePoint®—pulls SharePoint content into Workarea, where it can be managed like other content types.
  • Salesforce®, Marketo® Lead Management, Microsoft Dynamics® CRM—maps HTML forms to content in the external application. As a result, site visitors can submit forms, questionnaires, surveys that become completed forms in the external application.
  • You can securely deploy DxH in Azure (IaaS) while your CMS site is hosted in a Cloud service using the Azure PaaS environment. See Configuring DxH in the Azure Cloud in the Setting Up the Ektron Cloud Manager chapter of the Ektron Reference.
Ektron Cloud Manager (Licensed separately)

Ektron Cloud Manager (Licensed separately)

Ektron Reference > Setting up Ektron the Ektron Cloud Manager

The Ektron Cloud Manager has the following benefits:

  • Simplifies the process of creating, deploying and managing ASP.NET Web sites in Azure
  • Provisions new sites within hours
  • Connects your On Premises infrastructure with the cloud
  • Manages content changes easily through a true hybrid cloud deployment
  • Unlimited scalability
  • Reduces time-to-scale
  • Significant cost reductions
Ektron CMS Version 8.6

Ektron CMS Version 8.6

Mobile Web Experience

Mobile Web Experience

Ektron Reference > Ektron's Mobile-Driven Web Experience

Adaptive image resizing enhances the mobile Web experience by resizing images and using a caching strategy. Ektron’s adaptive image support includes:

  • A user-defined series of resolutions— renders the image in a device-appropriate resolution
  • Criteria to determine which files may be resized
  • A caching strategy to minimize the number of hits to your server

Also, you can view any PageBuilder page as it would appear on an iPhone, IPad or Droid.

Third-party Aloha Editor integration

Third-party Aloha Editor Integration

Ektron Reference > Working with a Third-Party Editor

You can use an editor from another supplier with Ektron.

Ektron provides useful plug-ins to the third-party Aloha Editor that let you use it with Ektron. You can download and extract the Aloha Editor from the Aloha-editor.org GitHub repository:https://github.com/downloads/alohaeditor/Aloha-Editor/alohaeditor-0.20.13.zip

After you extract the .zip file, run EditorIntegrationUtility.exe which, by default, is located at C:\Program Files (x86)\Ektron\CMS400v86\Utilities\EditorIntegrationUtility\. Then follow the prompts.

Search Enhancements

Search Enhancements

Ektron Reference > Using Search

  • Search has Microsoft® FAST Search support, which provides the following features:
    • Profile ranking, which forces topics to the top of search results
    • Faceted searching
    • Documentation promotion
    • High degree of relevant results/similar results
    • The "Did you mean?" feature, which suggests close alternatives
  • The Workarea search now uses templated controls, and its user interface is enhanced.
  • Autosuggest, a search feature that suggests similar terms or common refinements that searchers have used in the past that are related to the search term. As a user enters text, possible matches appear
Improved URL aliasing

Improved URL Aliasing

Ektron Reference > Creating User-friendly URLs with Aliasing

Ektron has improved its URL Aliasing feature. Ektron’s URL Aliasing makes it easy to create descriptive, meaningful and SEO-friendly URL aliases consistently, maximizing your Web site’s placement in search results. Use of words and phrases that actually define the page can increase an aliases’ search engine rankings. If you follow a pattern, you can scale your aliases across your sites as they grow. Search engines find URL aliases generated by Ektron. Ektron caches aliases to improve your site's performance.

URLs created in 8.5 migrate seamlessly to 8.6.

You can create the following types of aliases:

  • Manual URL Alias—give a content block a unique name. You can assign several manual aliases to content then decide which one is the primary alias. If multiple alias types are provided for a content item, you can enter any alias into the browser address field to access that content.
  • Automatic URL Alias—create rules to be applied to the following types of CMS entities. When you add content to any of the following types, it inherits the URL alias rules.
    • Taxonomy—create an alias that is based on the taxonomy in your CMS by using the levels of the taxonomy plus the title of the page. Because the alias is based on taxonomy, you can have multiple aliases that have relevancy to multiple search criteria.
    • Folder—create an alias that is based on the CMS folder structure. Descriptive folder names and a well-organized folder structure makes a URL more relevant to the content’s actual location.
    • User—create an alias using the name of a user in the URL. For example, a friendly URL for Steve's profile page can be www.example.com/steve.
    • Group—create an alias using the name of a group to help make community pages within your Ektron Web site easy to remember and find. For example, a friendly URL for car enthusiasts would be www.example.com/cars.
  • Regular Expressions (RegEx)—create a URL match pattern that can redirect or transform a range of URLs with a single setting.
  • Site Alias—lets an existing site URL have more than one URL for the same site. For example, if your company‘s name just changed from Bionics to NewGen, (and the site is essentially intact), you can use site aliasing so your customers can get to the same site content from the old www.bionics.com address and the new www.newgen.com address.
  • URL Redirect Alias—lets a link to an old URL find the new or changed URL that you want. You use this alias when you need to add, change, or modify an existing URL.
eSync updates

Ektron Reference > Synchronizing Servers Using eSync

eSync Updates

The following updates were made to eSync:

  • Content Dependency sync was improved. As of 8.6, Content Sync syncs content and all entities which have direct dependencies to it. This mostly refers to entities linked within a content block's HTML. The following metadata are synched for a content block.
    • Content Selector Metadata
    • File Selector Metadata
    • Image Selector

      Items selected via these selectors go into the metadata.

    • Alias dependencies are synched as part of Content Dependency sync.

NOTE: An 8.5 site talking to an 8.6 EWS will not evaluate or sync Content Dependency eSync because this feature requires database updates. In this case, it will run content sync as it did in 8.5.

  • Backup of configuration files: serverinfo85.xml, data.config and sitedb.config every 24 hours and on-service start and stop (if the files have changed since the last backup).
  • Extensive monitoring improvements for the EWS file sync operations via Windows Performance Counters. Counters allow a service to show the exact progress of activities without impacting performance. These are installed when the EWS is installed and run once.
  • Logging now includes the entire file sync scope, so anyone can easily see what the eSync framework is told to sync. This makes it easy to debug problems in the file sync. Here is an example.

    12/29 3:17:11 PM>TID:13|filesync|Ektron.ASM.EktronServices40.exe|SyncCommFileSyncHelper:
    :LogSyncScopeFilter()|LocalFilePath=C:\inetpub\85CMS400Min\workarea\synctest, 
    RemoteFilePath=C:\inetpub\CMS400Min\workarea\synctest, 
    FolderToSync=Custom, SubdirectoryExcludes=(.svn), FileNameIncludes=(3.pdf)
  • Improved logging of EWS start in the event log, noting if the EWS does not start properly.
  • The log file is a rolling log file based on day and file size in 20 MB increments. The log file name format is winservice.MM.dd.yyyy.<index>.log
  • The error log file has been renamed from test.log to errors.log.
  • eSync restarts if a file sync failure occurs.

NOTE: An 8.5 site cannot translate some status codes from an 8.6 EWS.

New templated server controls

Ektron Developer Reference

New Templated Server Controls

  • Content—combination of ContentModelSource and ContentView; supports custom templates.
  • Menu—combination of MenuModelSource and MenuView; supports custom templates.
  • Access Point—does not support custom templates.
General Enhancements

General Enhancements

Content

Content

Ektron Reference > Working with Ektron Content (See Writing a Summary for Content)

There is a new mechanism for disabling the automatic generation of a content item's summary.

Roles

Roles

  • Membership Admin—Can create, edit, and delete membership users and membership user groups. Member admin role members cannot work with Ektron users.
  • Widget Synchronizer—Lets members access the Settings >Configuration > Personalizations > Widgets screen. On that screen, they can refresh the widget list.
  • DxH Connection Admin—Can create and manage DxH connections via the Connect to DxH screen.

  • DxH User Admin—Determine which users and groups can import and update DxH content into Ektron folders.

DMS and library file types

DMS and Library File Types

Ektron Reference > Working with Assets

2 new web.config keys, ek_DMSFileTypeWhiteList and ek_LibFileTypeWhiteList represent allowed file types for library assets and DMS assets. In the Workarea, you may only add only file extensions included in the list. To add a new file type, first add it to the web.config key, then add it in the Workarea. This functionality was added as a security precaution.

Deleting Smart Form Configurations

Deleting Smart Form Configurations

Ektron Reference > Working with Smart Forms

You can delete a Smart Form Configuration only if no content is assigned to it. If content is assigned, you must first delete all assigned content. A new toolbar button lets you view and delete all assigned content.

Improved access to product documentation

Improved Access to Product Documentation

Ektron Reference

Ektron has a new HTML5 format for viewing Ektron Workarea help and the Web format on the Ektron documentation page. This format requires a browser with robust HTML 5 support. Ektron also has a mobile format for viewing help on a hand-held device. The product documentation is optimized for searching, scanning, and finding the information you are looking for.

Support

Support

Existing clients current with maintenance should use Ektron Support for questions or issues. Anyone evaluating Ektron 8.6 for any other reason is urged to engage with Ektron Sales for direction and options for further assistance.

Feedback

Feedback

Ektron encourages your feedback and wants to speak to you about your concerns, interests, and project needs. Please contact your Account Manager for more information. Send all other requests to support@ektron.com.

Issues resolved for Ektron Version 8.6
  • 24792—A new role, Membership Administrator, lets the assigned user create, edit, and delete membership users and membership user groups. Member Admin role members cannot work with Ektron users.
  • 49875—Previously, if you had 2 sites on the same server, one configured for Load Balance (with an LB license key) and one not, the Ektron Windows Service saw that LB was enabled in the config file. But, since the second site did not have an LB key, the Ektron Windows Service would stop. This is fixed.
  • 49978—If you add a customized style sheet to a folder, then applied a style to text within the editor, the drop-down might display incorrect spacing and possibly incorrect icons. This has been fixed in the Aloha editor, supported in Release 8.6.
  • 53864—Previously, if a user viewing his profile page clicked You have 0 unread messages, he would move to the Activity tab. Now, the text links to the Private Messages tab.
  • 54057—A new role, Widget Synchronizer, lets members access the Settings >Configuration > Personalizations > Widgets screen. There, they can refresh the widget list.
  • 55714—Error adding calendar event with ampersand in location. This is fixed.
  • 58194—Previously, when you added another site to your eSync chain (beyond the first two), the share_index field in the settings table was not being properly updated in one or more environments. This is fixed.
  • 54635—For a while, if you added showreport=true to the query string for a template with a poll control, the control did not display the poll's results. Now, results are displaying properly.
  • 59216—Previously, the AddTaxonomyItem method, while adding the content to the specified taxonomy, erroneously removed that content from all other taxonomies. This is fixed.
  • 59572—This fix involves the OnTrek starter site's home page, which has a slider control. That control is driven by a Smart Form with a slider speed value. Previously, changing that value had no effect on the slider display. This is fixed.
  • 59638—This fix involves placing a ContentBlock server on a template and setting the CacheInterval attribute to a value, for example 500. Previously, if you edited that content and clicked the preview button, initially preview works as expected. But if you edit second time and click preview, you had to wait 500 seconds to see the content. This is fixed.
  • 60029—Using the Aloha editor, you can change the look of the style drop-down menu within the editor, not just the individual lines, but also captions, borders, etc.
  • 60110—Two aspects of the Upcoming Events widget were fixed: If you uncheck Enable Paging, it actually does that now. Also, you can change the text of the read more hyperlink.
  • 61713—When a group is added to a folder or content's permission list, new methods retrieve permissions of a particular user by passing the userID: GetContentPermissionsList(user Id, cont ID) GetFolderPermissionsList(userId, folder ID).
  • 61827—The Content Awaiting Approval report (on the Reports tab) and the Content Awaiting Approval widget used to be limited to 300 content items. This restriction was removed.
  • 62603—If you create content in a folder that already contains content with the same title and the title includes an apostrophe, a number is now appended to the title of the second content item. This was only a problem if the title includes an apostrophe.
  • 62608—When editing content and deleting a library item, the user is prompted to also delete it from the server. Previously, this option was available only within the library.
  • 63102—Accented characters (like ë) no longer appear as their encoded value in the content title.
  • 64102—Fixes an issue where, occasionally, content was missing its associated QuickLink in the Library.
  • 64192—A very small rounding error calculated by a percentage-based coupon was fixed.
  • 64888—Fixes a problem with the template sync when the assetmanagement.config file was included.
  • 65141—Suggested search results were fixed for the OnTrek sample site.
  • 65205—Fixes a problem of hyperlinking in an event calendar. Now, the popup hyperlink window has an ellipsis (...) button next to URL so you can choose the link destination..
  • 65263—You can databind UI controls, so that you can rapidly deploy a user interface.
  • 65733—When a sync setup was upgraded from a previous version to 8.5, and content or a folder was deleted before the upgrade but after the last sync was performed, running a sync afterward did not delete the content or folder from the other side and caused skipped changes concerning the metadata assigned to the content.
  • 65613—Previously, if you used the usermanager API in the Framework to get a user object, modify and update it, the membership user was now verified when no one has done the verification. This was fixed.
  • 65824—Fixes a problem that occurred when trying to add a Targeted Content configuration if the Workarea language was not the default language.
  • 66529—Exception in FixOlderVersions Loadbalance license is invalid. This is fixed.
  • 66597—An inaccurate error message used to appear if you tried to add a membership user using an API call. Now the correct error appears: "invalid username\password error".
  • 66320—Customer user properties are no longer overwritten.
  • 66630—Fixes a problem involving Active Directory setup. When you see Active Directory Authentication is enabled and requires more configuration and click the CMS relationships need to be associated with Active Directory relationships, user names now appear.
  • 66725—Previously, if you
    1. Enabled Automatic URL Aliasing.
    2. Enabled Device Detection in the web.config file.
    3. Went to a content block and made sure an Auto Alias was assigned to it.
    4. Edited that content and clicked preview.
    5. You were prompted to view the content.
    6. You saw an error.

    This is fixed.

  • 66832—Pagination was added to the screen on which you add content to a collection. Now you can jump to a specific page by number.
  • 66865—Facebook updated their API to use oauth1.0 in their init. Ektron's Facebook interface was updated to support this change.
  • 66928—Fixes a problem with the PageBuilder toolbar. Now, if the lang type is specified in the URL as French, the Page Layout menu appears in English.
  • 66993—Fixes a problem with the CMS:WebSearch server control ButtonImgSrc. Previously, it was always prepended with /workarea/. Now, a new IsButtonImgPathSiteRoot property indicates whether ButtonImgSrc property is relative to siteroot or not. The default is false, which mean that the path is relative to Workarea.
  • 67059—Previously, some clients saw Workarea errors when deleting a taxonomy. The problem occurred because the server name stored in the AssetServerTable was being truncated. This is fixed.
  • 67074—A blog moderator gets more information about a blog comment before deciding to approve it.
  • 67082—Previously, if a membership user created via Facebook login was deleted, if anyone tired to create that user again, he was prevented from doing so. This is fixed.
  • 67190—Web Trends On Premises is no longer supported.
  • 67220—If you create a content item with the trademark (TM) special character in the title, Automatic Aliasing removes the "TM" symbol from the alias.
  • 67236—You may mark Ektron cookies as HttpOnly via a new web.config boolean property, ek_HttpOnly.
  • 67256—PageBuilder follows the same conventions as the Workarea regarding the language on the screens.
  • 67329—While using the Aloha editor, you can undo a replace action.
  • 67360—You can use the GetList method to retrieve menus based on specified criteria.
  • 67566—The case-sensitive database check now occurs when the database connection test is run. Previously, the check occurred later in the installation, and caused a login failure.
  • 67595—Fixed a problem with the ei_news widget. Previously, if you clicked the widget's Taxonomy tab, and drilled down one level to see subfolders, none of them had an expand icon.
  • 67596—Previously, in a folder that allows page layouts and has many folders, if you selected New >Page Layout, it took a long time for the wizard to open and display available wireframes.
  • 67628—If you use the Aloha editor, and you enable the Style dropdown for the in-context editor toolbar, custom classes for IMG tags are applied properly, regardless of the browser version.
  • 67717—For the eWebEdit400 editor: When manipulating a table, the Cell Properties Dialog accurately reflects the height and width of the current cell.
  • 67741—When performing a Backup and Restore of an initial sync, the server index in the settings table for the receiving site's database is now updated properly.
  • 67752—In Firefox 10 on a Mac, users editing content in eWebEdit400 can see DMS quicklinks when using the hyperlink/library buttons.
  • 67782—Previously, when synching a staging server, if there was a large number of files in the asset/library folders or the assetlibrary, eSync created so many .tmp files that an error would occur. This is fixed.
  • 67842— Previously, if User_A edits a PageLayout and then checks it in, User_B cannot edit the page. User B must publish the content before he can edit. This is fixed.
  • 67858—eSync includes Targeted Content configurations.
  • 67860—In the Workarea/content.aspx.cs file, the RegisterJs and RegisterCss methods no longer add an additional forward slash (/) to URLs that they create.
  • 67919—If you use the Aloha editor and left-align an image then add bulleted list items to the image's right, the bullets do not overlap the image.
  • 67977—A Today button is available on calendars. Click the button to insert the current date.
  • 68063—Client-side paging in a Smart Form Content Selector field no longer causes time outs.
  • 68085—Assume that you edit content and add a link to a PDF. If that link appears in search results, you can now click the link to access the PDF.
  • 68146—If you passed as a parameter a list of folder IDs to search, and the number of folders exceeded 10, an error occurred. This is fixed.
  • 68192—Calling the function, FolderManager.GetItem (), passing the parameters GetItem (0, false, true) returned the root as a child item when the parent is the root. This only occurred when you passed a false Boolean as the second parameter. If a true Boolean value was passed as the second parameter, the root was not returned as a child item if the root was the parent. This is fixed.
  • 68244—If you tried to use the email report option in the Contents > Reports section in Workarea, an error occurred. This is fixed.
  • 68265—A new error message was added: "Cannot view or edit files with &,+ and % characters in the file name or folder path."
  • 68358—Pagination and search functionality is now available for user groups.
  • 68360—Display Host Name in Workarea to help orient CMS users is added.
  • 68363—After upgrading to 8.02 SP3, blog posts in some categories (subjects) were not displaying. It is fixed by retrieving the post based on the category, after setting the maxresult property.
  • 68367—Exporting form data does not export all responses. This is fixed.
  • 68432—3-Tier documentation updates needed. The documentation is updated.
  • 68469—Dashes were not importing correctly when pasted from Microsoft Word. This is fixed.
  • 68472—When editing a community group via the site, the Delete button was confused for a cancel/close action. Button icon changed to reduce confusion.
  • 68474—Errors occurred during a full search crawl: could not crawl users, user groups, and content. This is fixed.
  • 68482—Ports 6080 and 6081 are required to be open for aspects of Search Server to work. This is documented.
  • 68495—On the Group Invitations Sent to Users screen, you cannot delete a user even if he is no longer an Ektron user. This is fixed.
  • 68497—Tooltip still shows Add Favorites after an item is added to favorites. This is fixed.
  • 68523—Case-sensitive passwords setting was not working. This is fixed.
  • 68567—Reordering taxonomy categories: Once a display order is established, if you tried to re-order items and click Update without actually moving any items, the last item in the list had its display order set to 1. This is fixed.
  • 68569—Blog posts were sorted by oldest to newest. It now sorts newest to oldest.
  • 68570—Error viewing automatic alias when content title contained a plus sign (+). This is fixed.
  • 68593—When you had a single quote along with a special character that needs encoding, it did not properly decode the value when the content title was being displayed in the Workarea. This is fixed.
  • 68603—Adding taxonomy to content in 1 language is not saving in the others.
  • 68616—MetadataTypeManager.GetItem() returns isEditable false when set to true in the Workarea. This is fixed.
  • 68633—Error from event viewer when viewing a deleted forum post. If you created a forum post and then deleted the topic, and then clicked a link to the deleted topic, an error occurred. This is fixed.
  • 68642—DMS source documents were not deleted after being cut and pasted to another folder. This is fixed.
  • 68643—GetCollectionList timing out. This is fixed.
  • 68663—Framework API: contentId was not being added to Library property enum. This is fixed.
  • 69753—DMS file names cannot contain period characters (.). DMS changes periods to underscore characters (_).
  • 68785—Device detection was seeing the Internet Explorer 9 browser as Windows Mobile 7.5 device. This is fixed.
  • 68815—Taxonomy not working when you enable both Italian and Portuguese under language settings. If you created a new taxonomy, then created a taxonomy for each enabled language, but 2 languages were not appending to the old taxonomy.
  • 68859—GetDefaultBasket returns NULL when using BasketManager. This is fixed.
  • 68896—Paragraph tags are not created when a single paragraph of text is used in a content section. Ektron introduced a provider-based editor in 8.6 to alleviate formatting issues such as this.
  • 68901—An alias redirect was returning a status code of 301 instead of 302. This is fixed.
  • 68923—Single occurrences of recurring events are not being deleted. This is fixed.
  • 68942—Ektron.Cms.Framework.Calendar.WebEventManager call GetEventOccurrenceList() did not return event metadata as part of the list. This is fixed.
  • 68956—A calendar event was not saving the event setting for times. This is fixed.
  • 69001—On the Workarea configuration screen, Smart Forms would not sort by ID. This is fixed.
  • 69002—The IDs on the controls were not consistently in the Search Framework API sample. This is fixed.
  • 69051—WebCalendar widget Event color dropdown was cut off in Firefox 12. This is fixed.
  • 69066—Activating users using Ektron API AuthGuid failed. AuthGuid returns GUID values now.
  • 69075—Security issue addressed.
  • 69079—When a Community Group that included a group calendar is deleted, the calendar folder (ekCalendar) is not deleted and is left without a parent folder. There were some features of CMS that recursively got the parent folder; consequently, when no parent folder existed, the feature would stop working (timeout). This is fixed.
  • 69147—When upgrading OnTrek from 8.5 RC1 (8.5.0.310) to 8.5 SP2, the site failed. This is fixed.
  • 69196—The CMS Administrator Group Association field improperly appends @domain in the group name field, and an error occurs when subsequent settings are updated. This is fixed.
  • 69200—The content folder table was set to allow up to NVARCHAR(100). The Stored procedures that use it were not updated from NVARCHAR(75). This is fixed.
  • 69238—Blog widget settings were not saved. This is fixed.
  • 69251—While changing a URL Aliasing rule, cms_UrlAliasMapping executed twice. It now executes once.
  • 69389—Documentation for v85 does not mention DHTML menu deprecation. It has been removed.