Greetings,
I'm trying to set the height of the bottom toolbar so that it is only the thickness of the default buttons at the bottom. Something like this:
___________________
Design HTML Preview
___________________
However, even when there are no modules declared and the Module Manager button is removed from the editor, I still get something like this:
______________________________________________________________
Design HTML Preview
_______________________________________________________________
What can be done to correct this??
Thanks!
9 Answers, 1 is accepted
0
Hi John,
Please, make sure that you are using XHTML doctype, for example:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
as well as that some global css class is not screwing the design of the bottom RadEditor zone.
If you are unable to solve the problem, please open a support ticket and send a sample working project that demonstrates the problem. I will examine it and once I am able to reproduce the issue, I will provide a solution.
Best regards,
Rumen
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
Please, make sure that you are using XHTML doctype, for example:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
as well as that some global css class is not screwing the design of the bottom RadEditor zone.
If you are unable to solve the problem, please open a support ticket and send a sample working project that demonstrates the problem. I will examine it and once I am able to reproduce the issue, I will provide a solution.
Best regards,
Rumen
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
0
John
Top achievements
Rank 1
Rank 1
answered on 24 Jul 2009, 12:07 PM
Hello Rumen,
Thanks for the feed-back on this. The page I'm working with has no declaration such as the one you prescribed:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
If I put that in the file I get the following warning and the page will not display at all:
Warning: ASP.NET runtime error: Only Content controls are allowed directly in a content page that contains Content controls.
If this line is normally required, is there some work around I can perform in the ToolsFile.xml since I'm using this to create the editor?
Thanks!
Thanks for the feed-back on this. The page I'm working with has no declaration such as the one you prescribed:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
If I put that in the file I get the following warning and the page will not display at all:
Warning: ASP.NET runtime error: Only Content controls are allowed directly in a content page that contains Content controls.
If this line is normally required, is there some work around I can perform in the ToolsFile.xml since I'm using this to create the editor?
Thanks!
0
Hi John,
The DOCTYPE declaration must be placed on top of your rendered page. That is, if you are using master pages, for example, you need to add the declaration to your master page, above the <html> tag.
In case you are not sure what to do, please create a default page with Visual Studio, as it has a doctype declaration by default - which will show you the correct place for adding the declaration.
All the best,
Tervel
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
The DOCTYPE declaration must be placed on top of your rendered page. That is, if you are using master pages, for example, you need to add the declaration to your master page, above the <html> tag.
In case you are not sure what to do, please create a default page with Visual Studio, as it has a doctype declaration by default - which will show you the correct place for adding the declaration.
All the best,
Tervel
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
0
John
Top achievements
Rank 1
Rank 1
answered on 04 Aug 2009, 03:16 PM
Hello Tervel,
I was wrong when I implied we don't already have the DOCTYPE on the master page. I was thinking it needed to be on the control or the control's parent. However, you can see from the 'source' lines below that the master page is setup correctly:
I was wrong when I implied we don't already have the DOCTYPE on the master page. I was thinking it needed to be on the control or the control's parent. However, you can see from the 'source' lines below that the master page is setup correctly:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html>
<head>
<title>
OUR TITLE HERE
</title>
...
...
</html>
Any ideas now why the statistics portion of the editor is not working properly. I took the button completely off the toolbar but the default height of the editor's bottom section appears to be fully expanded by default.
Thanks in advance for the help!
0
Hi John,
Ok, then let us go back to your original post and re-examine it.
Here is what you wrote:
However, even when there are no modules declared and the Module Manager button is removed from the editor, I still get something like this:
My observations:
1. Not declaring any module does not mean there are no modules. My default 4 editor modules are rendered even if they are not specified explicitly.
2. Not having the ModuleManager tool has no effect on the modules behavior.
Conclusion:
In our original answer, it somehow slipped under the radar that perhaps you in fact did not remove the modules and they are still there. Then, the discussion got diverted into whether DOCTYPE is set correctly or not - which is not related to the original problem.
Hence, to remove the modules, the easiest way to do so is declaratively in your RadEditor markup like this:
Regards,
Tervel
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
Ok, then let us go back to your original post and re-examine it.
Here is what you wrote:
However, even when there are no modules declared and the Module Manager button is removed from the editor, I still get something like this:
My observations:
1. Not declaring any module does not mean there are no modules. My default 4 editor modules are rendered even if they are not specified explicitly.
2. Not having the ModuleManager tool has no effect on the modules behavior.
Conclusion:
In our original answer, it somehow slipped under the radar that perhaps you in fact did not remove the modules and they are still there. Then, the discussion got diverted into whether DOCTYPE is set correctly or not - which is not related to the original problem.
Hence, to remove the modules, the easiest way to do so is declaratively in your RadEditor markup like this:
| <telerik:RadEditor ID="RadEditor1" runat="server"> |
| <Modules> |
| <telerik:EditorModule Visible="false" /> |
| </Modules> |
| </telerik:RadEditor> |
Regards,
Tervel
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
0
John
Top achievements
Rank 1
Rank 1
answered on 07 Aug 2009, 08:12 PM
Tervel,
Nope, I wish I could say this was the ticket but it is not.
After fooling with this sooooo much, I can say confidently that the bottom portion of the editor responds to height settings of itself, tables, divisions, columns. You name it, I've seen that thing expand fully and contract to normal over and over.
However, the problem I'm experiencing is that if I get the bottom looking right, some other aspect of the page doesn't like the height setting.
John
Nope, I wish I could say this was the ticket but it is not.
After fooling with this sooooo much, I can say confidently that the bottom portion of the editor responds to height settings of itself, tables, divisions, columns. You name it, I've seen that thing expand fully and contract to normal over and over.
However, the problem I'm experiencing is that if I get the bottom looking right, some other aspect of the page doesn't like the height setting.
John
0
Hi John,
Could you please open a support ticket and send a sample working project along with screenshots which demonstrate the problem? This will help us to reproduce the problem on our side and provide a solution.
Please, also check you stylesheet for global classes for TABLE element. These styles could spoil the design of RadEditor too.
All the best,
Rumen
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
Could you please open a support ticket and send a sample working project along with screenshots which demonstrate the problem? This will help us to reproduce the problem on our side and provide a solution.
Please, also check you stylesheet for global classes for TABLE element. These styles could spoil the design of RadEditor too.
All the best,
Rumen
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
0
John
Top achievements
Rank 1
Rank 1
answered on 10 Aug 2009, 01:32 PM
This would be a first for me to open a support ticket. I'm not sure we have such support. Is there an easy way for you to tell if I can open a ticket?
Thanks
Thanks
0
Hi John,
You can open a support ticket from the Support Tickets link under your Client.net account.
Best regards,
Rumen
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
You can open a support ticket from the Support Tickets link under your Client.net account.
Best regards,
Rumen
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.