Attached are the files for the beta extension for using the excellent Xinha wysiwyg editor with EE. Xinha is a descendant of the HTMLarea wysiwyg editor. It would be cool if some people could see if the extension installs and works correctly on their systems. Please see the included READ ME file for installation instructions.
Update: I just noticed that the Xinha download page is unavailable due to having exceeded its bandwidth limit. Perhaps this is due to the popularity of the editor. In the meantime, I’ve made the Xinha editor files available for download on my site.
Update—in the read me file, I ask beta testers for thoughts on how to set path variables for the ImageManager plugin that comes with Xinha. I’ve now gotten that question answered by someone on the Xinha discussion board.
Here’s an example. If your images are located at /exp/images/uploads, then the variables for that plugin would be set like this:
Hey Vik- looks cool. I’ve downloaded it, and when I get the chance I’ll see how it works on my test install. Which I seriously need to get around to updating first!
I used it for all my posts yesterday, and it worked very well. HTMLarea, which Xinha is built on, has been around for quite a while. It has a lot of plugins and cool features. It seems to load quickly too.
Update: I’m continuing to use it, and it’s working very well.
I just noticed that the Xinha download page is unavailable due to having exceeded its bandwidth limit. Perhaps this is due to the popularity of the editor. In the meantime, I’ve made the Xinha editor files available for download on my site.
As you’re working with this I though I would mention the Open Realty project.
This is a suite of xxMP tools for online realtors with it’s own cms integration templates - ie it can be installed on the same site as EE and integrated into the EE templating system to create an integrated look and feel between two otherwise separate applications (useful for anyone with realty clients).
O_R allows users to upload Xinha (and FCKEditor) and then select which to use (each has its own merits and de-merits) at different times, through a pick-list in the O_R Control Panel, in much the same way you are trying to achieve here.
I will give the beta a shot today and report back.
Jules - the exp directory is whatever directory you have your index.php and path.php file in. In many cases, this is the site root. In other cases, it may be a directory called exp. Or foo, or whatever you call it.
http://www.yourEEblog.com/exp/images/my_images/
- this was later on in the readme. That’s the only reason I knew what exp was supposed to mean.
Jules - the exp directory is whatever directory you have your index.php and path.php file in. In many cases, this is the site root. In other cases, it may be a directory called exp. Or foo, or whatever you call it.
http://www.yourEEblog.com/exp/images/my_images/
- this was later on in the readme. That’s the only reason I knew what exp was supposed to mean.
But yes, the docs need to be clarified.
Sue Crocker - 02 February 2006 06:23 AM
Jules - the exp directory is whatever directory you have your index.php and path.php file in. In many cases, this is the site root. In other cases, it may be a directory called exp. Or foo, or whatever you call it.
http://www.yourEEblog.com/exp/images/my_images/
- this was later on in the readme. That’s the only reason I knew what exp was supposed to mean.
It was over a year ago that I first installed EE, and I forgot that exp is not a directory that is part of the standard installation. I’ll update the extension and upload it here. Thanks for this good beta testing report.
Sue or Rob1, could you give me some advice on this? I need to set some paths for the extension to use, based on the individual user’s EE installation. I could ask the user to enter path info in the settings for the extension, but it would be more elegant if the extension could figure it out for itself. The paths I need to set are shown here, with contents that work on my EE installation, which is inside the folder “http://www.bigpicweblog.com/exp/”:
_editor_url = "/exp/xinha/"
<!-- Load up the actual editor core --> <script type="text/javascript" src="/exp/xinha/htmlarea.js">
<!-- Load user preferences --> <script type="text/javascript" src="/exp/xinha_prefs.js">
I have a feeling there may be a way to determine the paths via PHP with $_SERVER[‘PHP_SELF’], the explode function, etc., but without a Zend installation here it could take me hours of trial and error to educate myself on the right way to do this—whereas you may have done the identical thing many times before.
That way they put the xinha folder wherever they want- and enter it as a setting for the extension. Seems like the easiest way- cause then you can just copy from Paul. Otherwise, specify how the structure must be and use a path variable.
Okay, I’ve got a version working here, using a path that the user can enter in the settings file. (BTW, the settings capabilities of the Extensions architecture in EE are very cool).
I’ve got a question about the version updating mechanism, which I’ve posted in the Tech Support section. Once I get that taken care of, I’ll post a new version of the extension here.
The new version of the Xinha extension is ready for beta-testing. It’s attached. It lets you enter the path to Xinha in the settings for the extension. Xinha can be located anywhere on your server.
I’ve been using Xinha for a week on my system, and I like it a lot. Some cool features:
- Loads quickly.
- Has lots of plugins.
- Has Find and Replace.
- If necessary, can edit raw html right in the main edit window, rather than in a pop-up window.
- HTML Tidy plugin does some helpful clean-up.
I look forward to beta testing reports so as to get this finalized and available to all EE users.
I see 11 potential beta testers have downloaded the latest version so far. Have you had a chance to install it yet? If so, please post your feedback here.
