Closed (won't fix)
Project:
TinyMCE
Version:
5.x-1.x-dev
Component:
User interface
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
6 Nov 2007 at 18:53 UTC
Updated:
3 Feb 2013 at 19:50 UTC
Hello! I love the module, it is really helping out our website. I was wondering if there is a way to change the default size of the text box once TinyMCE is enabled. Right now our body box is very large and we would like to reduce the size. Thank you
Comments
Comment #1
kreynen commentedCan you be a little more specific about what "default size" means. Are you trying to change the size of textboxes (measured in columns and rows) or the amount of space the textbox + TinyMCE takes up on the page? Would reducing the number of buttons enabled (and thus the number of rows TinyMCE uses) solve the problem? Is this for a default content type like story or a new content type created with CCK?
Comment #2
MikeMoirano commentedSorry about that, I am talking about the amount of space the textbox+tinyMCE takes up on the page. I am not talking about the bar with the buttons provided by tinyMCE. This is for the content "submissions" which I believe we created through CCK. I am sorry I am pretty new to this whole thing. Thanks for your help.
Comment #3
kreynen commentedCurrently TinyMCE is added to an existing textbox and doesn't add/remove rows when it is enabled/disabled. You can change the number of rows in that field for that content type, but that will change the size for both the enabled and disabled states.
Comment #4
seanburlington commentedHi,
I came across this issue too
I added this to my template.php file
it looks for the body textarea and resizes it
This will affect both plain and richtext view (which is what I wanted anyway)
NB - uncomment the print statement if debugging other textareas to see the names available.
Sean Burlington
www.practicalweb.co.uk
London
Comment #5
pomliane commentedThis version of TinyMCE is not supported anymore. The issue is closed for this reason.
Please upgrade to a supported version and feel free to reopen the issue on the new version if applicable.
This issue has been automagically closed by a script.