Uploaded version 1.4.1 of Tinymce.

Wanderer,

Different versions of OS X and different versions of Safari behave differently. I only use the latest versions of both (currently, 10.4.9 and Safari 2.0.4), and under these versions, with no Safari hacks or add-ons, tinymce is totally disabled in Safari. So if you are using other versions or have modified your Safari install in some way, it could be that you would see part of tinymce, which I am not seeing at all. But just to let you know, I did test this on multiple OS X machines, some with different OS and Safari versions, and Safari didn't show tinymce at all on any of the machines I tested.

While this may be a moot point in your case, as you mention it is "overkill" for your needs, this dicussion may be relevant for those who come to this forum after us seeking help in Safari. From my standpoint, tinymce is quite nice except for the fact Japanese doesn't work. I don't like the fact it doesn't work at all in Safari, but at least (in my experience) it is smart enough to disable itself in Safari. I really can't be to upset about the lack of Safari support since I've yet to see a formatter like tinymce that works in Safari!

Wanderer,

Very curious indeed as to why you can see tinymce and I cannot. Hmmm.

Well, what I can say is that I actually like FCKeditor better, with the lone exception that FCKeditor doesn't hide itself in Safari but instead locks you totally out of editing anything! To me, that is unacceptable; whereas, tinymce at least will let Safari users enter comments. And Japanese works in FCKeditor too, whereas it doesn't in tinymce.

So if FCKeditor can be fixed to either WORK in Safari or AUTO-DISABLE itself in Safari, I would be very happy indeed!

MySchizoBuddy,

Thanks for the reply.

I just went to the FCKeditor DEMO page and tried all 4 samples. In every case, the toolbar does not appear at all in Safari, and although I can see the field, I cannot type text in the field. So it would seem that FCKeditor simply is not compatible with Safari. That's fine, but there should be some way for it to disable itself automatically. Possible?

MySchizoBuddy,

Thank you for the reply.

I see that you are referring to this webkit. From what I read, webkit is basically part of Safari. And you are suggesting that by using a nightly build (newer version) of this, that I might find FCKeditor or tinymce to be more compatible.

Although this may be true, and although I personally love to tinker with such tools to make my own web browsing experience better, the fact remains that I cannot expect all my Safari-using forum members to give their copies of Safari a heart-transplant (which is what "webkit" essentially entails). Therefore, I simply need to keep tinymce and FCKeditor disabled in my forum, or wait until FCKeditor will auto-disable itself under Safari. And like I've said in earlier posts in this thread, FCKeditor is, in my experience, better than tinymce except for the fact that FCKeditor won't auto-disable itself when the browser is Safari.

I think perhaps what we really need here is "pure simplicity, compatible with any modern browser." And yes, I classify Safari in that category. Honestly, we don't need much more than Bold, Italic, Underline, URL, Quote, and Code features! I wouldn't think this should be too hard to implement in a way that is compatible with IE Windows and Safari Mac.

Thanks for your suggestions.

MySchizoBuddy,

As I posted above, that FCKeditor demo does NOT auto disable.

MySchizoBuddy,

Thank you for the test in Safari. I just checked again on my machine at work, and it still shows a blank field in Safari (for that FCKeditor demo). My Macintosh G4 Cube at home exhibits the same exact problem. But after that test, I tried a couple other Macs in the office and found they could show the line of text and the text in the field was editable! I then created a new user on my G4 Cube here at work and found that Safari under the new user works fine to show the field and edit text.

So I backed up /library/Cookies & /library/Safari & /library/Keychains, and then I Reset Safari -- that theoretically restores Safari into a pristine, clean condition. I then restarted Safari. Sadly, I still cannot see the line of text in the field or edit it -- same problem as before!

I don't have any Safari hacks installed, so I can't see what's wrong here. Very odd. I know that reinstalling my OS would fix the problem, since the new user worked fine. But I'd rather not do that.

I enabled the Debug menu in Safari so I could see the errors logs. The JavaScript Console log shows several lines with errors. Interestingly, when I switch users on this same Mac and load that FCKeditor demo page, the JavaScript Console log is blank. So clearly, I am only getting these Javascript errors under my primary user account for some mysterious reason. And sadly, Reset Safari doesn't fix this problem.

