When upgrading from 2.0.6 to 2.0.7 did you run the upgrade script? It is located in /upgrade/xoops_206_to_207.php

Not sure with bbcode, but with HTML you should be able to use target="_self"

I'd start by doing a search for performance tuning, as this question is asked many times with generally very similar answers. In a nutshell you need look at how your webserver is configured to run PHP (CGI sux for speed, but is the way most default installs and shared hosting providers run it), install a PHP opcode cache (such as eAccelerator/APC), look at optimising your MySQL caching settings and finally configure you XOOPS caching and ensure that your theme is not bloated with images or bad HTML.

If you are using a shared host, then unfortnately it is quite likely that you will not have access to configure any of these apart from your XOOPS caching and theme. You can try asking your host about this, but if they are not prepared to come to the party then I would recommend changing hosts.

I think Monty's suggestion is pretty close to being spot on, however with the loads you are talking of there shouldn't be a need to throw buckets of money at it. The general rule of thumb I go by is that Apache (or any webserver) is bandwidth bound, PHP (or any interpreted programming language)is CPU bound and MySQL is Memory bound.

In the article I wrote about performance tuning XOOPS on IIS I took an old Althon 1.4Ghz based system with 512MB PC133 SDRAM and a single ATA-66 10GB 5400RPM HDD and took it from serving around 1100 hits per minute using the default server/PHP config to serving over 4000 hits per minute using optimised Xoops, PHP and IIS settings (I didn't even get to MySQL memory optmisations which would further increase performance). To put that in perspective with my site having around 23 HTTP requests per pageview, 4000 hits a minute is equal to around 250,000 page views (5.75 million hits) a day. With 20 people on your server only in business hours you probably wouldn't see 250,000 page views in a month.

So in your situation you are not bandwidth limited, assuming you have 1GB or so of Memory in your server you shouldn't be memory limited either, the only thing that might let you down hardware wise is CPU. Personally what I would do is setup you current server as a dedicated MySQL server (make sure it has at least 1GB RAM), and then get a dual opteron system as Monty suggested with the fastest you can afford (again with around 1GB of RAM). With the load your expecting I would not even bother with SCSI drives, it's a waste of money as once apache, PHP and MySQL are loaded into memory the disk I/O will barely be touched. For the webserver just get a couple of WD 10,000RPM SATA drives, put them in software RAID 1 (very reliable, I've done it myself for several years) or use a hardware RAID hotswap system if 100% uptime is important. Even then though you'll still need to look at apache, PHP, MySQL and XOOPS optmisations to get really snappy responses from your server as there is only so much hardware can do. Look at loading PHP as a module using FastCGI for apache, use something like APC/eAccelerator for PHP acceleration, query caching for MySQL and block caching for Xoops. Also be sure that your theme for XOOPS is not bloated with images and HTTP requests, and use CSS for layout as much as you can.

Caching will certainly help performance in CPU limit environments (such as shared hosting), especially block caching. The trick is to know what you should cache and for how long. As already mentioned ads served from external servers will also slow your page delivery time down. Depending on your current PHP environment, and you access to the server there are several other things you can do server side to massively boost performance and page delivery times. If you are using IIS then I have written several articles that will be of interest for you;

Performance Tuning XOOPS on IIS

Enabling IIS 6 native HTTP compression for PHP

If your using Apache then there are also things that can be done to boost your performance, but I am not the man to talk to for that. It might also be worth taking a look at installing these plugins I created that will show you the amount of MySQL queries and page generation time for each page. You can see it at the base of the page on my site (although the online user counter s seperate).

Page timer & MySQL counter for XOOPS 2.0.x

Page timer & MySQL counter for XOOPS 2.2.x

[extend] comes first, then [pagebreak]. SO your ariticle would look something like;
Quote:

Quote:

With AMS you must use the [extend] tag before you use the [pagebreak] tag. All [pagebreak] tags placed before the [extend] tag will be ignored.

Sorry it didn't work for you TopKnot. All you should have to do to get Koivi working is;

1) Install AMS
2) Install Koivi as per the instructions included with the Koivi download
3) Select Koivi as preferred editor in AMS preferences

Koivi is a seperate project from AMS, meaning it is a seperate download. If Koivi is installed correctly and you have sucessfully gone through the steps above it should just work. Regardless, if I were starting a new site now and were looking for an articles module my first preference these days would probably be phppp's article module.

Quote:

£110 a year!! Hell, I'd be upset too. As Jenclas said, we don't have specific taxes like this in Australia, but do have one of the higher income tax levels. I think we pay about 8 cents a day each ($29.20AUD / £12.17 a year)for our ABC (Aussie eqiv of BBC) which I don't mind paying as I hate commercial TV, but £110 a year is about $264AUD (over 72 cents a day) and I might have a thing or two to say about that.

It was a logical assumption to think the developer sent such an e-mail zioncurtain4 (I mean who else would really), so don't beat yourself up about it. My main concern now that we've cleared up that the offending email was not infact sent by Goran of 7dana, is that other people reading this thread know that and do not misjudge him by it. Goran produces some of the best and most widely used (even if modified) themes for Xoops.