Installing the KodHedZ Content Server and Client Components
The KodHedZ Content Management Suite consists of two distinct sets of components. Depending on the configuration of your system, they will be configured differently.
1. Installing the Server Modules
Within the main zipfile you receive, there are 8 different packages. Install only the components you require into your Server DotNetNuke Instance. It is mandatory to install the file titled KHZ.Content.Server.zip as this contains the operating components and web services. Also install the file named KHZ.ARC.zip. You will also want to make a few changes to the web.config file as there are some directives that need to be added.
in the web.config:
You will need to manually copy the file AjaxUploader.lic into the /bin folder of your server website instance.
Usually you will also install the KHZ.Content.Signup.zip module to allow users to register for accounts, but in certain circumstances, this can be installed onto a third party DotNetNuke portal to facilitate content account signup from a remote website.
If you want your users to be able to create and manage their content, videos and images directly within the Server website, you will install KHZ.Content.Manager.zip, KHZ.Content.ManagerList.zip and KHZ.Content.DragDrop.zip into the server website.
To display the content articles within the website, you will install KHZ.Content.Loader.zip into the server website.
The KHZ.Content.PurchaseCredits.zip module is generally placed on the same page as the Content Manager and facilitates the purchasing of page credits for the active Content Account. This is coupled with the KHZ.Content.AccountSummary module, which shows the various status of the current account, including credit balance and published pages.
Generally this is the extent of the server modules. The remainder of the zipfiles are used to handle displaying and searching the content. These are designed to be placed on a separate DotNetNuke portal and utilize web services, but they can also easily be added to the Server DotNetNuke instance if you wish to use a single instance for both serving and displaying the content.
The Content Server Package comes with a web.config file designed to integrate into your existing DotNetNuke 4.5.1 Instance. There are numerous changes defined that must be followed for both the Server and Client Instances to work properly.
2. Installing the Client Modules
The modules that are to be configured on the Client website are as follows:
The primary module is KHZ.Content.Loader. This provides the reading interface for the content pages.
It can be supplemented with the KHZ.Content.Search module to provide a search lookup for your articles and/or the KHZ.Content.TagList to provide a Title lookup of all the articles in your Content Account.
Togther these three modules make up the usual interface for reading and navigating your Content Articles.
To add more life to your pages, you may choose to sell specific content pages, or to display the license associated with the current page that is displayed. You can add the KHZ.Content.ContentPurchase module to the page to acheive this affect. The content articles themselves contain the license and the price, and determine if the item is for sale.
There is a simple Mailing List Signup module that allows each content author to collect a list of email addresses from subscribers to their articles. This also allows the subscriber to view the RSS feed in an easy link from the articles. This module is called KHZ.Content.EmailInput.
<httpModules>
<add name="CuteWebUI.UploadModule" type="CuteWebUI.UploadModule,CuteWebUI.AjaxUploader"/>
<add name="KHZ_ARC" type="KHZ.ARC.ARCInit, KHZ.ARC" />