We are moving websites around abit today (Tuesday 19th and possibly Wednesday 20th), so some outage will occur, mostly related to using the forum or bug tracker on the TinyMCE website, and also the shop will be down for a short period of time. This will affect all our websites Plupload.com, Moxiecode.com, TinyMCE.com and Fiddle.tinymce.com.

If you encounter any problems, try again the next day, if you still encounter problems with our website or services after Wednesday, please report it to us.

I guess its been out for a while, Apple now uses TinyMCE in their iCloud email application with great success.

Was a long time ago they showed us the beta of the new iCloud and told us they wanted to use TinyMCE. They are also using it together with Sproutcore, with TinyMCE mostly just used as an engine for the editable field, much like Squarespace and others are doing.

Stay tuned for TinyMCE 4, it will be another excellent major update to TinyMCE!

Jennifer Lampton has a video of the DrupalCamp Austin in November 20th 2011, explaining some advanced configuration with Drupal, TinyMCE and different modules.

There is a lot of modules, issues and security to keep track of when configuring your editor to Drupal, she goes through configuring and adding some good functionality.

Check out the video on her website.

Of course, we would recommend using MCFileManager and/or MCImageManager with Drupal to make it easier to work with images

Today we released a new service, to allow you to try different configurations and setups with TinyMCE, as well as aid in examples for our bugtracking system, we introduce TinyMCE Fiddle (fiddle.tinymce.com). Service is still in beta stage, feel free to comment and provide feedback in the forums at tinymce.com.

This service is heavily inspired by jsfiddle.net

The buzz around Plupload is huge right now, much more than we anticipated, and we are putting more resources into the continued development of Plupload and starting to create a community around it similar to TinyMCE. Over the next couple of weeks/months you will see a rebuild of the website so contain a wiki for the documentation as well as its own bug/feature tracker system (like the new one we are using for TinyMCE). The current website wasn’t built to contain so much content, but as the project grows, so must the website.

The new TinyMCE website is a huge success, ppl are getting engaged with the bug/feature tracker and submitting good quality reports, something we appreciate a lot and we no longer have to put up with the incredibly turtle-slow Sourceforge tracker system.

Just as a side note, many seems very interested in exactly when the new TinyMCE version will be out of Beta, can’t give you any exact date, but we expect this to be the last beta unless something unexpected shows up.

So, 500 million ppl just got access to TinyMCE, sweet

And as you might have noticed (we tweeted about it) Facebook is now using TinyMCE in their “Notes” section as well as “Facebook Questions”.

We are now back from vacation since the start of this week, getting back into things again and we got a lot of nice stuff for the community comming up.

In order to provide better TinyMCE support for those who need it, we have started a Partner network, and our first partner signed up is Ephox, they will provide support and commercial licensing for TinyMCE.

In addition, they have also commited resources to help out the community in a more direct way, by helping to fix bugs, answer issues on the forum and various other things. You might have seen Adrian commiting bug fixes on Git and answering some topics on the forums. Ephox has also setup an automated UNIT test bed that checks TinyMCE across browsers on different Operating systems as soon as something is commited to GitHub TinyMCE project. You can check out the Ephox Enterprise TinyMCE offering at their website. Also check out Adrians view on this partnership at his blog.

So why do we need this? Moxiecode Systems is a rather small company, we want to focus on the development of TinyMCE and not get bogged down with to much support and licensing issues (not everyone like/can use LGPL). “Outsourcing” these parts to our partner network and filtering bug reports through them will allow us to focus more on the needs of the community and future development.

Switching to GitHub was a major step in getting more social, getting more developers engaged in TinyMCE and making it simpler to contribute. This Partnership network is another step towards Enterprise customers that want more than just a community supported editor, they need premium support, guaranteed turn around times and many other things.

If you wish to become a partner, contact us and we will fill you in on how this works.

Moxiecode and TinyMCE is doing well, and we are looking for more ppl to join our team of developers. You can be located almost anywhere in the world.

These are the job openings right now:

Backend Developer

We need help working on the MCFileManager and MCImageManager products, an experienced developer could really help us develop some new thoughts we have regarding our products as well as develop new products and ideas.

Primary skills: C#, PHP

Secondary skills: JavaScript, HTML, CSS

Frontend Developer

Would you like to work on the most popular Open Source WYSIWYG editor in the world? We need someone who knows JavaScript like the back of his hand.

Primary skills: JavaScript, HTML, CSS

Secondary skills: PHP, C#

How to apply!

If you feel like you have the skills needed, send your application to info at moxiecode dot com with your name, address, current work situation and CV. If you are apart of some Open Source project or have code located in some public repository, send some info on how/where we can look at it and describe how you where involved in that project.

Social coding is the new thing, since our move to GitHub the community activity on all our project have increased, users find it easier to clone, fix, extend, patch and contribute to the software through GitHub.

The learning curve for Git is kind of steep, and we hope that more ppl will be able to help out when the tools (such as TortoiseGit etc) becomes better and more understandable. It can only get better from here.

We recently released a new version of TinyMCE (3.3.2), and we continue to review patches and contributions made by others.

Also, through a recent partnership we can offer better support and custom license options for TinyMCE, but more on that later.

If you wish to follow any of our products on GitHub, here is a link list of our current project.

• TinyMCE
• PunyMCE
• Plupload
• js-build-tools
• TinyMCE Compressor
• TinyMCE Spellchecker

Thank you everyone for all your contributions!

This new release adds better error handling with the new “Error” event. It enables you to handle everything from initialization errors to custom errors depending on server responses. We will add examples of usage of this to the site as soon as possible.

We also introduced a new ChunkUploaded event this is very similar to the FileUploaded event except that it’s fired when a chunk is sent to the server not when all chunks have been uploaded. If you trigger an error inside this event it will cancel the remaining chunks.

A new bytesPerSec property was added to the total progress. This allows you to display the current upload speed.

We also added new support for renaming of files before they get uploaded. This is a feature of the jQuery queue widget and will only be available if you disable the unique_names option and enable the rename option. It will only allow the user to rename the base part of the file not change the extension, how ever extensions should always be verified on the server for security reasons.

The Plupload site finally got a Forum. This has been a popular request by the community. So discussions regarding the product, news about the product etc will now be posted there rather on this blog. You can also follow the news using Twitter on our Plupload twitter account.