The change token is used to detect collision. The error you saw typically occurs if the content or the properties of the page has been changed by another person. Generally this is before you save your changes, but after you launched the Page Properties dialog.
One known issue is that you may have a stale cached version of the dialog. The solution is to ensure that the Microsoft® Internet Explorer option for "TemporaryInternetFiles > Settings... > CheckForNewVersionOfAPage" is not set to "Never". "Automatic" is the default setting and will avoid caching these dialog pages.
[Back to Top]
Topic: CmsAuthorizationModule missing in web.config
When saving a page I get the following error message in the error console:
Save Placeholder Failed
-----------------------------------------------------------
Error Details:
The current user does not have rights to edit the requested item. If you are seeing this exception when a MCMS template is executing, it means that you have removed the CmsAuthorizationModule from the HttpModules section of your web.config. You can only remove this module if: 1. All requests for every MCMS template in the web application will only be accessed by anonymous users 2. Guest access is enabled in MCMS (via the SCA) 3. The MCMS guest user has access to all postings based on templates in the web application If any of these requirements are not met, you MUST register the CmsAuthorizationModule in your web.config.
-----------------------------------------------------------
I checked my web.config files and the CmsAuthorizationModule is listed there. What could be the problem?
Answer
Although the error message indicates a missing authorization item in the web.config file, this is not the case. The error actually occurs when the editor is saving a page and is validating the contents of the placeholders and the template. If any invalid resources are referenced, the above "Save Placeholder Failed" error appears.
Typical scenarios for invalid resources include:
- A resource is added to the resource gallery, and a link to the resource is successfully added to a posting. Later the resource is deleted. When the page is next edited, the link to the now missing resource is invalid.
- An editor adds a link to a resource stored in a resource gallery. Then the editor's access rights to the gallery are removed. Next time when editing the page, the editor would get the above error, because the link would appear invalid.
- The author has only subscriber rights to the template gallery but not editor rights.
How to recognize invalid links?
In order to find out which link is invalid, the editor must go to the page in live mode, and click each of the links. If the link is valid, it works. If the link is not valid, either a "Page can not be displayed" error message is displayed (or the system will ask for username and password - as in error 2 above). It is also possible to write a script to crawl your MCMS pages looking for broken links.
Why can the administrator save the page on behalf of the editor?
When a resource is deleted from the resource gallery, the physical item is still in the database. However, it is no longer associated with a resource gallery. As resources are accessed with a GUID based link, the access to the item is possible but it is no longer possible to access the information about which users are allowed. This information is stored in the resource gallery. But as the item no longer belongs to a resource gallery the currently user cannot be verified. MCMS Administrators on the other hand, have access to all items. This means that no access check is done. This means that administrators also have access to deleted items which have not yet been removed from the database (during background processing). Therefore, when an administrator saves a posting, the placeholder content seems valid, and the save is successful. This is true as long as the resource has not been deleted from the database by background processing.
What must the author do when getting this error?
The editor cannot easily check for invalid links in edit mode, therefore it is best to open the page in another window and click each of the links. Once an invalid link is detected, he must go back to the edit page and remove the link.
[Back to Top]
Topic: Creating internal anchors
I want to create an internal anchor link inside my page. How do I do this?
Answer
Here is an example of how to do it in an HTML placeholder.
Step One: Create the internal anchor point
1. click inside the placeholder and select some text
2. click the 'Edit Hyperlink' icon on the Microsoft® Internet Explorer toolbar
3. under the 'Define as Internal Anchor Point' section, enter the name in the 'Name' box (e.g. name)
Step Two: Create the internal link
1. click inside the placeholder and select some text
2. click the 'Edit Hyperlink' icon on the Microsoft Internet Explorer toolbar
3. in the 'Hyperlink Address' box enter the name with a '#' sign before it (e.g. #name)
[Back to Top]
Topic: Error message about missing reference to "Microsoft.Web.UI.WebControls"
When I select "Create New Page" from the console, I get the following error:
Compiler Error Message: CS0011: Referenced class 'Microsoft.ContentManagement.WebAuthor.BaseTree' has base class or interface 'Microsoft.Web.UI.WebControls.TreeView' defined in an assembly that is not referenced. You must add a reference to assembly 'Microsoft.Web.UI.WebControls'.
Any ideas on what's wrong?
Answer
Ensure that in the assemblies section in the web.config file the following entry exists:
<add assembly="Microsoft.Web.UI.WebControls, Version=1.0.2.226, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
[Back to Top]
Topic: Error message: "'1' is not a valid identifier."
I get the following error message when I try to create a new posting based on one of my templates:
Server Error in '/TestTemplate' Application.
Parser Error
Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.
Parser Error Message: '1' is not a valid identifier.
Source Error:
Line ...: <FORM id="1" method="post" runat="server"></FORM>
Answer
The name in the form tag is the same name as your template file. You must not name your template with a number (without preceding the number with a letter).
[Back to Top]
Topic: Error message: "A potentially dangerous Request.Form value was detected from the client"
I get "A potentially dangerous Request.Form value was detected from the client" when saving a new page. What's going wrong?
Answer
The reason for this is that the Web Author posts HTML data to the server. HTML data posted to a Web server can potentially contain dangerous content. The .NET Framework 1.1 checks for this case. But the .NET framework does not know that MCMS expects the Web Author to send such content. This causes the error.
You need add the tag validateRequest="false" to your web.config. This will disable the check:
<configuration>
<system.web>
<pages validateRequest="false" />
</system.web>
</configuration>
For more details refer to the ASP.Net Web site.
If you don't like the idea to enable this for the whole web application, then you can also set this value to false in the web.config and only disable request validation on the templates that contain HtmlPlaceholderControls using the following page directive:
<%@ Page validateRequest="false" ...>
[Back to Top]
Topic: Error message: "File or assembly name <name>.dll, or one of its dependencies, was not found."
I am seeing this error message "File or assembly name <name>.dll, or one of its dependencies, was not found. (<name> is random)".
Error ID: -2147352567
Source File:
Source Method: NRSiteDeployServer
Description: File or assembly name ifdy1rnx.dll, or one of its dependencies, was not found.
What could be wrong?
Answer
Here are some things to consider:
- This error can occur if the ASPNET account doesn't have permission to write to the WinNT\Temp (system temporary) directory.
- This error can also happen if you run an MCMS application compiled for .NET framework 1.1 on .NET framework 1.0
[Back to Top]
Topic: Error message: "Invalid Mode for Update" when saving new page
When I try to save a new page, I see this error message:
Save new Page failed.
Error Details: Invalid Mode for Update. The requested action modifies the state of an object and can only be performed when the session is in 'Update' mode.
Answer
Here are some things to consider:
- Check if the template is in the root of the Web site. It should be in a separate web application.
You should not create a template project with http://localhost but with http://localhost/application
If you create a template project in the root then the web.config file and global.asax reside here: http://localhost/web.config
This will mean that this web.config will interact with the web.config in the /MCMS directory (http://localhost/MCMS/web.config)
- Ensure that the template is not named "Default.ASPX".
[Back to Top]
Topic: Error message: "Object doesn't support this property or method" when saving new posting
I have a problem creating a new page in the Web Author. After putting in the page name and clicking "OK" I get the following javascript error: "Object doesn't support this property or method" and the new page dialog window does not close.
What could cause this?
Answer
This can happen if a <FORM> tag is included in the template. ASP.NET automatically adds a <FORM> tag to ASPX pages. Pages can only contain one <FORM> tag.
Right click on the page in authoring mode and click "View Source". Search in the source code for "<FORM". If there is more than one tag, you will need to remove the extra ones.
[Back to Top]
Topic: Error message: "Specified cast is not valid" when opening a page
Error Message: "Specified cast is not valid" when opening a page in the Web Author. The page contains custom placeholder controls (e.g. DropDownPlaceholderControl).
Answer
This is a problem with the Viewstate data and a dynamically changing control tree.
When there are postbacks between different modes (which there are for a ReEdit event but not for a NewPage event), there can be issues with repopulating the viewstate. When this happens, exceptions like this can occur.
In the beta release I believe that ViewState may have been unavailable for all controls inside mode containers. When we allowed viewstate to work again, there were occasionally some issues like this. I believe this is a situation that can arise in a postback to any ASP.NET page where the control tree is significantly different from the source page for the postback, perhaps due to programmatic and conditional population of the control tree like this situation requires.
If the embedded control only needs access to the postback data itself and its viewstate is not required for your control, then you may be able to work around the problem by adding the following line:
this.controlname.EnableViewState = False
The following article explains this problem in detail:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vbcon/html/vbtskAddingControlsToWebFormsPageProgrammatically.asp
Abstract:
However, view state information about dynamically created controls can be a problem in two scenarios:
- If you insert dynamic controls between existing controls.
- If you insert controls dynamically and then reinsert them during a round trip, but with different values.
If you insert dynamic controls between existing controls, the dynamic control's view state information is inserted into the corresponding location of the view state structure. When the page is posted and the view state is loaded, the dynamic control does not yet exist; therefore, the extra information in view state does not correspond to the right control. The result is usually an error indicating an invalid cast.
[Back to Top]
Topic: Error message: "The module 'CmsAuthorizationModule' is already in the application and cannot be added again"
I get the following error message:
Parser Error Message: The module 'CmsAuthorizationModule' already in the application and cannot be added again
What might cause this problem?
Answer
This problem is being caused by a web.config located in the root of your website. You should create an MCMS application in the root of a Web site. Please either remove this web.config file or remove the duplicate keys which interact with your template application web.config file.
[Back to Top]
Topic: Error message: "The page cannot be displayed - Cannot find server or DNS Error"
When authoring my site I sometimes receive the standard Internet Explorer error page with the following message:
The page cannot be displayed
Cannot find server or DNS Error
Internet Explorer
Answer
This is a known problem with Internet Explorer when doing POST requests to a site using Windows authentication. You need to install the following hotfix on every affected authoring machine:
821814 - You Receive a "Page Cannot Be Displayed" Error Message When You Post to a Site That Requires Authentication
Note: the following newer fix implements the same fix in a different way and requires an additional registry key. Please see the "More Information" section for details:
831167 - Wininet retries POST requests with a blank header
[Back to Top]
Topic: Error message: "The user does not have sufficient right to view the page." when clicking "Edit Hyperlink"
Sometimes when I click the "Edit Hyperlink" button on the Toolbar I receive the following error message: "The user does not have sufficient right to view the page."
Answer
This has been identified as a problem in Internet Explorer.
One workaround for this is to remove anonymous access permissions from the following file in the IIS MMC:
\<templateproject>\CMS\WebAuthor\Dialogs\HLink\HLink.aspx
[Back to Top]
Topic: Error message: "The View State is invalid for this page and might be corrupted"
I get the following error message for some of my postings. These postings include a user control which stores values in a database:
"The View State is invalid for this page and might be corrupted."
Answer
This is a problem with the Viewstate data and a dynamically changing control tree.
When there are postbacks between different modes (which there are for a ReEdit event but not for a NewPage event), there can be issues with repopulating the viewstate. When this happens, exceptions like this can occur.
In the beta release I believe that ViewState may have been unavailable for all controls inside mode containers. When we allowed viewstate to work again, there were occasionally some issues like this. I believe this is a situation that can arise in a postback to any ASP.NET page where the control tree is significantly different from the source page for the postback, perhaps due to programmatic and conditional population of the control tree like this situation requires.
If the embedded control only needs access to the postback data itself and its viewstate is not required for your control, then you may be able to work around the problem by adding the following line:
this.controlname.EnableViewState = False
The following article explains this problem in detail:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vbcon/html/vbtskAddingControlsToWebFormsPageProgrammatically.asp
Abstract:
However, view state information about dynamically created controls can be a problem in two scenarios:
- If you insert dynamic controls between existing controls.
- If you insert controls dynamically and then reinsert them during a round trip, but with different values.
If you insert dynamic controls between existing controls, the dynamic control's view state information is inserted into the corresponding location of the view state structure. When the page is posted and the view state is loaded, the dynamic control does not yet exist; therefore, the extra information in view state does not correspond to the right control. The result is usually an error indicating an invalid cast.
[Back to Top]
Topic: Error message: "Type mismatch: Initialize Toolbar"
When I enter Web Author edit mode, I receive the following error message:
Error : Type mismatch: "Initialize Toolbar"
Answer
This problem is discussed in knowledge base article 811932.
[Back to Top]
Topic: Error message: "Write access denied. The user does not have sufficient rights to perform the requested action."
When our web authors throughout the company try to edit pages within MCMS, they are able to edit the page normally. However, they are unable to save any changes. Every time they try to save a page the following exception occurs:
Error: Error in Page Update using ROM
Description: Write access denied. The user does not have sufficient rights to perform the requested action.
Answer
This can happen when the user saving the page does not have rights to images or attachments embedded in one of the placeholders.
This can happen if the site way migrated from MCMS 2001 where such rights checks for resource gallery items did not exist or if the page was originally created by a user with more rights than the current user.
[Back to Top]
Topic: Error when uploading files to the resource gallery
We are not able to upload new resource gallery items to the resource gallery using Web Author or using Site Manager.
In Web Author we get the following error message: "Object reference not set to an instance of an object."
In SiteManager we get the followng error message:
Error description: (0x80020009)
Extended error: [What='The system cannot find the path specified.(3)'] [LCID='1033']
[SourceFile='javascript:void(null);']
[SourceFileLine='187'] [DebugInfo='javascript:void(null);']
[RecommendedAction=""] [Extralinfo=''] [UniqueErrorId='5001'] [Severity='5'] [Source='']
[CategoryId='0']
What can cause this problem?
Answer
The error message details indicate a problem with the path in the following registry key:
HKLM\SOFTWARE\NCompass\Resolution Content Server\Configuration\ResolutionTempFolder
This key is either pointing to a non-existing location or the permissions on this directory have been tightend.
The required permissions on the folder where this registry is pointing to are as follows:
- Administrators group (FULL)
- CMSSystem (FULL)
- Everyone (FULL)
- System (FULL)
[Back to Top]
Topic: Exception in "ConvertUtc2Local"
I'm running an MCMS Web site on two different servers. Presentation mode works fine on both boxes but on one box some actions in unpublished mode cause the following exception:
[NullReferenceException: Object reference not set to an instance of an object.]
Microsoft.ContentManagement.WebAuthor.DialogBase.ConvertUtc2Local(DateTime dtUtc) +61
Microsoft.ContentManagement.WebAuthor.StandardProperties.LoadDateTime(DateTime dtUtc, TextBox tbxDate, Calendar calendar, TextBox tbxTime) +54
Microsoft.ContentManagement.WebAuthor.StandardProperties.LoadPublishingDates() +83
Microsoft.ContentManagement.WebAuthor.StandardProperties.Page_Load(Object sender, EventArgs e) +192
System.Web.UI.Control.OnLoad(EventArgs e) +67
System.Web.UI.Control.LoadRecursive() +35
System.Web.UI.Control.LoadRecursive() +98
System.Web.UI.Control.LoadRecursive() +98
System.Web.UI.Control.LoadRecursive() +98
System.Web.UI.Page.ProcessRequestMain() +731
Answer
The reason for this problem is explained in the following KB article:
http://support.microsoft.com/?id=316112.
PRB: Session Variables Do Not Persist Between Requests After You Install Internet Explorer Security Patch MS01-055
[Back to Top]
Topic: Extreme document load time
While editing a page in the MCMS Web Author, I receive the following message in a popup:
Extreme document load time
The document is in the state of resolving links. While this is occurring the document may not be fully available for retrieval.
During this process some portions of the document may not be available. If this operation continues some items may be lost.
Do you wish to wait up to two (2) minutes for the document to complete?
Answer
This is not a message produced by MCMS but by the Ektron Placeholder control. Please contact Ektron (www.ektron.com) for details.
[Back to Top]
Topic: Forcing the download of ActiveX controls
After installing MCMS SP1, some of my Authors and Editors are no longer able to edit the pages using the Web Author. I assume this is a problem with the Microsoft ActiveX® controls. Is it possible to delete them and force a fresh download from the MCMS server?
Answer
Yes, you can force the controls to be downloaded. Follow these steps:
- Open Internet Explorer
- Click Tools and then click Internet Option
- Select the General tab
- In the Temporary Internet files section click Settings
- Click View Objects
- Delete "MCMS Html Editor" and "Microsoft MCMS Html Editor Toolbar"
- Close all Internet Explorer instances
[Back to Top]
Topic: How can I pre-select a template when creating a new page?
How can I pre-select a template when creating a new page?
Answer
You need to redirect to the following destination. This will open the Web Author with the template of your choice and the page will be saved in the channel of your choice:
WebAuthorContext.Current.GetUrlForMode(Posting,WebAuthorContextMode.AuthoringReedit)
[Back to Top]
Topic: IFRAME causes Javascript Error with Permission Denied
I've created a simple MCMS 2002 template containing an IFRAME (and the default console). When I view a posting based on this template, everything is fine until I switch to authoring mode. I then get a Javascript 'permission denied' error.
I set the visible property of the IFRAME (adding runat=server) so that it was only visible in Published mode. I no longer get the error when I switch to edit mode, but when I switch back to the live site, I still get the error (the page comes from the /NR/exeres/ cache).
Can someone explain why this error occurs, and t
he correct way to use IFRAMEs in a MCMS 2002 template without causing Javascript errors?
Answer
This is a small bug in the coding of Console.js. It causes a cross-site-scripting issue in framed sites. When switching between presentation and authoring mode, the Web Author tries to change the mode of all other frames.
This causes cross-site-scripting errors when the other frames do not belong to the same site.
This should also cause trouble in a framed site when the other frames contain content from other sites.
To solve this you have to add some code to the Console.js file located at the following location:
\Program Files\Microsoft Content Management Server\Server\IIS_CMS\WebAuthor\Client\Console.js
Change the code so that it looks like this:
function UpdateSiblingFramesInPublishedMode()
{
for (i=0; i < window.top.frames.length; i++)
{
if (window.top.frames[i] != window)
{
// refresh it with Published mode URL
try
{
window.top.frames[i].location.href =
GetUrlModePublished( window.top.frames[i].location.href );
}
catch(e)
{}
}
}
}
...
function UpdateSiblingFramesInUnpublishedMode()
{
for (i=0; i < window.top.frames.length; i++)
{
if (window.top.frames[i] != window)
{
// refresh it with Unpublished mode URL
try
{
window.top.frames[i].location.href =
GetUrlModeUnpublished( window.top.frames[i].location.href );
}
catch(e)
{}
}
}
}
[Back to Top]
Topic: Incorrect size and position of windows
In Web Author when a new window opens (e.g. Resource Manager) the positioning and size of the window causes the lower right edge of the window to be out of the screen. How can this be corrected?
Answer
To solve this this issue you need to modify some lines of code in the following file:
\Program Files\Microsoft Content Management Server\Server\IIS_CMS\WebAuthor\Client\Windows.js
The following code:
function WBC_UseDefaultSizing(pWindow)
{
var lWidth = WBC_getWindowWidth(pWindow);
var lHeight = WBC_getWindowHeight(pWindow);
...
needs to be changed to
function WBC_UseDefaultSizing(pWindow)
{
var lWidth = WBC_getWindowWidth(pWindow)-2*IDS_WIDTH_OFFSET;
var lHeight = WBC_getWindowHeight(pWindow)-2*IDS_HEIGHT_OFFSET;
...
[Back to Top]
Topic: Is it possible to pre-install the ActiveX controls for the Web Author?
A customer is restricting Microsoft ActiveX® downloads in browsers and wants to pre-install the Microsoft ActiveX controls necessary for the Web Author. How can this be done?
Answer
The customer needs to register the two classes contained in the following cab file:
c:\Program Files\Microsoft Content Management Server\Server\IIS_CMS\WebAuthor\Client\PlaceholderControlSupport\nrdhtml.cab.
Registration is done using "REGSVR32 <filename>"
If the same machines are required to author on MCMS 2001 and MCMS 2002, install the Microsoft ActiveX® controls of MCMS 2002. They are compatible with MCMS 2001.
[Back to Top]
Topic: Line Breaks in the HtmlPlaceholderControl
Is it possible to change the HtmlPlaceholderControl so that the lines are not double spaced? I just want a new line when I press enter. As it is, I have to press shift enter to get a new line.
Answer
When you press ENTER a <p> tag is inserted which means a new section is started. When you press Shift-ENTER a <BR> tag is inserted which means a line-break in a section.
If the line spacing for sections does not meet your requirements just change the margin-top and margin-bottom style attributes of the <p> tag in your style sheet.
It is not possible to change the Microsoft ActiveX® control to insert <BR> instead of <P> when pressing Enter.
If you really want to change this behavior you could create a custom placeholder control derived from the original HtmlPlaceholderControl which overrides the SavePlaceholderContent method and exchanges <p> with <br>.
[Back to Top]
Topic: Multiple Instances of the HtmlPlaceholderControl Toolbar
I experience the problem that I sometimes the have multiple instances of the Toolbar for the HtmlPlaceholderControl in the browser. How can I prevent this?
Answer
This can happen if there are hidden HtmlPlaceholderControls (e.g. hidden SPAN or DIV tags which surround the HtmlPlaceholderControl). This will still create the Tool but as the ActiveX control holding the Editor Component is not available the Toolbar cannot be bound to the placeholder control and remains orphaned on the page.
To prevent this either hide the HtmlPlaceholderControl using client side Script:
<script language="javascript">
mydiv.style.visibility='Hidden';
mydiv.style.Display='None'
</script>
or remove the HtmlPlaceholderControl using server side script by adding logic to the placeholder which prevents the HtmlPlaceholderControl from being added.
[Back to Top]
Topic: Page is refreshed when trying to save new page.
We experience problems when trying to save a new page in MCMS 2002 Web author. After closing the save new page dialog a postback to the server happens but rather than saving the page and switching to unpublished mode the page just refreshes in update mode and the placeholders show up empty. In addition the page has not been created.
What can cause this behaviour?
Answer
This can happen if the SQL server collation for the database is set to case sensitive. This is not supported with MCMS 2002. Ensure that the SQL server collation for the MCMS database is set to case-insensitive.
[Back to Top]
Topic: Placeholder content is lost when saving or doing preview
When I preview a posting or when I save a new posting, the placeholder content is gone. What can cause this?
Answer
This can happen if a <FORM> tag is included in the template. ASP.NET automatically adds a <FORM> tag to ASPX pages. Pages can only contain one <FORM> tag.
Right click on the page in authoring mode and click "View Source". Search in the source code for "<FORM". If there is more than one tag, you will need to remove the extra ones.
Beside this you also have to ensure that the placeholder controls are located between the <FORM...> and the </FORM> tag.
[Back to Top]
Topic: Problem uploading big files
I'm trying to upload a file in the resource manager. The file is a bit large (about 5 MB). When I select the file, and press ok button an error page is displayed.
Answer
Please add or modify the following section in your web.config file to control the maximum upload size and time:
<httpRuntime executionTimeout="3600"
maxRequestLength="1024000"
useFullyQualifiedRedirectUrl="false"
minFreeThreads="8"
minLocalRequestFreeThreads="4"
appRequestQueueLimit="100"/>
In this example, the values are set to 3600 seconds=1 hour and 1024000 KB=1GB.
[Back to Top]
Topic: Script error when switching to edit mode or when saving a posting.
#1: When I click on the "Switch to Edit Site" link in the console nothing happens but a script error shows up.
#2: I get a "__CMS_PostBackForm is undefined" message when trying to create a new posting in the Web Author.
What can cause this error?
Answer
There are several possible reasons for this:
-
Your Web application is missing the virtual directory "CMS". Ensure that this virtual directory exists and points to the IIS_CMS folder in the MCMS installation directory. Also ensure that it is just a virtual directory (not a web application).
-
If your template is named Default.ASPX, rename your template to a different name.
-
Ensure that the ID of the form inside the template aspx page (visisble in html view in Microsoft® Visual Studio® .NET) is not set to "default". Choose a different name.
-
Check if there is a virtual directory with the same name as your channel. Invalid Metabase entries on this virtual directory might interact with MCMS and cause this error. To troubleshoot this, rename this virtual directory to a different name and check if the console works correctly. If it does, and you need the virtual directory with the same name, check which entries are causing the problem.
-
Another reason for this can be if Whidbey and ASP.NET 2.0 are installed and the template project uses this version. MCMS 2002 is currently not compatible with ASP.NET 2.0
[Back to Top]
Topic: Setting the spell check language in Web Author
Spell checker in MCMS 2002 Web Author uses wrong language. How can I change this?
Answer
The spell checker is a component of Microsoft Word installed on the client machine. Please ensure that spell checking of this language works correct in Word. If this is ok, then check the value of the following registry key:
HKCU\Software\Microsoft\Office\10.0\Common\LanguageResources\InstallLanguage
(the version might differ)
Ensure that the correct language value is defined. Here are samples of the values for the most often used languages:
german
english
spanish
french
italian
dutch
swedish
|
|
407 (hex)
409 (hex)
40A (hex)
40C (hex)
410 (hex)
413 (hex)
41d (hex)
|
|
1031 (dec)
1033 (dec)
1034 (dec)
1036 (dec)
1040 (dec)
1043 (dec)
1053 (dec)
|
More languages can be found in KB 221435
[Back to Top]
Topic: Supported Browsers for the Web Author
Which browsers are supported by the MCMS 2002 Web Author?
Answer
Unlike MCMS 2001, there is no DHTML Version of Web Author available.
The Placeholder Controls shipped with MCMS 2002 require Microsoft Internet Explorer 5.x (also Microsoft Internet Explorer 5.01 with Windows Script 5.6) on Windows (Windows 9x and Microsoft Internet Explorer for the Mac are no longer supported).
This limitation not only belongs to the PlaceholderControls shipped with MCMS 2002. Also the dialogs are tailored for the above browser versions.
[Back to Top]
Topic: Template Gallery resources reference "/CMS/CMS/..."
When I select "create new page" in the Web Author console, I see the Template Gallery Window pop up but no images are being pulled down. The stylesheet is not being loaded and the Javascript files are not being pulled down. I viewed the source of this page and saw that there was an extra folder in the path to the resource files. The links looked like this: /CMS/CMS/WebAuthor/Client/WBC.css.
I had the same type of problem when I went into the resource gallery. What could be wrong?
Answer
The solution to this problem is that the virtual directory "CMS" in the template application is an application and not a virtual directory. You can tell the difference between the two by their appearance in the MMC. A virtual directory has a little world on top of a folder while an application has a grey box with a page in it and a green arrow.
To fix this:
- Open the IIS_Admin MMC
- Right click on the "CMS" Virtual Directory/Application item under the web root
- Click properties on the virtual Directory tab and select "remove"
- Click "OK"
[Back to Top]
Topic: Toolbar button "Edit Source" grayed out
I have this strange problem that in some (not all) of my templates when in edit mode I do not have the option to view the html source in my htmlplaceholders since the html edit source button is grayed out.
I checked that I have full formatting on the placeholder so this is not the problem what else can explain this?
Answer
This is not an option of the placeholder object but of the placeholder control object.
This option can be enabled/disabled using the "AllowHtmlSourceEditing" property of the
HtmlPlaceholderControl.
In VS.NET click on the placeholder control on your template and you will note the "AllowHtmlSourceEditing" in the behaviour section of the property windows.
[Back to Top]
Topic: Tree view refreshes without postback
If the list of resource galleries has exceeded the size of the window of the tree view control and the author has to scroll down to select and expand a tree node the following error occurs:
The resourcegallery is not expanded but the list jumps back to the first resourcegallery.
The same happens if more channels exist and a node in the hyperlink dialog needs to be expanded. The error only happens after a scroll down - not if no scroll down is required.
If the same node is expanded a second time the problem does not occur. Only for the initial page load. How can I avoid this problem?
Answer
To avoid this you need to update the treeview.htc file which is part of the IE WebControls:
treeview.htc, line 444:
...
try
{
var prevScrollTop = element.scrollTop;
var prevScrollLeft = element.scrollLeft;
// oItem.focus(); <--- this line needs to be commented out to avoid the problem.
element.scrollTop = prevScrollTop;
element.scrollLeft = prevScrollLeft;
}
catch (e)
...
[Back to Top]
Topic: Treeview broken in the Web Author
The dialog box used in the Web Author to link a piece of text to an internal link is missing the little '+' next to the channel names. This provides no means for the user to select a posting to link to. It only allows the selection of the root channel.
Answer
The resolution is to create a virtual web application named “webctrl_client” under the root of the MCMS Web site, and then map it to the “C:\Inetpub\wwwroot\webctrl_client” physical directory (this is the Default Web Site install directory). After you’ve done this, try the dialog again.
[Back to Top]
Topic: Ugly URL after postback
When I add a button to my template and click it, the URL line changes to the template instead of the nice posting URL. What's wrong?
Answer
This behavior is by design. What you can see is the true URL of the posting, which consists of a call to the template file with parameters identifying the posting. ASP.NET requires this URL to correctly process a posting. If a user enters the friendly URL in the browser the MCMS ISAPI filter silently replaces the friendly URL with the correct one. ASP.NET never knows about the MCMS internal URL, it creates postback links to the true URL.
Here is a workaround for this problem. Add the following code behind the <form...> tag in the template or add it to a User Web Control which you can add to all your templates:
<%@ Import Namespace="Microsoft.ContentManagement.Publishing" %>
<% if (WebAuthorContext.Current.Mode == WebAuthorContextMode.PresentationPublished) { %>
<SCRIPT language=javascript>
<!--
__CMS_PostbackForm.action = '<% =CmsHttpContext.Current.Posting.Url %>';
// -->
</SCRIPT>
<% } %>
[Back to Top]
Topic: Ugly URL when switching from edit to live mode
When switching from Edit to Live mode the URL in the browser is still in an ugly format. Can this be changed?
Answer
1) Add the following code part to global.asax.cs of you template project:
public void Application_PreRequestHandlerExecute(Object sender, EventArgs e)
{
//
// correct the url after switch to live
//
Posting thisPosting = CmsHttpContext.Current.Posting;
PublishingMode currentMode = CmsHttpContext.Current.Mode;
if (thisPosting != null && currentMode == PublishingMode.Published)
{
if ( Request.QueryString["NRORIGINALURL"] != null &&
Request.QueryString["NRORIGINALURL"].StartsWith("/NR/exeres") )
{
if ( !thisPosting.Url.StartsWith("/NR/exeres") )
Response.Redirect (thisPosting.Url);
}
}
}
2) Wire up this event in the global init:
this.PreRequestHandlerExecute +=
new EventHandler(this.Application_PreRequestHandlerExecute);
The complete implemetation looks like this:
namespace ...
{
///
/// Summary description for Global.
///
public class Global : System.Web.HttpApplication
{
public Global()
{
InitializeComponent();
this.PreRequestHandlerExecute +=
new EventHandler(this.Application_PreRequestHandlerExecute);
}
public void Application_PreRequestHandlerExecute(Object sender,
EventArgs e)
{
//
// correct the url after switch to live mode
//
Posting thisPosting = CmsHttpContext.Current.Posting;
PublishingMode currentMode = CmsHttpContext.Current.Mode;
if (thisPosting != null && currentMode == PublishingMode.Published)
{
if ( Request.QueryString["NRORIGINALURL"] != null &&
Request.QueryString["NRORIGINALURL"].StartsWith("/NR/exeres") )
{
Response.Redirect (thisPosting.Url);
}
}
}
...
}
}
[Back to Top]
Topic: Users not authenticated with Standard Edition
All requests to a site (MCMS 2002 Standard Edition) that is managed by MCMS and configured with windows authentication receives a 404 error. If a request is made to the application (root channel) then user will get a "Directorly listing denied" error 403.
Requests to non MCMS resources are resolving correctly, access to Site Manager is working as well as the SCA.
When doing a manual login into the Web site by accessing the Manuallogin.asp we are able to authenticate to the site and the site is working as expected.
This shows that the site is working but some part of the windows authentication is not working in the MCMS application.
What might cause the problem?
Answer
This can happen with MCMS 2002 Standard Edition if MCMS is not able to determine if a license violation has happened.
In the Standard Edition of MCMS there is a limit to the number of users that is allowed by the system and it is restricted to 15 Non Subscribers. NT/AD Groups are not allowed as members of nonsubscriber rights groups.
If MCMS is not able to identify if a member of a rights group is a user or a group you might experience the problem you have seen. Please enter SiteManager and have a look into all rights group and check if you find an entry where the type column is shown as <UNKNOWN>.
Remove all the affected entries and your site should start working again.
A known reason for the type to be <UNKNOWN> is that the domain is not accessable from the MCMS server machine (domain controller is down).
[Back to Top]
Topic: View state error when changing application pool of template application
After changing the application pool of my MCMS template application I receive an view state error. Is there any problem with doing this?
Answer
This can happen if the MCMS folders do not run in the same application pool as the Web site. See here for details about all the directories that have to run in the same applicaiton pool:
842429 - You receive a 403.18 error message when you run an MCMS application in a different application pool on IIS 6.0
[Back to Top]
Topic: Warning: "Are you sure you want to navigate away from this page?"
Clicking on a calendar control embedded in a template causes the following message: "Are you sure you want to navigate away from this page? Refreshing or leaving this page will loose all unsaved changes."
Answer
Some custom placeholder controls like the calendar control uses postbacks to the server when you click on it. This will cause this message to occur because the template assumes that you are leaving the page.
Another reason might be a client side reload being cause by (e.g.) a resize event. Some navigation controls use this to ensure that the rendering is done correct on the current window size.
For such situations you can use EnableLeaveAuthoringWarning = "false", a property of the console tag.
[Back to Top]
The information contained in this document represents the current view of
Microsoft Corporation on the issues discussed as of the date of publication.
Because Microsoft must respond to changing market conditions, it should not be
interpreted to be a commitment on the part of Microsoft, and Microsoft cannot
guarantee the accuracy of any information presented after the date of
publication.
This White Paper is for informational purposes only. MICROSOFT MAKES NO
WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS
DOCUMENT.
Complying with all applicable copyright laws is the responsibility of the user.
Without limiting the rights under copyright, no part of this document may be
reproduced, stored in or introduced into a retrieval system, or transmitted in
any form or by any means (electronic, mechanical, photocopying, recording, or
otherwise), or for any purpose, without the express written permission of
Microsoft Corporation.
Microsoft may have patents, patent applications, trademarks, copyrights, or
other intellectual property rights covering subject matter in this document.
Except as expressly provided in any written license agreement from Microsoft,
the furnishing of this document does not give you any license to these patents,
trademarks, copyrights, or other intellectual property.
© 2004 Microsoft Corporation. All rights reserved.
Microsoft, ActiveX, Visual Studio, Windows, and Windows Server are either
registered trademarks or trademarks of Microsoft Corporation in the United
States and/or other countries.
The names of actual companies and products mentioned herein may be the
trademarks of their respective owners.
| © 2004 Microsoft Corporation. All rights
reserved. |
