CKEditor 4 Beta Released
.jpg)
We are happy to announce the release of the much-awaited CKEditor 4 Beta. The team has been hard at work developing CKEditor 4 and now you are welcome to try it out before the official release!
CKEditor 4 represents one of the biggest advancements for us in terms of WYSIWYG functionality. It brings many new improvements to an already large variety of HTML editing tools designed to help you and your users easily create content-rich websites.
Inline Editing
The biggest enhancement in CKEditor 4 Beta comes in the form of Inline Editing, an HTML5 feature that removes the static limitations of most online HTML editors, making the toolbar a dynamic and discreet part of your editing page. You can now create content directly on the published page, giving you a perfect idea of the final work without using any impractical “preview” functions. CKEditor 4 truly gives you a WYSIWYG experience!
CKEditor has always been known for its customizability so we are proud to reveal that CKEditor is the only WYSIWYG editor offering a flexible hybrid solution, including both inline and normal text editing interfaces in a single package.
Find out how inline editing can help improve your website experience!
See inline editing in action
CKEditor Joins GitHub
.png){kind=logo}
CKEditor 4 Beta is now available on GitHub:
https://github.com/ckeditor
For those of you who never heard of it, GitHub is a popular service designed to simplify software development projects through git and improve community involvement. This is an exciting and important move for us as it will make it easier to track the various teams and contributors working on different parts of CKEditor. GitHub will also help fork CKEditor into different directions - something we always encourage. The final outcome will give the community an Open Source application easier to contribute to.
And Much More!
Enhanced DOM and CSS performance: CKEditor 4 has been reviewed and optimized to enhance its overall functionality.
Reformatted source code: We reorganized the source code to encourage community contributions, adopting a coding formatting strategy that matches the most important JavaScript applications out there.
Backwards compatibility: The CKEditor 4 JavaScript API has been kept compatible with CKEditor 3. We focused on making the upgrade experience as seamless as possible. Report issues regarding backwards compatibility.
Improved Copy/Pasting: We have rewritten the clipboard handling feature set, one of the most important functions of any HTML text editor. You should see increased quality in all browsers.
CKEditor 4 Skin Contest
Design the new default CKEditor 4 skin and win $1,000!
With so many improvements it’s only logical that we would also change the editor’s look. And we will, with your help!
A Real Man’s Move: Dropped IE6 Support
It was a tough decision, but we are finally dropping support for IE6. CKEditor 4 will represent this historical milestone.
Additionally, while we still support quirks mode on IE for normal editing, we’re not supporting it for inline editing. Considering that inline editing represents the future, it is senseless to support quirks mode on ancient technologies (just have <!DOCTYPE> on your pages!).
Feedback and What’s Next
CKEditor 4 Beta is a work in progress and not the final version. CKEditor 4 is still in development so we need the community’s help to iron out the quirks. Your input is very important to us. We will continue working on final enhancements and overall stability tweaks while listening to your feedback. If you find bugs or issues in the Beta, please report them at the following link:
Download CKEditor 4 Beta
So what are you waiting for? WYSYWIG text editing has taken giant leap forward so don’t be left behind. Download CKEditor 4 Beta now and experience the best online text editor like never before!
AWESOME!
and where's the CK4 documentation ?
CKEditor 4 Documentation is in the works and will be available once CKEditor 4 is officially released. Remember, v.4 is still in Beta. We are changing CKEditor 4 according to your feedback. In the meantime, check our new API (http://
Hi
I joined the dev site google group but I can't create any topics. Do I need to be approved before posting topics? In the mean time I tried the example of creating inline edit using code and I see the toolbar appear when I click an editable region but all buttons are grayed out and I can't type in the region even though it has a yellow border. Something to note is that I have multiple editable regions on the page and am trying to attach CKEditor to each one of them using
$('.editable').each(function(idx, ele){
CKEDITOR.inline($(ele).attr('id'));
//CKEDITOR.inline(ele);
});
Is this the right approach? if I set contenteditable="true" on the div I want to edit and not use the inline editing using code sample code then I see the editable and can edit all editables.
Thanks
You need to be approved to take part in google groups. As for your problem, this isn't the right place to post such topics. You should do it in our forum: http://cksource.com/forums/
This is exactly what I have been looking for! I am working on making it work for editing CSS3 regions. Worked great right out of the gate!
Glad to hear you like it and everything works fine. But we need feedback if you find issues! Report them here if you do: https://dev.ckeditor.com/
Is there a timeframe for when version 4 will be out?
I was just going to start looking for a different editor that supported inline editing, but since version 4 will have it I won't need to look for a different library.
Of course if it won't be out for 6 months I'll still have to consider a different library unless I want to risk running a beta in my production environment.
In about a month or two max.
The good news is, so far I haven't found any issues yet! One thing I noticed though is that with inline editing, the "Source" tab doesn't appear to be available at this time. Is this by design for inline editing? Is that feature going to be available with inline editing in the future? If not, I may end up building it myself as a custom button. Most of my users don't use it, but it does make it handy for me and my other web developers to have more complete control over the html for our content.
+1
+2
FYI I got an answer for this. Source isn't available for inline editing yet.
http://stackoverflow.com/questions/13617111/i-cant-add-the-source-button-to-ckeditor-4s-toolbar/13649394#13649394
the inline edit feature is cool but how does the "saving" work? there's not post event going on that I could see
Consider that the editor, in the new inline mode, doesn't work like a <textarea> replacement in that case. So, we're not inside a form to be posted, but instead we're playing directly into the page contents.
This means that the editor is not responsible to deal with the data handling part of the page. That depends on the application that uses CKEditor, which will be controlling the page, much probably adding aditional UI elements for saving, aborting, login, etc.
Inline editing is a very cool thing, but it'll be useful on new kinds of applications, that are made for inline editing. A one to one replacement for form based editing is not the case for it.
You could use JavaScript to check for the .blur event on the editor, and when it occurs, check if the editor is dirty, and if it is, call the .getData() method and send the data via AJAX to your server.
where/how does the inline editor post? How does it get saved?
Помогите пожалуйста, ставлю на MediaWiki 1.19.2, что прописать в LocalSettings.php, пытался:
ckeditor.js
API-CHANGES.md
не запускается.
You might need to create a custom extension to make it work on MediaWiki. There used to be a third-party plugin for it in FCKeditor but not for CKEditor. Here's a link to it - please note that we do not offer support for third-party plugins: http://www.mediawiki.org/wiki/Extension:FCKeditor_%28Official%29
there is a relatively fresh version CK editor extension for mediawiki.
http://www.smwplus.net/index.php/WYSIWYG_extension
it doesn't support ckeditor 4 yet though.
how can i disable the purified output
problem is in my code there is statements and ckeditor strips some of them out.
my <!-- IF B_COUNTDOWN --> is there but the <!-- ENDIF --> is gone
also <table id="csstable2" cellspacing="4" cellpadding="0" border="0" width="620px">
is gone and some other things.
Hi Looks like this is getting to be best editor in the world :)
i like to use Ck editor to edit my pages so i need to have the code maintain syntaxes html etc.
i use the sample outputhtml.htm as for it to be strict html 4
so nice if there is a way to disable the Purifier.
This looks great! Did someone compare this to http://aloha-editor.org/index.php ? Aloha is out there a bit longer already and looks really good too. A feature comparison list and a strengths/weaknesses overview for CKEditor 4 vs. Aloha would be very helpful!
Okay, found one good thing About Aloha: It lets you copy and paste via mouse. CKEditor 4 doesn't and claims it's a browser restriction. But can't be, otherwise Aloha couldn't do that, hm?
It seems CKEditor 4.0 has a more liberal licence than Aloha. It can be used in commercial software: http://ckeditor.com/license
If I understand it correctly to use Aloha in a commercial project you have to buy a licence: http://aloha-editor.org/license.php
CKEditor builds a custom context menu for the mouse right-click, so it is possible to add editor related features to it. Others instead leave the default browser menu, which is ok for copy/paste, but it much more limited for the rest, as there is no way to enhance it.
Ah, that makes sense. However, the text appearing when one tries to use copynpast would have to be changed I guess. Into something like "Our customized context menu cannot access the browsers copy'n'paste functionality, due to security restrictions"... That would be more accurate, hm?
Anyway, does a customized context menu give users so much? I have a client who really wants copynpaste to works 'as in other editors' he says. So switching just to get this feature is not the best option as ckeditor is otherwise great for him.
An easy solution would be to make it possible to switch off ckeditor's context menu. That option would be great! Shouldn't be too dificult to implement, hm?
Seems its already there: http://dev.ckeditor.com/ticket/311 Great!
hi,
we are currently using fckeditor, and looking into upgrading to ck.
will you recommend using the latest 3. version and then upgrade to 4, or use the 4 beta release and then update to the final version?
We are currently upgrading from FCK to CK and i`d like to know whether we should use the beta or continue with 3.6.5 implementation and then migrate to 4 when it is released?
I`d appreciate a quick response.
Thanks!
Lior
Install either one but betas are used when you are willing to find bugs. Switch to 4 when it's out if you have no intention to contribute to the beta.
is there an estimated release date
It's hard not to use the "soon" reply, but that's all I can say. We're finishing up other things which v4 depends on, and those things sometimes get delayed. In a matter of weeks, if you want a more specific date.
I'm rewriting https://github.com/galetahub/ckeditor/tree/master/app/assets/javascripts/ckeditor to work with version 4.
Will old plugins still work with v4 or do they need a complete rewrite?
We tried to keep the CKEditor 4 API as compatible as possible with version 3.
There are some differences though, most of them documented here:
https://github.com/ckeditor/ckeditor-dev/blob/master/API-CHANGES.md
I've integrated the new beta with the existing ckeditor gem for rails. See https://github.com/lafeber/ckeditor - it works.
Merge branch 't/9535' doeswork with CKfinder ! did something change ?
Love the new inline editor and it beats aloha hands down for the fact that it does not force a fixed width on the editable content areas of 177px like aloha does - if you are trying to inline edit really narrow columns, aloha breaks it. CK editor v4 appears to leave it WYSIWYG and this is just what we want, but...
How on earth do you send edited data via php to a mysql database. With the old ckeditor you just add a text area and submit the changes. How do you do this with inline editor?
Everyone is complaining that there are no examples on passing the edits - and they are right. Every example shows cool multi-editing and cool tag specific edits - but what use is all this if no one knows how to send or save those changes.
Come on CK - do a simple php posted data example
Seriously, it's a great feature which is worthless without a hook to let me know that the content has been changed. How do I bind to this event?
This is looking great, can't wait to update my CMS to use this. I was just wondering if there were any plans for for image managent. Is CKEditor compatible, or a new version going to be released?
ckEditor does not get resized according to dimensions provided or resolution. Its editable area carries a default height of '200px' ! and if we try to add dynamic height according to resolution it breaks and doesnt resize itself once the height is given.
Is there any event that can give us any kind of indication or flag that ckEditor's DOM is completely loaded.? If this is possible then i can carry height of toolbar and bottom area deduct it from editor container and give calculated height editabe area.
Would great if any solution provided. I tried 'resize' and exec'Command'
Bad issue! Awaiting positive reply.
Where is JQuery Adapter for CKEditor 4?
I was wondering is that missing !! Please reply if u read me.
how to use jQuery in Ck 4 please help me out.