Prometheus Rad Editor Issues

[Sir]

1)  How do I make the text editor background white?

2)  The toolbars are all blown apart
The dropdown arrows for some of the controls are underneath the actual image.
The previous version did not have this issue.

3)  How do I get rid of the bunch of wasted space underneath the preview button.  It's empty space that is better served for the actual editor window.
The previous version did not have this space/issue.

The only real way to describe the issues is if you let me email you a jpg of what I'm looking at.
This is for internal company intranet app on IE 6.0.29

Thanks,
RjD

[Clint MacDonald]

1) by default the editor grabs the page background color.  Therefore you need to create a second css file that describes the style you want the editor to show and then use the cssFiles property to point the editor at the newly created file
2) The drop down arrows in the wrong place can happen as the new toolsbars are infact wider than the RadControls version, this means you need to leave more room for them and therefore they also now wrap.  If you can, make your editor a little wider to see if this resolves this issue.
3) You will have to create your own custom ToolsFile.xml....and play with the module section:  The NodeInspector, HTMLInspector, and XHTMLInspectors can be set to "false" and they will then be hidden.

 <modules>

  <module name="RadEditorStatistics" dockingZone="Bottom" enabled="true" visible="true"/>  

  <module name="RadEditorDomInspector" dockingZone="Module" enabled="true" visible="true" />

  <module name="RadEditorNodeInspector" dockingZone="Module" enabled="true" visible="true" dockable="false" />

  <module name="RadEditorHtmlInspector" dockingZone="Module" enabled="true" visible="false" />

  <module name="RadEditorXhtmlValidator" dockingZone="Module" enabled="true" visible="true" dockable="true" />

 </modules>

Hope this helps....

[Sir]

Thank you for attempting to answer based on so little info!

1)  Respectfully request you make background color a simple property
Last 2 versions this has been an issue.  Now I have to hack out your CSS to fix the background color (again).

2)  Please click on the link below to look at a screenshot - it clearly shows what is wrong with the toolbars - they are not wrapping or anything like that, the overlay images are sitting underneath instead of on top of their respective images.
Prometheus Toolbar Issue

3)  The custom ToolsFile.xml you suggested did the trick here.
So by the way, how do I remove the "resize radeditor" icon that is on the far right of the preview icon?

Thanks again,
RjD

[Clint MacDonald]

no problem, and I do not work for Telerik but am a dev myself.  I have just run across these issues before and noone had responded for 3 days, so I gave you some ideas.......
1) The background color thing is VERY annoying and I wish there was a way to tell the editor to IGNORE the page css and just set a background color....you will see the background color is a property....but I have never had it actually do anything.
2) That is wacky.....I might suggest replacing your radcontrols directory....or checking to see you do not have a css style on the page setting image properties (like margins, padding, or margins)
3) I am glad....but I do not know how to solve the resize issue....hopefully Telerik may anser this one....?

Thanks
Clint

[Mike]

The background color issue is probably the most annoying thing ever!

I have tried to implement the secondary .css file but what is the controls name for the text area?

[Clint MacDonald]

Your separate css file should be its own entity with the specifications of the area where the editor content will be displayed.  So if you set the "body" area of the css with the background desired it should be the way you want it.

[Mike]

Hi Clint,

Thanks for the response. Yes I created a seperate .css file called editor.css and put it in the same folder and then in the Editor tag I set the ContentAreaCssFile="editor.css" but my control is still rendering with the background of the page which makes it completely useless.

Am I not setting this up correctly? I really wish Telerik would have at least included a sample of how to do this, it seems like a very common thing that people would want to do.

I still can't belive they ditched the "Save" and "Cancel" buttons. They provide a snippet on how to include them but they don't include the full tools.xml just a small portion so you have to completely rebuild it.

I appreciate your help,

Mike

[Tervel]

Hi all,

In fact there is a sample called Setting Content Area Defaults which deals with this functionality quite extensively, explaining how to use both CssFiles property as well as the ContentAreaCssFile property. Please note the use of the !important css attribute when setting a background-color.

The sample can be found in the editor online demos:
http://www.telerik.com/demos/aspnet/prometheus/Editor/Examples/SettingContentAreaDefaults/DefaultCS.aspx


Regards,
Tervel
the Telerik team

Instantly find answers to your questions at the new Telerik Support Center

[Clint MacDonald]

Well...it would be nice if the property descriptions are filled in so in the property window (at the bottom) there is a description when highlighting the property.
Just my comments

[Paul Wood]

Did anyone ever get to the bottom of the reason why Sir's toolbars where blowing apart? Exactly the same is happening for me in IE6 and I'm not sure why. The only image style I have in my global CSS is img { border:0; } which doesn't cause this as far as I can see.

[Rumen]

Hi Paul,

Please, make sure that you are using the default VS2005 page DOCTYPE

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

as well as that you have not some global style for UL and LI elements (not for IMG) which can destroy the toolbar appearance.

If you are unable to solve the problem, please open a support ticket and send a sample working project (along with your stylesheet and all needed files) that demonstrates the problem. Once we are able to reproduce the problem on our end, we will do our best to provide a solution soon.


Best regards,
Rumen
the Telerik team

Instantly find answers to your questions at the new Telerik Support Center

[Paul Wood]

Having issues with posting

[Paul Wood]

In creating a sample application to show you guys the bug, I was able to narrow it down to its simplest form and can tell you that it happens under these circumstances:

• IE6
• Use a master page
• Editor skin is Outlook

Then you'll see exactly what we're seeing.

[Rumen]

Hi Paul,

I tried to reproduce the problem following the provided instructions, but to no avail. You can see my test in the attached video. Am I missing something?

In addition, I have also attached a sample project which you can test. Is it possible to modify it and send me back (using the attachment functionality of the support ticketing system) so that I can reproduce the problem on my end. Please, also include a screenshot of the problem.


Kind regards,
Rumen
the Telerik team

Instantly find answers to your questions at the new Telerik Support Center

[Paul Wood]

Add
<?xml version="1.0" encoding="utf-8"?>
to the top of the master page (above the DOCTYPE) and it will happen for you.

[Martin]

Hello Paul Wood,

The <?xml?> tag before the DOCTYPE of the page is called xml prolog and has been widely used in the near past by IE6 developers to trigger quirks mode without removing the doctype, or declaring non-standards compliance DTDs. This bug was later fixed in IE7, and that is why you experience skin problems under IE6.

RadControls for ASP.NET AJAX are designed, developed and intended to work under standards-compliance mode (in order to make use of all browser, css, javascript, etc. improvements that were introduced with xhtml 1.0 and xhtml 1.1). By putting the xml prolog before the DOCTPE, you actually tell your page to be in standards-compliance mode, but instruct the browser to render it in quirks mode, and this is the reason for the problems.

We are sorry, but we do not provide controls that work in quirks or HTML 4 modes.

My advice is to try pure xhtml mode, and you will be fascinated by the tons of new possibilities for development.

Sincerely yours,
Martin Ivanov
the Telerik team

Instantly find answers to your questions at the new Telerik Support Center

[Paul Wood]

Thanks Martin, I'd forgotten about the XML prolog's effect in IE6. It was just unusual to me that the other skins didn't have the same issue.