-
MODX Staff
- 10,725 Posts
Dimmy, this sounds like it might be another language file issue with FCK. Perhaps your instance of IE is configured to display in a language that is not included with the FCK plugin? Just a thought...
I deleted all the files from my server and copyed the new file on it and now it works...
weard overwriting them should have the same effect.
this is not cool if this needs to be done at all my site to get it to work.
anyway great work and will start bugtraking this puppy
Greets
I took another look at your test site and, yeah, it appears to be working fine now in IE. However, I did notice that the initial launch of the editor window still chops off part of the FCKeditor toobar. Resizing the window to make it a bit bigger did the trick. By default, FCK is set to display at 100% size. It’s not set at any particular width. So, my best guess is that this is a little bug with FCK itself and not with our code. Try setting the width of the popup window to around 575 or higher. 650 worked quite well for me. You can do this by editing the output.js file in the /assets/modules/quickedit directory. You’ll see a line for the settings variable. The width is set for 525 by default. Another thing I’ll look into is breaking up the editor buttons into more logical sections that split up a bit better. Might not be necessary though if we just keep the width higher than 525.
Jeff Whitfield
"I like my coffee hot and strong, like I like my women, hot and strong... with a spoon in them."
On another note, the width issue affects other editors as well. I tested the TinyMCE plugin with QuickEdit and, yeah, at a width of 525 some of the editor options are cut off. Definitely need to keep the width higher than 575. I’d say make it 660 to be on the safe side.
Jeff Whitfield
"I like my coffee hot and strong, like I like my women, hot and strong... with a spoon in them."
Quote from: aNoble at Aug 23, 2005, 02:25 PM
I considered bumping up the width but you end up getting some crazy wide textboxes, checkbokes, radios etc. I might be abel to work around this with CSS though.
Do you think we need the width bumped up even with the ability to resize the window? I’ll see if I can find a way to have the best of both worlds though it may be possible.
Well...layout issues with textboxes and stuff are probably easier to deal with. Granted, you’re right about resizing the window...but I thinking that some users might find this to be a nuisance. Setting the width to 660 is a fair tradeoff and will at least allow just about any editor plenty of room to show all the editor buttons. I’ll likely still look into chopping the button sections a bit just to be safe.
Jeff Whitfield
"I like my coffee hot and strong, like I like my women, hot and strong... with a spoon in them."
Quote from: aNoble at Aug 23, 2005, 02:39 PM
If I can’t find a way to bump up the width for richtext editors and keep it narrower for others then I’ll set the default width to 660px. Thanks for the advice.
Quick and dirty solution! Try this:
Open up custom_config.js in the /assets/plugins/fckeditor directory. One line 47, change this line from:
['Style','FontFormat','FontName','FontSize'],
To this:
['Style'],['FontFormat'],['FontName'],['FontSize'],
This forces the dropdowns to act as separate blocks, thus allowing them to wrap as necessary. Works well!
I’ll do the same with TinyMCE and Xinha during testing to make sure they wrap properly. No need to change the default width.
Jeff Whitfield
"I like my coffee hot and strong, like I like my women, hot and strong... with a spoon in them."
