Tony

This has been completed.

This is starting now it might actually take up to an hour to complete. Nothing should go down during that time though.

This has been completed. It took a little longer than expected but nothing was ever done it just took ages to rebuild everything and re-generate the configuration files.

This has been completed.

Our backup systems are currently located in Dallas so as a result on March 28th starting at 3:00AM CDT you will be unable to restore from backups. The reason being there is private network maintenance going on in Dallas. You can find the specific maintenance notice below: http://www.hawkhost.com/forums/showthread.php?t=353 Date: 03/28/2009 Start time (CDT): 03:00:00 End time (CDT): 05:00:00 Services affected: Backup Systems

Datacenter Engineers will be upgrading the IOS and rebooting the backend / private network routers across the Dallas network on March 28th 2009 starting at 3:00am CDT. During this window backup restorations will not be possible as our servers will be unable to communicate with the backup system as this is all handled over the back end network. Date: 03/28/2009 Start time (CDT): 03:00:00 End time (CDT): 05:00:00 Services affected: Backend/Private network

On Saturday March 21st at 2:00pm we will be upgrading the Mercury servers PHP to 5.2.9. We do not expect any down time during the maintenance window. We will be upgrading the system PHP to 5.2.9 first then the web servers so for a short time there may be different versions handling command line cronjobs. This should not affect anything but we figure it's worth noting. If you have any questions about this maintenance window do not hesitate to contact support. Date: 03/21/2008 Start time (EST): 2:00pm End time (EST): 2:30pm Estimated Down Time: None Duration: 30 minutes

On Saturday March 21st at 1:30pm we will be upgrading the Mars servers PHP to 5.2.9. We do not expect any down time during the maintenance window. We will be upgrading the system PHP to 5.2.9 first then the web servers so for a short time there may be different versions handling command line cronjobs. This should not affect anything but we figure it's worth noting. If you have any questions about this maintenance window do not hesitate to contact support. Date: 03/21/2008 Start time (EST): 1:30pm End time (EST): 2:00pm Estimated Down Time: None Duration: 30 minutes

On Saturday March 21st at 1:00pm we will be upgrading the Skyline servers PHP to 5.2.9. We do not expect any down time during the maintenance window. We will be upgrading the system PHP to 5.2.9 first then the web servers so for a short time there may be different versions handling command line cronjobs. This should not affect anything but we figure it's worth noting. If you have any questions about this maintenance window do not hesitate to contact support. Date: 03/21/2008 Start time (EST): 1:00pm End time (EST): 1:30pm Estimated Down Time: None Duration: 30 minutes

On Friday March 20th at 2:00pm we will be upgrading the Saturn servers PHP to 5.2.9. We do not expect any down time during the maintenance window. We will be upgrading the system PHP to 5.2.9 first then the web servers so for a short time there may be different versions handling command line cronjobs. This should not affect anything but we figure it's worth noting. If you have any questions about this maintenance window do not hesitate to contact support. Date: 03/20/2008 Start time (EST): 2:00pm End time (EST): 2:30pm Estimated Down Time: None Duration: 30 minutes

On Friday March 20th at 1:30pm we will be upgrading the Neptune servers PHP to 5.2.9. We do not expect any down time during the maintenance window. We will be upgrading the system PHP to 5.2.9 first then the web servers so for a short time there may be different versions handling command line cronjobs. This should not affect anything but we figure it's worth noting. If you have any questions about this maintenance window do not hesitate to contact support. Date: 03/20/2008 Start time (EST): 1:30pm End time (EST): 2:00pm Estimated Down Time: None Duration: 30 minutes

On Friday March 20th at 1:00pm we will be upgrading the Jupiter servers PHP to 5.2.9. We do not expect any down time during the maintenance window. We will be upgrading the system PHP to 5.2.9 first then the web servers so for a short time there may be different versions handling command line cronjobs. This should not affect anything but we figure it's worth noting. If you have any questions about this maintenance window do not hesitate to contact support. Date: 03/20/2008 Start time (EST): 1:00pm End time (EST): 1:30pm Estimated Down Time: None Duration: 30 minutes

The problem with private name servers is no domain registrar has the same setup to create them. Godaddy calls it host summary, name cheap calls it something else ect. ect. So we just give the IP's you should use and most know how to do it if not we at least point the person in the right direction.

ajax based shoutboxes are still generating excessive page views. Every ajax request is actually requesting a page so maybe shoutbox.php. So the user is still accessing the pages even if to them nothing is reloading.

Thanks for spotting that. The old site it was http://www.hawkhost.com/Policies/tos and we switched it to http://www.hawkhost.com/Legal/tos so I updated the order system to reflect that. It was the only url we changed of course

I'm no expert on emailing it to yourself but I believe you'd have to make a php or perl script to do it. Dumping the database to the home folder be easy as that could be done entirely from the command line so entirely cron. The email portion is where I think you'd need php or perl.

That is exactly what I am trying to avoid doing. The client area works great that way due to how it's designed. The support system is terrible when doing that and we used to wrap it. All sorts of design elements broke within it as well as it breaking the design itself. For a forum I am not a big fan of doing that as in most cases it just ruins the functionality of the forum if it has to be made smaller. I have no issue with it taking aspects of a design but that's as far as I'd go. A blog well I don't see much point in having it match a design. That's just me though We'll see though maybe all three will be integrated I do not know at this point.

The problem in this case was the user had a .html file accepting POST requests which is not possible. Depending on the ISP and browser it would produce an error. As for your issue CGI is handled fine so that does not make a whole lot of sense that it did not work.

1) Nope 2) Well depending on how popular your forum is it may become a problem for you. If your shoutbox is using a lot of resources it's going to cause problems just for your account. We're not going to disable your VPS for having one but you'll make your VPS slow if it's using all your resources.

Everything should now be fixed unless I missed something. The typo's were easy. The IE specific bugs not so much but I hacked together a solution to the right menu not showing up properly. I had to switch the padding of each option from 10px to 8px in order for it all to fit. The headings on the comparison pages was another css fix as the headers specified a width then used colspan. This would produce unpredictable results so I removed the width specification and that solved that. The floating buttons I cannot find where that happens as it looks the same for me in Internet Explorer, FireFox and Opera. As for the forum and blog I'd love to have matching designs for both. So I'll see about getting around to having that done. I am not talking about using the actual design and throwing the forums or blog into it. I am just talking about the same color scheme and logo so that updates to either software will not break the design (I hate having to switch it constantly).

Thanks for the suggestions and issues you've found. Fixes will probably show up tomorrow. Right now some other things have taking priority.

Fixed it was suppose to be Pluto but when I copied the row in the database I forgot to change the name. Fixed That's what happens when you forget a page then last minute write something up in an IDE without any sort of spelling or grammar checks

The new site is live granted a few things are not 100% going as of yet. Post if you find any bugs or have any suggestions.

It's up proved you all wrong

It might be a better idea to use your domain to connect in case the server you're on ever switches or you switch providers or anything like that. I'd hope that's never the case but always a good idea to have it set to something you'll never change.