Posted 1 year ago #
I have found the bug, to solve it just remove or disable the following lines in file tiny_mce.js，it will work on safari 3, but i'm not sure if it can work on Safari 2.
4025: if (tinyMCE.isSafari && this.formElement)
4026: this.formElement.innerText = htm;
Posted 1 year ago #
I have those exact two lines (4025 & 4026) in my file... Am I supposed to be changing something?
Posted 1 year ago #
Splendid! I found the lines a couple of lines later in the file (I'm running 2.3.2), but I just commented them out and now the problem's gone. Thanks!
PS: @Oseary, yes, like meetnet21 says, just remove them or disable them. I commented them out, but just plain deleting them will work.
Posted 1 year ago #
I can ALSO verify that the "hack" works!! YESSSS! Thaaank you @meetnet21.
We can consider this FINALLY closed. But will it be fixed in the next version? :-)
Posted 1 year ago #
This seems to be working for me as well.
I am curious what exactly these lines of code do, or in other words what functionality are we disabling by commenting these out?
Posted 1 year ago #
Yes indeed that did the trick. Very pleased. Thank you!!!
If someone does actually figure out what exactly was disabled by this action it would be very nice to know.
Anywho. Thank you
Posted 1 year ago #
Hi,
I'm still seeing the same problem even after removing the 2 lines of code from the tiny_mce.js file as suggested above.
I'm using Wordpress 2.3.2 and Safari 3.04
Any other ideas? This is driving me crazy!
Posted 1 year ago #
Many thanks, meetnet21. It worked fine for me too.
FYI, in WordPress 2.3.2 those statements are on lines 3950 and 3951. And for those who may not know, the file is found at /wp-includes/js/tinymce/tiny_mce.js.
I hate modifying core files, but it sure beats having editors using Safari messing up every post they touch if I forget to turn off the visual editor for them.
Posted 1 year ago #
Okay
Am I crazy??? I've been having the same problems, then magically it was working all this week until today. Back to no paragraph breaks. Anyone else notice this strange occurrence? I didn't do anything different and it was working, now today it's not.
Grrrrr
Also, I am a newbie - I just use wordpress.com to post and am not running wordpress on my computer, so I cannot edit these files...
Posted 1 year ago #
The hack worked for me, too, but now the shortcut tags menu is gone and I no longer have the ability to format text or the page. So, I decided to put the deleted 2 lines of code back into the page. But the missing menu still does not return, even when I have "Visual" turned on my profile.
I am getting so aggravated with WP right now. I tried FCKedit in lieu of TinyMCE, but it has a big problem with uploading images and is just as frustrating when it comes to being able to manage images.
I'd rather go back to TinyMCE with the hack but I do need the menu bars, because this for the guess bloggers who will be inserting images.
If someone could help me with this, I would be really greatful.
Thanks.
Posted 1 year ago #
Changing the code didn't work for me either, but I began using Fluid as a workaround. It basically creates an app for a single website and works fine with the editor. So I don't quite feel like I'm abandoning Safari so much as just launching a dedicated admin app... I wrote briefly about it this morning here. This should also work for anyone on wordpress.com, just set the Fluid destination to your admin page.
Posted 1 year ago #
If by "bug" we mean that, when using safari and WP 2.3.3, that WP strips all paragraph returns out of either the "visual" or "code" panels when posting, then yes, I can replicate the problem. Commenting out the code, as suggested above, does not fix the problem.
To add insult to injury, if I copy text from MS Word to Safari, Safari will faithfully place all RTF formatting into the post field. Thereby killing the theme with arbitrary text formatting code. I file it under "thanks for nothing."
I don't have either problem when using camino. I've advise my client to switch to camino but safari support would be nice, of course.
« Previous 1 2
This topic has been closed to new replies.
