You don't need to close the extend tag, and you only need one. All the extend tag does is define what AMS should use as the article introduction. I.E, what ever is before the [extend] tag is used as the article introduction, and whatever is after it is the main body of the article.

If you are using Koivi, then you should not be using the extend tag at all as you should have two seperate text windows when submitting articles. The first one is for the article introduction, and the bottom one is for the main body of the article. You will still need to use the [pagebreak] tag using Koivi if you wish to paginate your article.

How do I submit and article?

I'm getting the same issue as your here animas with the "You have already replied to this survey" message appearing above the header, but this is not the only one. If I try and access the survey module without any active surveys, then a "Errors
Form inactive" message appears above the header in the same way. Also, if I reorder a survey's questions then a "Survey Reordered" message appears above the system admin icon in the XOOPS admin panel. I've tested this on two different systems, both of which are IIS 6, but one running PHP 4.3.11 and the other is PHP 4.4.0. The behaviour is the same on both.

I think that is probably some pretty good feedback kalpax, and I hope the docs that the others pointed out to you help you out. Having been here for quite a while now I can see that forum based support for the beginner does not seem to be as accessable as when I first joined. In saying that though there are a LOT more tutorials available thanks to people like jdseymour, and carnuke & co have done a great job with the FAQ's. As an old timer I find that I just get really bored with answering the same old questions over and over, so in the ned I just don't do it. This would be helped with your suggestion of more comprehensive documentation, but creating that is dependant on available man power. Over the last few years it seems that there aren't as many people coming up through the ranks who then stick around to help others out either which is probably compounding the issue. Perhaps if it is a point of concern for you could make it your pet project and create some documentation from a beginner for a beginner as you go along. One thing that is hard for more experienced users when creating documentation is being able to view XOOPS through a beginners eyes.


@Fastian

You can't require someone to create documentation, you can only encourage it. This was what was the driving force behind the QA team was...

Compatibility woth PHP 5.1 will be another thing you'll need to look at lasergazer. With XOOPS it's general not a large wait until the core is brought up to spec, but some of the modules submitted can lag behind a bit, and sometimes never get updated at all. What I am trying to say is that unless you are a coder, or have a budget to burn on hiring a coder, then I would be looking to get the functionality you need as one of your primary selection criteria. If your server is even only of moderate specs and is configured correctly, then speed shouldn't be a huge issue for you unless you are serving 10's of thousands of visitors an hour. I wrote a guide on performance tuning XOOPS on IIS where I got up to a 1000% increase in performance in some cases, with over a 300% increase in successfully served HTTP requests over the default values. All these gains were made without touching a single line of XOOPS code.

Once you get a bit more familiar with XOOPS and being a webmaster mlb160, you may also find this article I wrote to be of interest to you;

Implementing PhpAdsNew into your XOOPS site

PhpAdsNew is the best open source PHP based ads management server there is, and if you wish to start using advertising in any kind of serious way is definitely worth a look.

Also, you might like to have a look at the guide I wrote here;

Maximising your Google Ads revenue with Xoops

No problem . I see you've discovered IIS-Resources (I am part owner) so you'll always be able to get PHP/IIS help there. If your interested in performance tuning PHP on IIS I have also written a bit of an article on it which can be found here.

Have fun

Glad you got it . When looking for php.ini PHP will first look in the directory specified in the %PHPRC% variable, and then if nothing is there it will look in the directory specified by the %windir% variable.

Have you verified that the MySQL extion is loading? Removing the ";" should be enough, but if there is some other issue with your PHP.ini config (such as extensions path) then it still might not be loading. Type the following into a file and call it something like phpinfo.php and then place it into your XOOPS root.

When you access this file does it say MySQL support is enabled?

There is nothing wrong with running PHP on IIS, I've been doing it for years and it has been both very fast and very stable. I'm also a Microsoft IIS MVP, so I won't be switching to apache in a hurry .

@ Zaphod

You will be getting that error because you are running PHP5 where the MySQL extension is not loaded by default. Open up your PHP.ini file and find this:

Once you find that remove the ";" from infront of it and restart IIS.