(f) ckeditor 3

Stay tuned... when CKEditor will become stable, there will be a Drupal module available.

Looks like RC is released. Do you find it stable enough? Or planning to wait for the final release?

Is there any roadmap? Cant decide what wysiwyg to use. And dont know what time it will take, to support Ckeditor 3.0

Though as this point i still prefer the fckeditor module, you can use the current ckeditor release with the wysiwyg api module (v2 and v3) -- there's an issue for it in the issue queue.

So, the final version is out. i vote for support!

In the next version of this module.

Does the current dev build support CKeditor 3?
OR is it possible to drop Ckeditor folder contents into the fckeditor directory of this module and "work"?

No, that's not possible. I have yet to look into the differences between FCKeditor and CKeditor in terms of invocation.

Subscribe

Subscibe

@Jorit Yes you're absolutely correct, the directory structure, invokation, etc., is completely unique to CKeditor. Instead of invoking the FCKeditor class as I have done in the past with FCKeditor, the new version is simply called with a .js file inclusion in the head, and by id'ing a textarea element to "ckeditor1", "ckeditor2", etc. You can defines styles / options / etc in the

Well I'm willing to get Image Browser going on it once ckeditor is there...

Subscribing...

subscribing too...

subscribing

subscribe

subscribe

subscibe

subscribe

subscribe

subscribing

subscribing

Subscribing.

Subscribing.

subscribing

subscribing

Another subscribe :)

subscribing

Umm ... Wysiwyg API has a working version of ckeditor 3.0

#462146: Add editor: CKeditor

and

http://sirkitree.net/node/25 <-- shows you how to install it with the appropriate patches (pretty simple!)

Josh

A fact I pointed out almost 30 subscribes ago. ;-(

Also see http://drupal.org/project/issues/subscribe-mail/fckeditor

@joshmiller and @WorldFallz: I think many of us are waiting on a stable release either here or there, doesn't matter. I subscribed to the WYSIWYG API thread a while back too, but I tend to not trust WYSIWYG patches until sun does.

subscribe

The problem with Wysiwyg API that it never seems to give you all the buttons that should be available on the Full HTML toolbars in FCKEditor. I have installed CKEditor on one site with WYSIWYG API and despite checking most of the buttons I don't get several important ones in the toolbars, i.e. font, style, pagebreak. This was true with FCKEditor as well.

Subscribe

subscribe

also subscribing

Subscribe

subsribe

subsc.

subscribe

subscribe

subscribe

subscribed

Subscribe

@wwlc: you said when ckeditor is stable there will be a drupal modul. Well... it is stable.
Is there a schedule, when this modul will be available?

subscribe

sigh, subscribe

subscribe

subscribe

+1

subscribe

subscribe

subscribe

subscribe

subscribe

subscribe

subscribe

hmmm... seems like there are a dozens of people who are interested in this, but nobody is willing or is able to start this new project. :|

Well , if you see the first post , it's quite obvious that someone is working with it!

Subscribe

Count me in too. Wish I had more time though to help with some patches. Subscribing.

subscribe

+

Subscribe

subscribe

Subscribe

Subscribe

Uber noob question. But do you all write subscribe so you can track this post? Or is this a subscribe button I'm missing? =\

If you make a post (whatever text) this issue will appear in your "My issues" section AND more important, the developer sees that there are interested ppl.

You also can subscribe this the old school way:

http://drupal.org/project/issues/subscribe-mail/fckeditor

but than you get ALL issues and nobody sees you did subscribe.

If i am mistaken, please correct me.

Yet another Subscribe, Very interested in being able to not let people call it the F**CK Editor.... -.-"

major subscribe. ck is head and shoulders above fck especially in terms of load time.

omg i beg you-- please stop with the subscribes already. They serve no purpose at this point except to bubble the thread up on 60+ trackers 3-4 times a day for no reason-- it's beyond absurd at this point. This thread is the single best example of death to subscribe I have ever seen.

With almost 50k users I can assure you, the maintainer is well aware of the interest in this upgrade-- we certainly don't need 50k '+1 subscribes' on this thread to prove it.

To follow along you can subscribe to this issue queue as pointed out in #72, monitor the feed, or simply bookmark the thread and check time to time.

Also changing priority as upgrades are certainly not critical when there's a fully functional official release of a module available.

subscribing does serve a purpose as it is easier to monitor the feed of just 'my issues' that i've subscribed to, rather than monitor feeds of each issue separately.
if there was a 'flag' or some other way, i'd use it, but as far as i know, the only way to flag an issue is to add a pointless 'subscribe +1' post to the issue.
are there any other ways to flag an issue that i'm not aware of?

and the fully functional release of a module (i presume you are talking about Wysiwyg API?) supporting the newest CKeditor doesn't appear to fully integrate with IMCE, so it isn't fully functional in our case, plus we aren't too keen on installing a completely different wysiwyg module along with a helper module to get IMCE to work with it.

i'm glad the maintainer is well aware of the interest in this upgrade and we can't wait for the upgrade to get released.

@worldfallz - While I can agree with you that the priority shouldn't be "critical", I wholeheartedly wish there was an "URGENT" priority in that dropdown. The absolute largest complaint I get from my users on a daily basis is how SLOW fckeditor loads. It comes down to a productivity issue: If my users are migrating a large number of sites with thousands of pages, the added minute its taking fckeditor to load adds up. For just the general Drupal user, this may be fine. However, in an enterprise environment where we're paying our developers by the hour, this ends up costing us money. So the priority for us is much more than "normal".

Also, as you point out, there are 50K+ people using this. While I agree that we don't need the million subscribes to gain visibility - its been half a year since this thread was started, at this point a status update from the developers at some kind of regular interval would be nice. There are potentially 50K+ people waiting silently and respectfully for this update.

Unbelievable.

Wow-- you guys realize this is open source right? ANYONE is free to work on this and submit patches. We have 60+ useless (yes, useless), "+1 i want this now"s and yet not one offer of sponsorship or assistance. If it's that important to you and your business / clients I recommend you put your money or your time where you mouth is. Otherwise, wait patiently for the maintainers to provide scores of man hours of work for you for free.

WorldFallz, don't be a jerk. People are free to both 'subscribe' to threads and are also free to ask 'when will this be available'. Chill out. Are you a maintainer of this module? Who are you? Why are you in everyones face simply because they ask when?

I'm not the one being a jerk-- I merely commented on this thread to provide people with a possible alternative while they wait. Sorry, but being a jerk is "+1 i want this too" 60+ times when the maintainer has already said they're working on it.

oh, and I'm also free to express myself -- same as you or anyone else. At least I don't engage in name calling. But then, whenever someone has nothing of value to say the ad hominems come flying don't they.

omg i beg you-- please stop with the subscribes already. They serve no purpose at this point except to bubble the thread up on 60+ trackers 3-4 times a day for no reason-- it's beyond absurd at this point. This thread is the single best example of death to subscribe I have ever seen.

I type "subscribe" just to piss people like you off lol

So let em do whatever they want. It's just the internet. People are going to comment until they can no longer comment.

Excellent work! Per discussion with the maintainer this thread is now locked.

BTW-- irritating maintainers, who provide their massive efforts for free, is probably not the smartest way to participate in an OS community.

And yes, he is already aware of how important this feature is.

FYI: http://drupal.org/project/ckeditor

After two years of being locked, this thread has been unlocked by a Drupal.org webmaster. I will now close it in my attempt to close all FCKeditor issues. The module will stay around for legacy support, but I encourage all users to upgrade to CKEditor (http://drupal.org/project/ckeditor), especially since browsers evolve and FCKeditor does not.