Tony

Did you install the forum via fantastico? Usually what you'd do is set the path to blank so it goes into the root. Now if you uploaded the files yourself than you could just move them since you have nothing to worry about in terms of fantastico breaking.

The root directory most likely has an images folder. You should remove it then you should be able to install joomla via fantastico.

I am blind and didn't see what the original code was doing. But for anyone curious the issue is with the PEAR loader system which seems to be locking the include path for some strange reason. Just disabled it globally since no one uses it anyways.

Well I suggest you make a ticket I have no idea what server you're on. I've tested ZF on a few machines and it has no such issues.

Well what you've shown shows that it is using the include paths without issue. So I'm wondering are you relying on our Zend Framework? You need to keep in mind we're always updating to the latest. This is why we suggest if your code is production or may be ZF version sensitive you upload your own copy.

set_include_path has not been disabled on any of our servers. Have you tried a simple example to see if it's the include path problem or something else?

Assuming everything checks no more than an hour. If you pay via paypal e-check a little longer as we look more closely at the payment and information given.

Neptune is now running LiteSpeed.

Once you order it we could have it done within 24 hours depending on the size of your site. IRC is not running through our server so it would be better.

No No No Our acceptable use policy states no shoutboxes. Now this is more to protect us from a site with a lot of visitors putting one up. But overall they are very poorly made and make a site with very few visitors like the one you describe be a heavy hitter. You need to ask yourself is your site a forum or a chat site. Every time the shoutbox refreshes that is like having a pageview on your site. I've seen a 1000 visitor a day site generate 100,000 pageviews a day through their shoutbox. So I'd really advise against it or at least put it on one page only viewable to members. That is more reasonable then being on every page and viewable to anyone. That should be fine. We allow a maximum of 25 concurrent connections and the MySQL space usage is counted against your total usage. As far as databases we have no limit on the number but as I said it all couns against your total quota.

On Monday January 5th starting at 11:00 am EST we will be migrating the Skyline server from using the Apache web server over to LiteSpeed. We're saying it's going to take us three hours to do this migration but we doubt it'll actually be even remotely that long. We do not expect any down time so the migration time should have no impact on anyone. Once we have LiteSpeed configured on the server we will switch the server to use LiteSpeed. If we do run into any problems we can switch back to Apache with just a few clicks on our part. You can find information about LiteSpeed by visiting our blog post Should We Switch To LiteSpeed? as well as our forum post Should We Switch To LiteSpeed? We hope no one has any issues once we're switched over and their web sites are loading even quicker than usual. Date: 01/05/2009 Start time (EST): 11:00am End time (EST): 2:00pm Estimated Down Time: None Duration: 3 hours

NS2 has been shutoff as per our notice. NS1 will be going down on Monday January 5th.

If you're forcing .html files to be parsed with .php the best method is to use AddType application/x-httpd-php5 .html [/CODE] This is a very silly way to produce .html to be shown to the users address bar. The best way to accomplish this and support any php configuration and any web server using mod_rewrite would be to rewrite .html -> php script. So for example something like this would work much better: In your .htaccess file you have: [CODE] Options +Indexes Options +FollowSymlinks RewriteEngine on RewriteBase / RewriteRule ^([^.]+).html$ $1.php [L] I am pretty sure that'll work and any .html will go to the .php equivalent. Now longer any headaches of handlers or anything of that nature.

Saturn is now using LiteSpeed for it's webserver

The other question was answered and I can confirm whether shared or reseller hosting it's easy to upgrade. Now as far as helping us out a great way is to post a solid review. We get quite a bit of traffic from sites like http://www.webhostingstuff.com/ and http://hostjury.com/ to name two but I'm sure there are others. More reviews on sites like these help us out quite a bit. Never hurts to post your thoughts in a blog post on your site or something like that. Now as far as powered by logo's or anything like that. Just wait until we have a new site and everything. We're going to have a mascot an awesome logo and a powerful interactive site. I just can't wait until it all comes together.

