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

Shoutouts to our friends at Ephox, for their great contribution to the TinyMCE code base.

Also shoutouts to the WordPress guys, congratulations on the 3.3 release, we now have 2 of our projects running within WordPress, both TinyMCE and Plupload.

Thanky you all for using our products.

Showing some advanced work on how to customize and form the editor to fit your website better, using custom styles, adding custom buttons and styling the interface, a very good slide, wish I had heard the talk.

Check out the article and slides here.

This service is heavily inspired by jsfiddle.net

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.

On another note, we have a new employee, Davit Barbakadze has been helping us out for a bit the last couple of weeks and he is now a part of Moxiecode Systems AB. His main focus right now will be to incorporate some fixes and enhancements into Plupload and then move over to help out on TinyMCE development as well as other development.

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.

Well on the 1st of April, GitHub announced SVN support, most ppl thought it was an April fools joke, but it does actually work.

It is read-only of course.

If you want to check out TinyMCE using SVN you use this url.

svn checkout http://svn.github.com/tinymce/tinymce.git

Check out their blog post on GitHub for more info.

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!

Limiting write access

If you have other ppl than yourself that uses the software a good option is to limit functionality as much as possible until they request it. One good way of limiting the problem with users uploading files into the configured root folder (usually a website root) is to limit write access completly to that folder, but not sub folders.

Place a file named mc_access into the configured root folder and fill it with this content:

_filesystem.writable=false
_general.disabled_tools=createdir,createdoc,refresh,zip,upload,edit,rename,cut,copy,paste,delete,selectall,unselectall,view,download,insert,addfavorite,removefavorite

The underscore “_” forces the option to be local and not continue to apply to all sub folders.

Each configuration option in the wiki will contain example on how to use the config option inside an mc_access file.

Forcing formatting options

One common problem with users uploading images is that they tend to upload their 3000×2000 pixel camera images, any images larger than say 640×480 isn’t usually used on websites, unless you are publishing print quality pictures for press releases or similar. One way to force this, is to set formatting options in the only folder they are allowed to upload files, there are actually various ways to configure this, you can simple force a site wide upload.format option that places different sized files in different folders. This example is for use inside an mc_access file.

Create a file called mc_access in the folder where images are stored.

upload.format=640x480=%f_%w_%h.%e

This will create a file named <filename>_640_480.<ext> if uploaded in that folder (or any subfolder). The size will be forced to this.

One idea might be to have a main images folder, and then make 3 sub folders called “small”, “normal” and “large” and add different mc_access files to that folder for the different forced images sizes.

You can read more about the upload.format option in the wiki.

Directory templates

This is quite a nifty feature, when a user creates a folder, you can use directory templates in order to control what that folder can do and contain, that means you can put an mc_access file into a directory template! You might want to have a complete folder with sub folders when your user creates a new folder, so he knows where to put images and documents. Perhaps you want a certain index file, or empty submenu file to be included with every folder if you use it to control structure, submenus and layout.

You can checkout the configuration option in the wiki, also don’t forget that you can force your user to use these directory templates, and of course, if you configure using mc_access you can have different directory templates depending on where the user decides to create a new folder.

The MCFileManager also has file templates that allow you to copy a template file when the user creates a new document through the gui.

We hope these tips might help you on the way to implement our products with your own, good luck, and be sure to visit the forum if you have any problems.

This information will also be added to the wiki.