Latest in FAQs

Please note that this works only for controls and not web parts. After you have set the properties of some control in the code behind, you need to force the data reload. Below is example with CMS List Menu control.

ASPX code: <cms:CMSListMenu ID="ListMenu" runat="server" ClassNames="CMS.MenuItem" Path="/%" />

In the code behind you can place this code to the Page_Load method, but it is recommended to override the OnInit method:
protected override void OnInit(EventArgs e)
    {
        base.OnInit(e);

        this.ListMenu.Path = "/Partners/%";
        this.ListMenu.ReloadData(true);       
    }

You need to insert the license as you have recieved it. This means also with the domain name, product and expiration. Please make sure you are entering license for appropriate version (2.x, 3.x, 4.x, etc.) and that there are no white spaces or lines.

Could you please set the default page of your web site through the Site manager-> Settings-> <selectYourWebSiteFromTopLeftDropDownList>-> Web Site-> Default Alias Path and set the path e.g. to "/home". You could look for the alias path of the particular page in the CMS Desk-> Content-> <page>-> Edit-> Properties-> General-> Alias path. Please note there is no need to set up this information in the IIS.
Second option is that the documents have set different culture then the default content culture. You can check this setting on the Properties tab of each document and for the site you can check it in Site Manager -> Sites -> edit your site -> Default content culture.
Another possible setting is in Site manager-> Settings-> <selectYourWebSiteFromTopLeftDropDownList>-> Web Site-> Combine With Default Culture. It should be checked if you are using multilingual site.

To set SSL for logon.aspx page, please go to your solution in Visual Studio, open CMSPages/logon.aspx and it's code-behind file.
Now write please following code in Page_Load method:

if (HttpContext.Current.Request.Url.AbsoluteUri.ToLower().StartsWith("http://"))
{
   Response.Redirect(HttpContext.Current.Request.Url.AbsoluteUri.Replace("http://", "https://"));
}

Could you please check the IIS settings? We had a similar problem in the past caused by the wrong setting of the application pool (IIS 6 and higher). For more information please see http://www.developer.com/net/asp/article.php/2245511.

The subject of the e-mail is a resource string. You can find the key value in the CMS.resx file placed in CMSResources folder. In this case it should be "ordernotification.customersubject" and "ordernotification.administratorsubject".

You can change the values for these key directly in the resource file. The "{0}" is a macro and the orderID is displayed instead.
Other way is to add these keys to the Site Manager -> Development -> UI Cultures -> click to edit En culture -> New string. Add the key value and the text you want to have. This will ensure that you will be able to easily translate the subjects in other languages (www.kentico.com/docs/devguide/international_support.htm).

The problem is that often the developers are using applications like MultipleIEs to have older versions of IE on the PC. They are testing it in this application and there is probably some bug in it when using IE6. When the site is visited in the default IE6 - it works fine, but it breaks in MultipleIEs e.g. on some post back action - the CSS styles are missing or corrupted. 

The error is usually thrown on this line of code <uc1:ForumUserPicture ID="picUser" runat="server" />. This happens when using precompiled web sites which are allowed to be modified. It may help to uncheck (set to false) "Allow this precompiled site to be updatebale" when precompiling the web site and/or to clear .Net cache.

Go to Site Manager -> Settings -> <your site> -> Content Management -> Personalize user interface by permissions checkbox and check it (set it to true).

Go to the document Properties teb -> General -> Document URL path and change the value to be for example: /home/

We have tested our product on MS Windows Server 2003 with MS SQL Server 2005 (both 64-bit editions) and it works with no problem. We use only standard .NET/SQL2005 features. Kentico CMS is compiled for 32bit OS, so if you wish to fully leverage the 64bit OS, you may need to recompile the full source code using Visual Studio 2005/2008 for the 64bit environment.

This problem is partially caused by PayPal. PayPal somehow remembers all of the OrderIDs , so in case you performed some test orders and you have deleted them after and tried to create a new order it might have the same OrderID that has been previously marked in PayPal as "paid".

It is recommended to go to the Kentico CMS database -> COM_Order table and check your 'OrderID' column, eventually to increase next OrderID to some value you are sure has never been used before.

Make sure that on both servers is the system time the same. Make sure that the Microsoft.Web.Services3.dll.rename was renamed to Microsoft.Web.Services3.dll

CMS is set to store the files on file system. When you create link to some file document uploaded to the CMS, you have two choices - to use and not to use permanent URLs. Then, when some visitor wants to save the file, it is saved with the GUID name. If you want to set the CMS to allow downloading the files with they real file name, you need to uncheck (set to false) this box: Site Manager -> Settings -> Files -> Redirect files to disk.

This means when set to true, if the files are on the disk, they are obtained from there including the GUID name. If false, the name of the file is obtained from DB.

Yes, Kentico CMS produces valid XHTML code. Also the built-in WYSIWYG editor automatically cleans up the code so that it's XHTML compliant. You also have full control over the HTML (XHTML) code of the page layouts and document transformations, so you can always adjust the code so that it's XHTML compliant.

If your web site uses a dark body background, you may want to use a different background for the WYSIWYG editor. In such case, you need to specify the CSS styles like these:

.LTR, .RTL
{
  // set the dark background here
  background-color: black;
}

BODY
{
  // do not set any background here ...
}

The LTR/RTL style is used only for the web page background, while the BODY style is used for both the page and the WYSIWYG editor. Alternatively, you can create a separate CSS stylesheet and assign it to the editor in Site Manager -> Sites -> Site Properties -> General dialog.

You may want to check the following settings:

1. Make sure the "Show for document types" property value is empty and the "Document types" property is set to appropriate document type, such as "cms.news" (without double quotes).
2. Make sure the "Transformation" value is set.
3. If you specified any "Path" property value, set it to /% and test if it helps. If so, you may need to adjust the property value.
4. If you specified any "Site name" or "Culture code" value, try to clear the values.
5. If you specified any "Maximum nesting level" value, try to set it to -1.
6. If you specified any "WHERE condition" value, try to clear it.
7. Make sure the "Check permissions" value is set to false or - if you want to check the permissions - make sure that the current user has appropriate permissions. 

Sometimes you need to change the date format from the default US format (mm/dd/yyyy) to other, e.g. dd/mm/yyyy. Please follow these steps:

1. Go to Site Manager -> Development -> UI Cultures
2. Click 'New UI Culture' and insert for example following values:
     UI culture name: British English
     UI culture code: en-GB
3. Click OK to save changes.
4. Go to edit user (CMS Desk -> Administration -> Users -> edit the user account you are using) and change 'Preferred user interface culture' to British English (you can make the same setting in CMS Desk -> My desk -> My profile).
5. You may need sign out and sign in back for the changes to take effect.

Please note: the date format on the live site is changed according to the site culture.

You can specify max file size by setting max request length parameter in the web.config file. Please open the web.config file, find the <system.web> section and insert the following line into it:

<httpRuntime maxRequestLength="8000"/>

This will increase the max file size to 8MB. You can find more information at: http://msdn2.microsoft.com/en-us/library/e1f13641(vs.71).aspx

If you're using version before 2.2, you may receive an error message like this:

Exception Details: System.Security.SecurityException: Request for the permission of type 'System.Web.AspNetHostingPermission, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed.

You need to upgrade to version 2.2 and adjust the security settings as described in the KB article Kentico CMS in a Medium Trust Environment.