Yeah, I'm having these sorts of weird problems too.

What web browser are you using?

I have tried adding articles via AMS, using Koivi editor, with both Firefox and Internet Explorer on two different machines.

Firefox has no trouble on either machine, but on one PC when I use IE it has what sounds like the same problem you are having, yet when I use IE on the other PC it has no problem!

The problem being that I can edit only the plain text input fields (like "Title", "Banner/sponsor" & "Select file"), but NOT the wysiwyg fields "Article Text" or "Extended Text". However, both those fields ARE editable if I select the "HTML" check box(es) on the bottom right corners of those fields.

This certainly indicates a problem with how IE is configured on my first PC, but I haven't had a chance to properly compare and contrast the settings with each other - I will have to try that later this evening or at the weekend.

Ok, ok, I obviously need to install kiovi. Duh!

I found it (http://dev.xoops.org/modules/xfmod/project/?koivieditor) and installed (i.e. unzipped and moved the wysiwyg/ folder under the class/ folder) and configured AMS to use it and it really looks great!!! This is going to be much easier to work with in the future for articles.

What about for XOOPS v2.0.13.2?

There is no <root path>/class/xoopseditor/ directory nor <root path>/modules/AMS/class/xoopseditor/ directory.

Also, that article you reference says "edit AMS/include/" - but that is a directory, not a file. I initially figured it must be referring to "modules/AMS/include/index.php", but I can find on references to text string "wysiwyg" in that file nor in some of the others I've tried looking in. (Note that I don't have command line access to my server, so I'm browsing files using the cPanel File Manager interface - I can't do a nice easy grep for strings)

Quote:

Thank you brash, but Koivi does not look any different to XOOPS Default editor for me.

They both have only one "Article Text" window and a "Banner/Sponsor" window, not a second "Article Text" window.

Would you be able to think of a reason for this?

Quote:

Aha! Yes, that does work now!

But the interface for the "XOOPS default" editor looks exactly the same as that of the "Koivi" one!?!

Anyway, thank you for your help!

Hi jdseymour

Well, I did wonder why AMS automatically put in an "[extend]" at the bottom whenever you edit an article, but it does NOT seem to work as you suggest. It (both the "extend" and "pagebreak" tags) simply gets displayed as though it was text intended to be part of the article.

Do you have any idea why that would be?

See:http://bluezeus.biz/modules/AMS/article.php?storyid=13

Cheers
Steve

Quote:

Thanx Dave!

Yes, started tinkering with XOOPS a few months back, but only recently had the time to get a site going with it... and also recently discovered how easy it is to use adsense.

Anyway, good luck with your troubles.
Steve

Hi

Well, what is "correctly", and how do you achieve this in a way to get AMS to show only the first paragraph?

I am having the same problem as Poslanik: i.e. AMS shows the articles on my site in full on the index page, not just the first paragraph. And I DO have Koivi as my default editor.

Help!
Steve

Quote:

Hi Dave

Thank you for the great amount of detail.

My site is on a hosted server to which I do not have full access – other than via my section of cPanel. I got them to upgrade the Fantastico version in order to get a newer version of XOOPS available for me to upgrade my site to (the intention being to overcome the vulnerabilities which v2.0.13.2 is supposed to fix).

As you will be able to see from my site, I am very new to Xoops.

As you can see above, I started on v2.0.13 [which was also installed via Fantastico]. The Fantastico upgrade by my hosting supplier made an XOOPS upgrade to v2.0.13.1 available, and I saw here [https://xoops.org/modules/core/singlefile.php?cid=3&lid=118] that the update patch to upgrade from v2.0.13.1 to v2.0.13.2 seemed pretty simple to apply, so I decided to go ahead with this.

I did a full backup of my site and went through the upgrade process to v2.0.13.1. I did have some directory permission problems [which my hosting supplier helped resolve – I guess the Fantastico upgrade script wasn’t quite thorough in the directory permission area – the web service process owner account’s group needed write permissions added for a few directories] but it seemed to have gone smoothly after that was fixed.

So then I did the update to v2.0.13.2 – which involved simply unzipping the zip file in my site’s root directory.

It was only then that I noticed the duplicates in the Web Links section. I suspect it most likely occurred as a result of the upgrade from v2.0.13 to v2.0.13.1, since the path from there to v2.0.13.2 didn’t seem to be as intensive a process.

At this time I am reluctant to try install the v2.2.3 since I don’t have full access to the server and this version is obviously too new to have made its way into Fantastico yet (or at least the version my hosting supplier has available to them).

Anyway, my site is still quite in its infancy [I’m still working out what works, what doesn’t, what might be better, etc], and it seems the simplest fix will be to remove the duplicates at the database end. I’d rather not go the route of something too much more involved than that at this time, if it is avoidable. Unless som “greater power” can suggest something better!?!?!!?!?!?

It is great to have such thorough feedback though – thank you again!


Cheers
Steve

P.S. By the way, for what it’s worth, I am using these modules:
- ForumEx (“Newbbex”)
- iMenu [well, it is installed, but not actively being used yet]
- Article Management System (“AMS”)
- News
- Links (“Web Links”)
- Contact Us
- Partners
- FAQ
- XHLD (“Headlines”)

Hi Dave

Yes, your problem looks like what I am having.

And you are right: if I go and look at the MySql table "xoops_mylinks_text" that sure is where the records are duplicated.

So does it seem to you that the only way to sort this out is by removing the duplicated records in this underlying database table "xoops_mylinks_text" by hand?

This will obviously be a "hack" of a fix. If there is no other way, then I guess I will have do that to fix this problem.

But surely this is an indication of a problem / bug that needs fixing in XOOPS – or is it just in the "Web Links" module? Do you think that the "Template Set" problem is a related bug? Or a completely different one?

Cheers
Steve