First, the details as requested in the "before you post" post:

Website URL:http://juice.spidersilk.net (test site)
XOOPS Version: XOOPS 2.0.13.2
Module Name/Version: AMS 2.4.1
PHP Version: 4.3.10
MySQL Version: 4.1.14-Debian_3-log
Web Server Software (Apache/IIS/Other): Apache/1.3.33 (Unix) DAV/1.0.3 mod_fastcgi/2.4.2 mod_gzip/1.3.26.1a PHP/4.3.10 mod_ssl/2.8.22 OpenSSL/0.9.7e
Operating System: Debian Linux (don't know what version, sorry)
Theme you are using: my own
Custom template: tweaked templates very slightly, but only in cosmetic ways, nothing major
PHP Debug Messages, MySQL Debug Messages, Smarty Debug Messages: none of these showed any errors
A full description of the issue:

I am using the Koivi editor with AMS, and the image manager does not seem to be working properly. Yes, I did install the alternate image manager template and update the system module, and I'm getting the little "insert into WYSIWYG" button, which *seems* to work - the image shows up in the WYSIWYG text area and can be manipulated there.

But when I go to publish the article, the image doesn't show up - instead I just get a fragment of HTML code. I viewed the source of the page in my browser and what Koivi appears to be generating as an img tag is this:



It looks like Koivi tried to turn the URL in the img tag into a hyperlink the way it would if a URL was embedded in regular text. It appears to have messed with some of the rest of the code inside the img tag too -- turning quotes into their ASCII entity equivalents, dropping in backslashes, and that sort of thing. So somehow it does not appear to be recognizing the img tag it inserted as an image, despite the fact that the image showed up fine in the WYSIWYG box.

However, having a vague idea what is happening does not mean that I have any idea WHY it's happening, or how to fix it...

Has anyone else encountered this? Is there any way I can fix it, or do I need to go back to the default editor if I want the image manager to work?

Strange behaviour, adding WYSIWYG to ams seems to be tricky as I experienced today. Perhaps you want try inbetween which comes with three different image-managers?

HERE you'll find a description on how to implement inbetween into ams. inbetween you'll find in the module repository on xoops.org.

Hmmm... I checked it out, but if it's based on TinyMCE, doesn't that only work in IE? I'd really prefer an editor that's not browser-specific - I think at least one of the two people who will be putting most of the articles on the site uses Firefox and possibly both of them.

Also, I'm a little wary that three different image managers will make it too complicated for them. Basically, this is an online magazine, and the two editors will be uploading most of the articles. Neither of them are all that computer-literate, so I need to keep it as easy to use as possible.

The main reason I switched it to Koivi in the first place was so that they didn't have to remember the extend tag the default editor needs, and I figured the WYSIWYG aspect would also make it easier for them. Though as it turns out they do pretty much all their formatting in Word and just copy and paste it into the editor - apparently when you copy and paste from Word, or at least their version of it (but not mine), it includes HTML for the formatting. So I need something really simple and easy to use for them.

And it doesn't appear to be the Word HTML that's messing with this, at least as far as I can tell. That was actually my first thought, but it doesn't look like it is...

The days for being IE-exclusive are over for nearly every modern javascript-based WYSIWYG-Editor.

You are not forced to use THREE image-managers. The easiest of those three is ibrowser.

The "NEW" thing in inbetween is that you can define toolsets for every group. So you can use easy-tools for beginners and super-tools for the advanced user.

Copying text from word is quite easy also. There is a plugin that strips all word-specific-formatting from the text.

Ooh, OK, that does sound cool! Sorry I misunderstood. I will definitely check that out.

My impression of TinyMCE being IE-only was based on trying it in a Mambo site I created early last year, but I guess a lot can change in that time.