First of all we’d like to say thank you for the great comments and feedback we have received about the epEditor. Secondly we’re sorry we’ve been so quiet for such a long time.

As we said back in August, client work took over our world and we spend all of September and a chunk of October building an web app in Ruby on Rails. The good news is that the app was launched mid October and we finally had time to take a holiday.

So now we’re back, rested and refreshed and are pleased to announce that at long last version 1.0.6 of the EE epEditor module is now stable enough to be let loose. Please be aware that this is still very much a beta release. We really hope some of you will download it, put it through it paces and let us know how you get on; but we suggest that you do so in the safety of a development environment. Read the rest of this entry »

We had been hoping to release version 1.0.6 at the end of August, but unfortunately we are going to have to push this back.

Putty towers has been a hive of activity over the last few months; we’ve launched two new sites (www.readingsight.org.uk | http://www.oneworldtrust.org/csoproject/) and have a third ready and waiting in the wings. On top of this we’re deep in developement of our first web-app so it’s a very exciting time. Read the rest of this entry »

OK, we’ve been back to the drawing board and come at this from a different angle. The method we were using to determine the include path from the image manager to the core.system was not robust; it worked for some but not to others and we couldn’t figure out why.

As we were using a module file to process the image uploads anyway we have decided to extend this and use the module directory as the place to store all the editor files. This way the path from there to the core will be the same for everyone and (hopefully) the image manager should work.

Unlike previous version of the epEditor you will need to install both the extension and the module. The extension is used to hook into the CP and render the editor in the publish page, the module is used to create the required records in the exp_actions table and to configure the editor.

Apart from the changes to the installation process the other major update with this release is the ability to manage custom classes via the module interface, so there should be no need to go anywhere near the JavaScript files.

Please give this one a try; there are installation and updating instructions in the read me file. I have run a load of tests here are the only problem I encountered was when I updated from a previous version while I was already logged in to the CP and viewing an publish screen, so please log out before you update the files.

Download version 1.0.5 here

We’re please to announce that version 1.0.4 of the EE extension for the epEditor is now available to download. Read the rest of this entry »

We have just updated the version 1.0.2 release with a bug fix and a change request.

1. The pagination issue in the image manager has been resolved.
2. The image manager and link manager popup windows are now centred.

Thanks, EP.

We recently started using the excellent Structure module and immediately saw the need to be able to create internal links between pages. So we set to work on the link creation element of the epEditor and are pleased to announce that version 1.0.2 is now ready to download. Read the rest of this entry »

In response to feedback we received from other Expression Engine users we’ve spent some time working on integrating the epEditor with EE’s proprietary file system.

The epEditor already had methods for adding and updating images so we made a few modifications and hooked these into a simple Image manager. Version 1.0.1 of the edEditor is now ready to be downloaded. Read the rest of this entry »

Tapping in to the excellent network of developers and general webby people we have down here on the south coast, we asked Brighton’s New Media List for volunteers to test the epEditor. We had a lot of feedback and some really encouraging comments but the main issue which arose was the way Firefox behaves when you press return.

As with most browser-based editors, the epEditor utilises the native editing capabilities contained within the browser, and, as with everything, these are inconsistent. Read the rest of this entry »

Tempted by the promise of Version 2 we decided to give Expression Engine a try for a site we’re working on. The current version (1.6.4) ships without a WYSIWYG editor so we decided to use our own.

EE’s architecture allows the creation of extensions which enable “developers to modify aspects of ExpressionEngine without hacking the backend scripts“. Tiny MCE already offers an EE extension for integrating their WYSIWYG editor so we grabbed this, hacked around with the code and rolled our own.
Read the rest of this entry »

Through our work with various Content Management Systems we have experimented with several browser-based WYSIWYG editors. We wanted something which was cross browser compliant, easily to install and modify and which generates valid XHTML.

We looked at several but none quite performed the functions we were looking for or created XHTML which we considered up to standard, so we began developing our own.

The result is the epEditor which is now just about stable enough to be released for testing. It provides a suite of basic editing functions and comprehensive HTML cleaning methods.