Posted 2 years ago #
The text area become very narrow when i tried to edit post from front end.
I disabled the Rich text editor:"WYSIWYG", then it became ok(match with my theme's width). But i need to use the rich text editor.
Any fix?
I'm running WP 2.9.1
ront end editor 1.7
my site http://www.engineer2u.com
Try version 1.7.1.
Posted 2 years ago #
Tried upgrading to 1.7.1
Still same problem, the text area width is very narrow, squeezing my text.
It's not the theme, i used WP default theme also same problem.
Please help.
I'm afraid I won't be able to help unless I see for myself. This means you would have to make an admin user for me, on your site.
Posted 2 years ago #
I'm experiencing the same thing (using the Twenty Ten theme on trunk). I'll try to catch you on IRC this week and PM you a login to a test site.
Posted 2 years ago #
I'm using the last development version and I get the same problem... the width of the editor is 179px
Posted 2 years ago #
I've also noticed in the development version that the Font-type is written as Font-family
Posted 2 years ago #
I can give you admin access if you like
Ok. My email is scribu@gmail.com
Posted 2 years ago #
Hmm it works fine now??/ maybe it was my theme or sumfing? but it's very hard to then select the image and apply an alignment to it
Posted 2 years ago #
same problem for me... area VERY narrow with Internet explorer 8, ok with chrome.
tried 1.7.1 and 1.8a, same problem
I can't believe I didn't ask what browsers people were using.
Thanks, ernexto.
So, can anyone else confirm that it's a problem with Internet Explorer only?
Posted 2 years ago #
Yup, IE8 is making mine narrow too.
Ok, I'll do some testing with IE8 when I have the time.
Posted 2 years ago #
Hey Scribu, I've got the same problem with Safari. I've also tried it with various themes including the default. Can give you admin access if you want.
This should be fixed in the development version (1.8a2).
Posted 2 years ago #
The "development version" that is available at downloads.wordpress is only 1.7.2, not 1.8a2. If you have fixed this in 1.8a2, maybe you should take the fix back to 1.7.3 as stable. It is a devastating bug.
The narrow WYSIWYG editor column problem occurs, in FEE 1.7.2, on FF, Opera, Chrome, on sites with very different setups and themes, both live (Linux) and locally served (Windows). It is fairly new (a few weeks?), doesn't seem connected with any plugin change, and occurs with all other plugins deactivated.
It occurs regardless of FEE configuration -- even if only checked "edit post content" (which avoids your multiple-id error -- which really should be corrected, please).
For some reason FEE inserts into some divs completely unnecessary inline styles of width:nnn, where nnn doesn't make any obvious sense, but is much less than full (and differs for me on different sites). By "completely unnecessary", I mean that if I remove them (using FireBug magic), the display becomes correct.
Let's get this fixed -- I'll start reading code now.
Kim Kirkpatrick
Version 1.7.2 is the former 1.8a2 dev version (I rolled it back to make it a minor release).
So upgrade to version 1.7.2.
Then, disable the WYSIWYG editor to make debugging easier.
Is the textarea still narrow?
If so, is the X (cancel) button red or not?
If it's not, are you getting any errors in Firebug?
Finally, are you using any other plugin of mine (including WP-PageNavi or WP-UserOnline)?
For some reason FEE inserts into some divs completely unnecessary inline styles of width:nnn, where nnn doesn't make any obvious sense, but is much less than full (and differs for me on different sites). By "completely unnecessary", I mean that if I remove them (using FireBug magic), the display becomes correct.
That's done by nicEdit (don't ask me why).
It occurs regardless of FEE configuration -- even if only checked "edit post content" (which avoids your multiple-id error -- which really should be corrected, please).
It's the first I've heard of the "multiple-id error". Please open a new topic with further details.
Posted 2 years ago #
Yes, I'm using 1.7.2. Without WYSIWYG, textarea is narrow. The X is red. I have disabled ALL plugins except FEE.
Evidently something is cached or saved in WordPress that causes this. Here's the complicated story.
Those inline width styles which are inserted by nicEdit create the problem. They are calculated at lines 323 and 419 of nicedit.dev.js, using the expression
parseInt(e.getStyle('width')) || e.clientWidth
For some reason the width style retrieved from the element e is wrong.
If the parseInt expression is replaced by, say, 400 in both places (ie 400 || e.clientWidth), the width of the resulting editor is 400px.
But, as I said, these width stylings are unnecessary; the editor displays correctly without them. So in desperation I forced the editor to display correctly by getting rid of all width style settings that involve these calculated values -- commented out width stylings at lines 323, 426, 429, 592, 1422. This makes the editor full width (this works in the several themes I've tried, one and two column, fixed and flex). And the non-WYSIWYG editor is full width, too.
Here's the mystery. On one of my sites, after doing this, I reverted to the original nicedit.js, and the display remained corrected! (On all browsers -- this is not a browser cache problem.) But I haven't been able to replicate this healing on other sites. So whatever stored data that got changed in one system by temporarily correcting the display, didn't get changed in others.
So on those other sites, I'm using the brute-force correction of the modified niceditor.js. I don't like it, but whatever. Perhaps eventually that mystery healing will occur.
The problem with older versions of FEE was that front-end-editor/editor/editor.css wasn't loaded. But if you say the X button is red, that means it's now loaded.
So, for sites where the textarea is narrow, check with Firebug if there's a width: 100% CSS rule applied to it or not.
Posted 2 years ago #
i confirm that this nasty bug is still present in v. 1.7.2 and with internet explorer! :-(
it's ok in firefox and chrome...
checked with firebug and the width: 100% css rule (!important) is present!
Posted 2 years ago #
Posted 2 years ago #
Here is what I've come up with, attempting to get FEE to work with IE6, 7, and 8, Firefox, Chrome, Safari, and Opera (on Windows; no idea about Mac or Linux browsers).
1) IE 6, 7, 8 seem to require the following surgery on nicedit.js: in lines 323 and 419 (of the nicedit.dev.js file), I changed
(parseInt(e.getStyle('width')) || e.clientWidth)
to
(e.clientWidth || parseInt(e.getStyle('width')))
I found this suggestion on the nicedit forum -- others have had the same problem with nicEdit on IE, and not just within WordPress.
(Note that this "||" is the rather unusual "assignment or", not a logical or: If the first value exists/is "true", that value is returned, otherwise the second value is.)
This fix seems quite necessary for all IE's -- I see the problem, and the success of this fix, on several quite different sites using a number of different themes, including classic and default. Fortunately, I haven't seen any negative effect due to it.
2) Because width is not inherited, it may be necessary that the enclosing div be given a width explicitly in the css. But not always -- for example, not in the default theme.
3) And several browsers (IE and Opera are the fussiest) don't like widths in % or auto or inherit. Only absolute units (px, em ...) seem to work for all browsers.
This is a flakey problem. It is real, but not universal. It is not a simple WordPress plugin interaction, since it occurs even with all other plugins deactivated (though some may have left traces in database's wp_options -- perhaps that is where the problem is, and why it sometimes seems to appear/disappear spontaneously). And it occurs outside WordPress (see the nicedit forum), so it's not just a plugin interaction.
Each of the "cures" mentioned above is quite repeatable within a specific situation (site, theme, browser) -- that is, if I remove the fix, the problem returns, and goes away again when re-fixed. But, as I said, they are not all necessary for all setups -- except perhaps for the first fix.
Feedback?
Kim Kirkpatrick
Wow, thanks for the in-depth research, Kim. :)
I've included solution 1): [215091]
For testing, grab the development version in about 15 minutes.
Posted 2 years ago #
I've included solution 1): [215091]
For testing, grab the development version in about 15 minutes.
I have this version (1.7.2) and the problem of narrow edit window in IE8 still exists.
The development version is 1.8a4.
Posted 2 years ago #
I just downloaded the development version, but I'm still having the problem in IE8.
Should that be the case? Seems from what I read above the development version should resolve the issue.
It's working fine for me in IE 8. It's probably an issue with your theme.
See if it happens with the default WP theme.
Posted 2 years ago #
I can only explain my incompetence by the hour of the night that I was working.
Somehow, I was still on 1.7.2. Thought I'd upgraded. Who knows...
Anyway, yes, it works fine. Thanks to everyone who contributed to getting this fix done.
Posted 1 year ago #
Scribu
Having problems with the editor width issue in FF, Chrome, Safari, I am using Thematic theme. I read through this post and it all makes sense even checked the nicEdit.js file but the fix is in the latest version. I tried the development version and it fixed the width but the WYSIWIG editor bar disappears. Any idea what could be going on? Kinda stuck.
Thanks
This topic has been closed to new replies.