I'm going to close the topic as this has been completed. Everything still is looking fine and CPU and memory usage is lower as expected. Pages are probably loading slightly faster but it's not something you'd notice unless you benchmark it.

Jupiter is now running on LiteSpeed. We're actively monitoring the server now to make sure everyone is running fine.

You may no longer override php values using a php.ini. You must use a .htaccess file with php_value varname newvalue . For example: php_value register_globals on Would turn on register globals.

This a topic dedicated to potential issues you could experience due to the migration over to LiteSpeed.

It'll happen on any invoice paid moving forward. If you already paid it's not going to effect you until you renew. Now as far as the dollar amount. We charge USD and we'd take 5% on the paid amount. If we charged you the CAD amount on your hosting we'd still take the same amount in GST because your hosting plan is now say $15 instead of $10. I hope I explained this well enough basically the way the math works 5% charged on the CAD amount be the same as the 5% charged on the USD amount once you convert it all to CAD.

This has been completed. We were able to keep the same raid card type so no data loss occurred.

We're going to be doing maintenance on the bosco server tonight which currently acts as our backup machine. We'll be swapping out the memory and raid controller of this server as we believe they may be causing problems resulting in backup corruption. It will take us from 10:00pm EST until 12:00am EST to swap the parts. Once that is done we will most likely formating the machine if the raid card is unable to pickup the old array properly. So please keep in mind we will be wiping out all the backups and we will not have the usual 7 days retention. This is unfortunate but we need to solve the corruption problems and switching of the raid card will most likely mean we'll need to make a new raid array and as a result format the machine. If you have any questions about this maintenance window do not hesitate to contact us. Date: 12/22/2008 Start time (EST): 10:00pm End time (EST): 12:00am Estimated Down Time: 2 hours Duration: 2 hours

On Friday January 2nd starting at 11:00 am EST we will be migrating the Neptune server from using the Apache web server over to LiteSpeed. We're saying it's going to take us three hours to do this migration but we doubt it'll actually be even remotely that long. We do not expect any down time so the migration time should have no impact on anyone. Once we have LiteSpeed configured on the server we will switch the server to use LiteSpeed. If we do run into any problems we can switch back to Apache with just a few clicks on our part. You can find information about LiteSpeed by visiting our blog post Should We Switch To LiteSpeed? as well as our forum post Should We Switch To LiteSpeed? We hope no one has any issues once we're switched over and their web sites are loading even quicker than usual. Date: 01/02/2009 Start time (EST): 11:00am End time (EST): 2:00pm Estimated Down Time: None Duration: 3 hours

On Wednesday December 31st starting at 11:00 am EST we will be migrating the Saturn server from using the Apache web server over to LiteSpeed. We're saying it's going to take us three hours to do this migration but we doubt it'll actually be even remotely that long. We do not expect any down time so the migration time should have no impact on anyone. Once we have LiteSpeed configured on the server we will switch the server to use LiteSpeed. If we do run into any problems we can switch back to Apache with just a few clicks on our part. You can find information about LiteSpeed by visiting our blog post Should We Switch To LiteSpeed? as well as our forum post Should We Switch To LiteSpeed? We hope no one has any issues once we're switched over and their web sites are loading even quicker than usual. Date: 12/31/2008 Start time (EST): 11:00am End time (EST): 2:00pm Estimated Down Time: None Duration: 3 hours

On Monday December 29th starting at 11:00 am EST we will be migrating the Jupiter server from using the Apache web server over to LiteSpeed. We're saying it's going to take us three hours to do this migration but we doubt it'll actually be even remotely that long. We do not expect any down time so the migration time should have no impact on anyone. Once we have LiteSpeed configured on the server we will switch the server to use LiteSpeed. If we do run into any problems we can switch back to Apache with just a few clicks on our part. You can find information about LiteSpeed by visiting our blog post Should We Switch To LiteSpeed? as well as our forum post Should We Switch To LiteSpeed? We hope no one has any issues once we're switched over and their web sites are loading even quicker than usual. Date: 12/29/2008 Start time (EST): 11:00am End time (EST): 2:00pm Estimated Down Time: None Duration: 3 hours