UPDATE: I quit Safari and trashed user/library/Preferences/com.apple.Safari.plist . To my delight, upon restarting Safari and trying the FCKeditor demo, it works this time! I can now edit text in the field! (I must say that "Reset Safari" is a pathetic command in that it doesn't delete the plist file too!) Anyway, I'm quite pleased at this result.

Has anyone seen the editor on Google Docs?

Now that's an editor and from what I have seen it works flawlessly on all browsers, which further convinces me that anything that breaks and blames the browser is just a combination of bad and ignorant coding.

Posted: Saturday, 16 June 2007 at 2:15PM

Come now, that's like saying that any normal program that doesn't automatically work on Windows, Linux and OSX is badly or ignorantly coded...
Yup, that's exactly what I'm saying but we're not talking about any normal program, just a browser.
And Safari 3 beta is here, lots of things that balked in version 2 are now playing nice with the beta of version 3.

In any case, now the iPhone has landed, much more attention will be drawn to such issues and "bad or ignorant" coders will not get away with stuff usually just accepted by the masses. They will be exposed and hopefully named and shamed. I love progress.

Posted: Saturday, 14 July 2007 at 8:33AM

Currently, the many poorly coded (non-compliant and rely on Exploder to work) sites that work with Exploder because it's not compliant are not an issue because the majority of visitors also use Exploder.

Enter the iPhone which uses Safari and the very compliant Webkit. These sites, instead of receiving a miniscule number of complaints from a perceived "niche" market sector will no longer be able to ignore the complaints.

It happened in Australia years ago when, as Mac users, we were ignored and denied access to internet banking. Many IT departments had a kick up the arse (ass?) when it was realised by management that many complaints were being cut off with replies such as "go away and get a PC with IE" if you want to bank online.

I understand it's a matter of numbers, now the numbers again are increasing, so will the complaints and hopefully positive action as a result.

It's not just "bad" coding but reliance on active-x and similar technologies that are proprietary, available only for Windblows and blindly ignorant of any other platform.

Deny all you like that the iPhone is a business tool, forget about its current version 1.0 shortcomings, they are being addressed and it's not the individual features that make it great it's the sum of all parts and the promise of new thinking that make it unique.

Imagine no longer being held captive by the minions in your IT department in league with Microsoft and its evil exchange server with its closed system and Windblows dependent ways.

The end of the dark side is imminent in many ways, this (the iPhone and its potential) is just another ally in the fight against those that keep true progress in shackles with closed, sub-standard, proclamatory, big-market-share smugness and I could go on but I just fell off my soap box.

Posted: Saturday, 14 July 2007 at 9:50AM

No, Stash, You probably wern't... :D

Winblows expires when you hit puberty, true enough. But it then changes to Windoze. It's no different than when we rip on those who prefer to design websites with Dreamweasel or GoWhere? instead of SoftPress Freeway. Bash what deserves bashing, I say! Age matters little when you're having fun. And you never know how many 70-year-olds are out there on the net doing just that, acting like pre-teens, trying to relive the past!

Now what in the world do the last 8 posts have to do with TinyMCE (the subject of this thread)? Sure, they're general talk about editors, but they have nothing at all to do with TinyMCE!

No, because my current installation of FCKeditor works fine and I would rather use that now that TinyMCE (and yes, I installed and tested TinyMCE along side FCKeditor). But as I posted in the FCKeditor thread, we really need a new version that re-enables Safari because version 3 will most likely show all the icons now.

I get the "Are you sure you want to navigate away from this page?" alert after hitting [Add your comments]. Any way to disable this when running the wysiwyg editors?

I've not encountered this myself. Have you got a link to your forum where this is happening?

Hi everyone,

I'm very new to Vanilla and PHP have no idea how to integrate Tinymce inside Vanilla page. I can't find the instruction anywhere. Can someone help me with this please.

I already upload the file to Vanilla extension, now what php page in Vanilla should I include the code into, and where to put the code so the comment page can show the Tinymce panel.

Thank you so much for your help

help,how to add plugins such as media plugin