Ashoat

Okay, I think it's time we changed some things around on HelioNet. This place is filled mostly with spammers who aren't able to read big red text. Also, HelioHost is getting too slow. That needs to be changed. Here are the changes I am going to make sometime in the next few months: Change HelioHost a bit. HelioHost is pretty slow, and needs to be updated.Get a new server. I'm going to finally purchase a server, instead of renting one. This server is going to get colocated, and it is going to have a quad-core Intel Core 2 Duo processor, 8GB of RAM, and 1TB of HDD space.Remove ads from user-pages. That means you don't have to post on the forums to get no-ad hosting. This will be lessen spam here, and will boost our ratings way up to #1 on the biggest directories. This means much more members, which neccesitates more moderation (see point #2).Allow linking of HelioHost accounts with HelioNet forum accounts. This will make customer support easier. Also, I'll upgrade the signup script a bit... namely, have it check IP addresses, allow domains other than .com, .org, and .net, and email each user when their account is validated.Add new scripting languages on the new server. I'm hoping for Python, Ruby, Ruby on Rails, and JSP on the new server, along with our current PHP, SSI, ASP.NET, Perl, CGI, and FrontPage extensions. I'm getting rid of ASP, as it is outdated.Add account moderation. Staff members (see below) will be assigned a number of accounts that they will need to monitor for illegal activities.Change the HelioHost web site. The site is outdated. Its "1337" image is outdated and attracts immature posters while detracting mature ones. Furthermore, the Flash format is bad for indexing, the intro is annoying, the site is way too small, and it isn't visual enough.Fix up cPanel. cPanel has that annoying ad at the start and has most of the content in bad positions. I'm going to fix those issues.Make cPanel auto-update email changes to the account DB and limit cron in cPanel. I'm going to synchronize cPanel email records with my own records in the HelioHost account database. Also, unlimited cronning is a big problem. I'm going to limit cron to a maximum of two crons, each running a maximum of once an hour.Push moderation way up. I'm going to: Add more staff members. Staff members' jobs are going to be to manage and watch HelioHost accounts, to moderate early users' posts (see below), and to generally keep posts high quality. They are going to watch HelioHost accounts through a console where they will check the user's webpage and their CPU usage.Force moderation of all new users' posts. That means that if somebody doesn't make a really good first ten posts, they will be banned.Make moderation easier. I'm going to put some AJAX moderation tools in topic view for moderators, so that they can easily put a user on probation, fine them, ban them, and warn them.Make points harder to get. It's too easy to get points nowadays. I'm going to fix this by:Cutting down the number of forums. Some forums on HelioNet are useless and barely contribute to the community. I'm going to get rid of them.Take down the interest level. This allows people with 100 posts to get domains. Not really fair.Make points based on post length and topic creation. This means that a short post will be worth 3 points, while a long expansive one will be worth more like 20 points. We will NOT allow copying and pasting of content to get long posts and therefore more posts.Also, I need to update the purchasable items in the store. Since Posting Standard accounts are now the same as the normal account, they should be removed. As for Posting Plus, I should just make "more space" and "more bandwidth" items available.Eliminate the points and store systems. Since the points and store systems no longer serve any real purposes, they have been eliminated.Gray = done Yah, that's all I can think of for now.

Put a "Hello, world!" program into your public_html and give me the URL so I can check it out.

As I said, I have no clue why this is happening. It is probably something having to do with the upload libraries your scripts use. Find a forum or support site dealing with those and ask them if they know anything. If they say you need root or shell access, post the URL here and I will take a look at what the fix requires.

ASP files only work in the public_html folder. They can include files in the other folders, however. So, just make a wrapper ASP file and put it in the webroot (public_html).

We don't have any quizzes currently.

I have no clue what the problem is. It's probably function-specific - check the PHP manual.

The only disk space quotas available are listed at heliohost.org.

Yah, I am aware that it takes a while sometimes. I've modified it a bit for ads and status indicators. However, I'm pretty sure it shouldn't be taking two minutes - trying refreshing again. Are you using dial-up?

They are down, and probably will remain that way for a while.

Can you give me the URL of the script?

I'm pretty sure that we have Python. Make a .cgi file and declare Python in the first line.

Are you declaring the perl directory on the first line?

I'll ban you too.

I have no clue what you are talking about. Please try explaining the problem using standard English.

I'd ban you.

See if the extensions work now.

Hmm, I'm not sure. I've never really worked with Frontpage Extensions. Were you installing from cPanel?

I can delete your account, and you can then setup a new account with the same username and domain...

Check the CNAME now.

It's not that big of a deal. The CNAME has been changed.

I doubt command line would help. It seems like a permissions error. It might have something to do with suPHP... we'll see what cPanel has to say. EDIT Nevermind. Looks like the error I was having was because I was logged in to two accounts simultaneously, and the error saidinstouch was having was probably due to some late validation thing.

I checked it out... looks like a weird error is happening. I'll ask around the cPanel support forum. I'll let you know if they have any ideas.

ASP.NET has built-in support for ASP, as far as I know. Note that ASP files that are being executed (ones that are being included don't matter) must be in your DocRoot (public_html/www).

Unfortunately, we're set at 8MB. 20MB is a really huge number - you're going to need a paid host if you want something like that.

I have absolutely no clue what's going on. Sorry Best to post on a MySQL support forum - maybe they would know what's going on. If it's a problem from my end that I can fix, let me know.