Ektron 9.00
To work with content on your website or in the CMS Workarea, you must log in as a CMS user. Ektron lets you access content on a Web page in the following ways:
Ektron has many types of content that you can use on your website. See Understanding Ektron Content for information about the types of content.
A website consists of pages that are made up of one or more blocks of content as shown in the following example from the home page of one of Ektron’s sample sites.
The following sections provide information about Ektron content.
Every piece of content in Ektron is one of the following types.
NOTE: For information about editing content, see Editing in Ektron.
Non-HTML content types:
Specify a title and begin creating your new content item.
NOTE: Only the last approver in the approval chain sees the Publish button. Other users see Submit. If no approval chain is assigned to the content’s folder, every authorized user sees Publish.
All required metadata must be added before content can be checked in or submitted into the approval chain.
A folder's Aliasing tab has a Manual Alias Required check box. If checked, the user creating or updating content must enter a manual alias before the user can save or submit the content.
After you create content, you or your system administrator typically make it available on the site. For example, you can add a hyperlink to it from another page, or place it in a collectionA list of Ektron content links for display on a Web page. or menu. Your administrator can add it to a list summary or content list.
You can set up an approval process by which content is available to your website after it is reviewed by people with approval responsibility. See Also: Accessing the Permissions Table. When a content creator submits content for publishing approval, an email is sent to the list of approvers. When the last approver signs off, the new content becomes available on the website. The following graphic illustrates the content approval cycle.
To help track content’s position in this workflow, Ektron assigns a status to each content item. The status determines what you can do with it, and indicates what must occur for it to get published to the website. See Also: Content Statuses.
You can move content from a folder to another folder. Or, you can copy content between folders. Moved content retains the original ID number, while copied content gets the next available ID number.
Your can only move or copy content that has an Approved status. If a destination folder has an approval chainA series of users or user groups who must approve content before it can be published., the content status changes to Submitted (or Approved if you are the last person in the approval chain).
NOTE: The folder's Approval Method can affect the status of the moved/coped content. See Also: Setting the Approval Method
You should move or copy content only between regular folders or eCommerce catalog folders. Do not move or copy from or to other folder types. If you copy an eCommerce catalog entry whose product type is not assigned to the destination catalog folder, the new product type gets assigned to the folder. See Also: Defining Roles; Managing Folder and Content Permissions
To move or copy content between folders:
NOTE: If you are copying content, and the content exists in more than one language, you are informed that some content exist in several languages and asked if you want to paste them in all languages or only selected languages. If you are moving content, all language versions are moved.
Permissions for moving or copying content are defined as follows:
When content is moved or copied, the following changes are made.
NOTE: If the Link Management setting in the web.config file is set to true
, you do not need to update the quicklink. Link Management automatically finds the correct template based on the current folder.
ASP.NET Unleashed(2)
.The Delete command lets you permanently delete content from your website. You can only delete checked in or approved content. And, you can only delete an eCommerce catalog entry if it is not on an order and its status is checked in or approved.
NOTE: If you do not see a Delete button or menu option as described below, you do not have permission to delete.
Like publishing, deleted content must proceed through the approval chainA series of users or user groups who must approve content before it can be published. before it is removed. If you are the last approver in the approval chain, the content is deleted immediately. See Also: Approving or Declining Content
NOTE: It is good practice to check for broken quicklinks before deleting content.
Use the link checker button to locate all content with a link to the current content. The identified content that will include a “dead” link after you delete the current content. So, remove or change the obsolete links before deleting.
On the View Contents of Folder screen, you can delete several content items at once.
A content summary is a short description that supplements the title when several content items appear on a Web page, such as Web page of top news stories. Content authors compose a summary when creating or editing content. Web developers can create pages that display the content title and summary to attract readers to the full story. Summaries can include images and various font styles and sizes.
TOP STORIES
Ektron Launches International Distribution Program(08-08-2009)
|
Ektron automatically generates a summary for new content if none exists when it is first published. If the summary is blank, Ektron copies the first 40 words of content to the summary. After the content is published, you can update or delete the summary. If you delete a summary, it remains blank and is not automatically generated again.
By default, content summaries are automatic generated. To disable that:
ek_enableContentAutoSummary
to falseGenerateAutoSummary
to zero (0) If a membership user edits content and wants to update the summary, the user checks the Auto Generate New Summary field on the membership editing screen, and the first 40 words of the content are automatically copied into the summary.
There is no limit on the number of times a membership user can automatically generate a new summary.
You can only edit the summary of content that is published, checked in, or checked out by you. When you enter or edit existing content’s summary, its status changes to checked out. After you create or edit the summary, click Check-In to check the content in. From that point, you need to submit or publish it.
Private content is available to Ektron administrators and users or membership users with at least Read-Only permissions for its folder. Those users must log in to work with private content. Unauthorized site visitors cannot see it. When you make a folder private, the content and any subfolders are also private (if they inherit permissions). You also can designate specific content items as private.
IMPORTANT: Private content is hidden from search results if your search provider is Microsoft Search Server 2010. It is not hidden if you are using another search provider.
NOTE: You can determine the appearance of the menu shown above. See Working with Ektron Content.
NOTE: You can only set content to private when inheritance is broken. See Also: Inheriting Permissions
If assetan external file, such as a Microsoft Word document or image, stored in Ektron. It can be managed like native Ektron content.s are set to private, they are handled like other private content with one important exception: unless you follow the procedure described below, anyone can access an asset by typing the URL of the asset into the browser’s address field.
If a user attempts to access the asset in any other way (such as, linking to it from a Web page), the regular methods of making content private work. See Making a Folder Private and Making Content Private.
To make assets private even if someone types their URL into the browser’s address field:
NOTE: If site users receive a 404 Page Not Found error when trying to view private assets, make sure you have completed all steps below.
web.config
file, located in the site root folder.<remove verb="GET,HEAD,POST" path="*"/>
<httpHandlers> <remove verb="GET,HEAD,POST" path="*"/> <add verb="HEAD,OPTIONS,PROPFIND,PUT,LOCK,UNLOCK,MOVE,COPY,GETLIB, PROPPATCH,MKCOL,DELETE,(GETSOURCE),(HEADSOURCE),(POSTSOURCE)" path="*" type="Ektron.ASM.EkHttpDavHandler.EkDavHttpHandlerFactory"/> <!-- <add verb="GET,POST" path="*.doc" type="Ektron.ASM.EkHttpDavHandler.EkDavHttpHandlerFactory"/> <add verb="GET,POST" path="*.docx" type="Ektron.ASM.EkHttpDavHandler.EkDavHttpHandlerFactory"/> <add verb="GET,POST" path="*.xls" type="Ektron.ASM.EkHttpDavHandler.EkDavHttpHandlerFactory"/> <add verb="GET,POST" path="*.xlsx" type="Ektron.ASM.EkHttpDavHandler.EkDavHttpHandlerFactory"/> <add verb="GET,POST" path="*.ppt" type="Ektron.ASM.EkHttpDavHandler.EkDavHttpHandlerFactory"/> <add verb="GET,POST" path="*.pptx" type="Ektron.ASM.EkHttpDavHandler.EkDavHttpHandlerFactory"/> <add verb="GET,POST" path="*.vsd" type="Ektron.ASM.EkHttpDavHandler.EkDavHttpHandlerFactory"/> <add verb="GET,POST" path="*.vsdx" type="Ektron.ASM.EkHttpDavHandler.EkDavHttpHandlerFactory"/> -->
Eight add verb
statements in the middle are commented out.
<add verb="GET,HEAD,POST" path="*"
type="Ektron.ASM.EkHttpDavHandler.EkDavHttpHandlerFactory"/>
web.config
.Scheduling lets you control when a version of content becomes visible on the website or when it expires (and is removed).
When you create or modify content, you can select a “go-live” date and time. If you do, after the content passes through the approval chainA series of users or user groups who must approve content before it can be published., Ektron publishes the content to the live site at the scheduled time. For example, your company is having a sale of the century in a month, and everything is ready except the announcement. With this feature, you create the Web content now and set it to go live a week before the sale.
The Ektron Windows Service manages these changes to your site. See Also: Handling Background Processing Functions with the Ektron Windows Service
NOTE: When you select a time for content to go live, that time depends on the server’s system clock. If the clock is incorrect, the content will not go live at the intended time.
After you save the content, it appears on the Content Pending Start Date report, which tracks content with a future start date. See Also: Content Pending Start Date Report
After you set a go-live date and the content completes the approval chainA series of users or user groups who must approve content before it can be published., the following scenarios may occur:
When you set a go-live date on new content, it becomes viewable on the specified date and time as long as it completes the approval chain. If a site visitor accesses the page that contains the content before then, only the template appears.
If a logged-in Ektron user browses your website, the user sees a gray border around the content until the date specified. If the user clicks within the gray border, the user can use the Preview option to see the new content.
When you set a go-live date for changes to existing content, and it completes the approval chain, a logged-in Ektron user sees a gray border around the content until the date specified.
When you view content on the website, you see the previously published version. When the go-live date occurs, the new content replaces the previous version, and its status changes to Active.
When content reaches its end date, it appears on the Expired Content report. See Also: Content to Expire Report
If your choice means the content will not appear on the website, you should have another content item ready to replace it. If not, the template appears without the content.
Use content’s archive options to determine what happens upon reaching its end date/time. To be eligible for any option, the content must reach its end date/time, progress through its approval chainA series of users or user groups who must approve content before it can be published., and be published. Until those events occur, the content remains visible within its Workarea content folder and on the site.
Archive and remove from site (expire)
Archive and remain on site
contentype
property is set to Archive_Content.http://localhost/CMS400Developer
/dynamic.aspx?id=1014&__taxonomyid=14
Add to CMS Refresh Report
You can view and restore past versions of published content. After viewing previous versions of content, authorized users can replace the current version with any previous one. See Also: Managing Folder and Content Permissions
Ektron assigns a unique number to each content version. The number is increased by one tenth if the content is checked in but not published. If the content is published, the next whole number is assigned. For example, if the current version is 1.0 and you check in that content, that version is 1.1. If the next editor publishes it, that version is 2.0. Published version are indicated by an arrow.
If content versions are purged, the numbering scheme restarts with the remaining content.
NOTE: The Purge History feature deletes historical versions of content according to user-defined criteria. Therefore, some previous versions may be unavailable. See Also: Purging Content History
The window displays the following information for each version.
To view any version, click its title to display the Content History window for that content.
There are 3 view modes.
If content can be compared with another version, the View Difference button () appears in the content history area or the Web page view.
NOTE: The first time you use the View Content Difference screen on a client machine, you are prompted to install the differences tool. When the installation program completes, close and reopen the View Content Difference feature.
There are varying versions of this procedure. Consult your system administrator to determine the correct procedure for you.
NOTE: The ability to restore content is a permission granted by the system administrator. If you do not see Restore on the View Content History screen, you do not have permission to do so.
IMPORTANT: Ektron recommends restoring a Checked In version of content, because this restores all content attributes. If you restore a published version, metadata is not restored.
To learn how to recognize checked-in content on the View Content History screen, see Managing Versions of Content.
If desired, check out the content to make additional changes. Select the workflow to perform on the content. When the historical version is approved, it is published to the website.
You can only remove an applied XSLT when viewing historical versions of XML content. If you remove the applied XSLT, you can view the content without the irrelevant XML tags.
IMPORTANT: