mojoPortal 2.3.1.9 has been released. A number of image related features went into this new release. Some of the new features found in mojoPortal 2.3.1.9 include:
Easy content animation/slide shows - You can enable it in the settings of an Html Content instance and it will create a slide show based on the content using cool transitions that you can also configure in the settings. The animation uses the jQuery Cycle Plugin. It can rotate images paragraphs or any html content.
Integrated Image Cropping
Bulk Image Upload in the Image Gallery - Bulk upload was added to the Folder Gallery in the last release and now the same feature has been added to the the Image Gallery.
Integrated Twitter Widgets
New Configuration file for TinyMCE - More control over which plugins and toolbar items are displayed is provided via an xml config file.
Additional details and more information on the features included in mojoPortal 2.3.1.9 can be found on the official announcement at mojoPortal.com.
Although you wouldn't expect an application with the version number of 2.3.1.5 to contain anything but bug fixes, in the world of mojoPortal almost every release contains new features for the CMS. mojoPortal 2.3.1.5 is no different with a number of changes centered around rich text editors (WYSIWYG). TinyMCE has replaced FCKeditor as mojoPortal's primary text editor.
Tiny MCE Editor Rises To The Top
For a long time now the FCKeditor has been the best editor available out of the box in mojoPortal. It was the only one with the ability to browse and upload images and files, it was the only one with integration for our Content Template System and Content Style System, and it was the only one with a spelling checker. Not anymore! I had not upgraded the Tiny MCE editor in a long time, I had tried to once and it broke and I was busy so I reverted to the working version. But recently we've been having some issues with FCKeditor so I decided to give the Tiny MCE upgrade another try.
Joe Audette, mojoPortal developer, writes that FCKeditor fans shouldn't feel like they're being left behind. mojoPortal also supports the CKEditor. The makers of FCKeditor realizing that the code base for their RTE was more than six years old and needing improvements began CKEditor as its replacement. CKEditor focuses on features such as accessibility and performance improvements that weren't quite there for FCKeditor.
Besides changes for TinyMCE and CKEditor, mojoPortal 2.3.1.5 also includes these enhancements:
New Permissions Tab in site settings
NeatUpload 1.3.18 upgrade
The DOCTYPE changed to Html 5 for included skins
The default 90 days allowed to comment on a new post post can be changed
Removed Site Office
New translations include Hebrew and Polish. The German translation has been updated.
Raphael Mudge sent us an email on his latest project, After the Deadline.
I'm a computer scientist working to fill a gap in current CMS feature sets. It isn't a new social or wireless feature. I'm working to bring spelling, style, and grammar checking to web applications. The technology is available for WordPress and the Open Source TinyMCE editor.
After the Deadline is an exciting plugin that adds a much needed feature often missing in most CMS rich text editors. After the Deadline currently supports plugins for TinyMCE and Wordpress. Some additional bullet points behind the plugin include:
I've been using the contributed Drupal module WYSIWYG API since last Fall. Although the module is open source and free (offered under the GPL), I feel like I got it for a steal at $30 USD.
One of the most frequent criticisms by new users of Drupal has been that the content management system doesn't include a rich text editor (WYSIWYG) in its core. Historically, the core developers have opted to include an RTE option through contributed modules. While the use of non-core Drupal modules for implementing WYSIWYG in Drupal is fine, the development pace, availability, and implementation of a particular RTE module (FCKEditor, TinyMCE, etc) has often varied when major versions of Drupal are released.
The Wysiwyg API attempts to improve the implementation and consistency of RTE's in Drupal. The module is capable of supporting any kind of client-side editor as long as there are support files available to integrate the external library with Wysiwyg API. Editors currently supported by the module include FCKeditor 2.6, jWYSIWYG 0.5, markItUp 1.1.5, NicEdit 0.9.0, TinyMCE 3, TinyMCE 2, and Whizzywig 55 (download).
Up to this point much of the work has been done by Daniel F. Kudwien (known as "sun" in the Drupal community). Since Daniel has invested a huge number of hours on this project he has asked users of the module to voluntarily contribute to the project financially. For someone like me who is not a developer, nor has a lot of free time, giving financially is way of showing appreciation for the open source products you use. Even the smallest financial support can help the community and future development of the software.
If you're not comfortable with donating to an indivudual developer in your open source project, if available, you should consider taking membership in the project's association or foundation. For instance, this week I'll be renewing my membership in the Drupal Association. Many of these open source groups such as the Drupal Association use the membership revenue to support the maintenance and growth of the infrastructure that Drupal.org runs on, as well as to produce various conferences and workshops around the planet.
I'm spending time Friday and this weekend upgrading the software I use to run CMSReport.com. You'll have to excuse the mess as I'm working with a lot of themes/modules for Drupal 6 that are still under development. Feel free to report problems below, but note that the WYSIWYG for comments is currently offline. working but considered under "test mode".
I'm in the middle of switching the text editor on CMS Report from FCKeditor to TinyMCE. Both are fine WYSIWYG editors, but I have seen some problems lately so this is a good time to try something different. The text editor is available to those who have open a free account here at CMS Report. The CSS in the Drupal theme I'm using isn't quite compatible with the TinyMCE editor so I'll be doing some tweaking in the next week or so.
During the past few months, I've been getting inquiries about how to place an ad on this site. If you are one of those people, I'm sorry if I haven't gotten back to you in a timely manner. I've been a little more focused on just getting the content out there as well as working on some usability issues for visitors here at the site. I plan on looking at some options and in a couple weeks should have a "how to place ads" page up here at CMSReport.com. If someone would like suggest an option, please feel free to leave a comment here or send an e-mail through the contact page.
As always, I'm open to suggestions for improving the site as well as criticism. A lot of people in IT don't like to hear complaints, but I'm not one of those people. Without good quality criticism, it's difficult make necessary improvements.
In case you missed the news, the Website for FCKeditor is now using the Drupal content management system (CMS). FCKeditor is a HTML text editor with a WYSIWYG interface and is commonly utilized in Web-based applications. The following was posted at the FCKeditor site:
We're proud to announce that, from today, the FCKeditor web site is running over Drupal, one of the best Open Source CMSs out there. After a long research, Drupal has proved to be the best solution to handle our half a million page views monthly, with flexibility and reliability.
This important change will make it possible to provide even better services to our community.
Ironically, the Drupal module for the FCKeditor hasn't been fully released for Drupal 4.7, the latest version of the CMS. The module documentation for 4.7 cites that the "integrated file management needs lot of manual configuration". Luckily for Drupal 4.7 users, the Drupal module for TinyMCE has been available for some time. TinyMCE is an alternative HTML text editor and in some ways could be considered FCKeditor's "main competitor". Here at CMS Report...we like both editors fairly evenly.