This is more or less a duplicate post based on another post made for project team members. This plugin adds the Xinha RichText Editor to the manager.
Some of the default plugins are not enabled at this time: CSS, DynamicCSS, FormOperations, Form, FullPage, HtmlTidy, Linker, SpellChecker, SuperClean, and Template. They are either not compatible or are not recommended for use with MODx.
Please post any bugs, comments, or whatnot. Definitely would appreciate the feedback!
L8R!
Jeff
Update v0.11:
* Fixed problem with multiple instances (variable wasn’t set). Xinha should now work with QuickEdit and TV’s.
* Fixed a few minor problems with certain plugins not showing up.
* The SuperClean plugin has been added to the list.
Update v0.2:
* Added two new plugins: ModxImage & ModxLink. These replace the default ’Insert Image’ and ’Insert Link’ dialog boxes with ones that provide integration with the resource browser. The plugins are available so long as the ’Use Resource Browser’ option is set to ’Yes’.
* Removed unused plugins from plugins directory.
Update v0.3
* Updated Xinha to revision 421.
* Added ClientsideSpellcheck, GetHtml, HorizontalRule, PasteText plugins.
* Changed how plugin selection works. Custom plugins are now entered via a comma delimited textbox. The plugin parameter for this was removed.
* Front-end capabilities were not added due to configuration and security issues. It is not recommended to use Xinha for a RichText widget!
11/20/2005 Notes:
Regarding update v0.3, this is still considered a beta because...well...Xinha is still a beta itself. Until a stable, official 1.0 release, there are going to be some outstanding issues with Xinha. These issues effect what Xinha can and cannot do in MODx. Most notably, Xinha is not the most configurable editor when it comes to its toolbar. As such, using Xinha as a front-end editor within a RichText widget is not recommended since too many options would be available for the average visitor. Thus, I didn’t rewrite the plugin to allow for front-end use...I just think that Xinha is not the right editor for this. Also, I’ve noticed quite a few quirks in getting Xinha to display properly in all browsers (especially IE!!).
It is for these reasons above that I will not likely be continuing full development on the plugin. I might release an update here and there...but unless I start seeing some serious turn-around on the development of Xinha, I just don’t think it’s worth the effort to continue supporting it for the time being. This doesn’t mean that Xinha will be ignored in the future...it just means that I won’t be messing with it too much...at least until a more stable version is available.
