I'v got an editor on a pblic page and need to get the entered value in codebehind.
In CMS 5 we used:
string body = "";SetValuesForPropertyControls(myHtmlEditor);body = myHtmlEditor.PropertyValue as string;
But SetValuesForPropertyControls doesn't seem to exist in CMS 6, what is the soulution there?
Also have I noticed that after installing IE9 the buttons in the Editor doesn't work, when I have the editor on a page, it still works in EPi.If I switch to compability mode it works. Any ideas?
SetValuesForPropertyControls still exists on PageBase. Perhaps your inside a user control or have a page that does not inherit from a PageBase-derived class?
Yes we have the editor on a usercontrol.
So, just cast the page to a PageBase and call the method ((PageBase)Page).SetValuesForPropertyControl([some control])
Thanx that worked fine, had a validation issue as well but that was solved with setting the requestValidationMode to 2.0 we are currently running in .NET 4.0Any ideas on the IE9 issue or is it something that will be solved in R2?
We have not tested the CMS 5 editor in other than IE7Legacy mode as far as I know. I'd suggest that you either set the page to legacy mode or change editor as it's unlikely that we spend a lot of time fixing the CMS 5 editor for site usage. EPiServer CMS 6 R2 comes with a pretty new version of TinyMCE which is tested in IE9/IE8 document mode.
Did you mean the CMS 6 or 5 editor, because the issue we have is with the editor in CMS 6?
There are two editors in EPiServer CMS 6: TinyMCE and the (legacy) editor called "EPiServer CMS 5 editor". If you have upgraded a CMS 5 site without changing configuration you are probably running the CMS 5 editor. We recommend people to "upgrade" to the TinyMCE editor if possible since this produces more valid output and works with a log more browsers. If this is not an option I would set the IE7legacy tag (that's what we do in the CMS editor UI).
No its a clean install of CMS 6 and we are using TinyMCE
Ok. The TinyMCE version that exists in EPiServer CMS 6 is not fully IE9 compatible. The version in CMS 6 R2 is though so you have three options here:
Thanx for the tips. The site isn't going live until this summer so we where planing to update to R2 before that. But good to know that it will work then.