MikeJ

When you use "virtual" includes, it basically makes another call to the webserver, so the webserver needs to know how to handle it. So, if the file your including is "/somedir/somefile.pl" for example... if you go to "http://localhost/somedir/somefile.pl" with your browser, the output you get is the same as what the include will get (which I believe in your case would be just source code). There's basically 3 ways to correct this (exclusive of each other)... Put the perl script in a ScriptAlias directory (like /cgi-bin). It's already setup to execute CGI's. Add something like "AddHandler cgi-script .cgi .pl" to your httpd.conf file. This will allow cgi's with those extentions to be run from any directory. Enable "ExecCGI" for the directory you have the script in (see apache documentation for ways to do this). Number 2 is probably your simplest option, and would be a good choice to make your environment better match TCH's.

The same thing that Robert mentioned: RewriteCond %{HTTP_REFERER} !^$ That line basically means "On condition Referer is not <blank>", since ^ = beginning of string, and $ = end of string with nothing inbetween when speaking in regular expressions. ! is your NOT statement.

Couple lightweight ones off the top of my head: PunBB ( http://punbb.org ) MiniBB ( http://www.minibb.net/ ) I haven't used either, you'd have to look to see if they have the features you want.

You know, Thomas.... I look at that picture, and now all I want to do is take a nap. Thanks.... <_<

Redirect hotlink and allow direct requests are unrelated items. If you don't input a redirect, the user will get get a forbidden error (or a broken image if it's inline to a page) if the referrer is from a non-allowed site. Whether you redirect or not won't affect the ability to request the image directly... only what happens in the event it fails.

Nevermind.... found the server was missing a MIME type definition.

Nothing to do with TCH... Anyone here happen to have worked with serving VoiceXML under IIS before on Windows servers (particularlly IIS 6 on Windows 2003)?

Or easier yet, just select "Allow direct requests" when you enable hotlink protection through cPanel. Anything referenced in a CSS should, I believe, still have a referrer to it (as long as the browser is sending referrer info). In general though, it's a good idea to allow direct requests as some browsers and proxies won't send referrer information.

On shared hosting, what's more important then processor speed is how many sites are on the server for the power it has. While TCH doesn't disclose how many sites they allow per server (no hosts really do), TCH put less domains per server than average in order to insure that your site remains quick.

Correct. TCH is not a reseller. TCH owns its hosting servers, and has colocation space in several datacenters.

Mainly just because they are busy at the moment with other matters. Remember the forums is not the main method of support, which is why when possible the forum mods try to answer as much as possible so the staff don't have to spend a lot of time here responding. So don't mistake lack of a response by Head Guru or staff as a lack of concern or any lack of action being taken. As for GroovyFish's link, that's the normal way their service works. The question is how a link to it showed up (there's never supposed to be). That'll take some investigation with the domain service.

Yea... I have an idea what happened, but I have to wait for my new registration to go through to "test" it. Anyway, this is clearly a problem that happened with the Domain partner, combined with the error that the user registering made by picking domain parking instead of Hosted at TotalChoice (which was the default, btw). The domain partner does branding to show TotalChoice, and somehow the user ended up on the domain partner's hosting pages which aren't supposed to be accessible for a TCH customer. Since he carried the TCH branding through, the hosting pages all looked like they were TotalChoice and he signed up on that premiss. So the problem was really that the customer changed the default setting of being hosted at TCH and instead chose to park the domains. Then it was compounded when he probably went back to change it and was given an option somewhere to host at the domain partner, branded as TCH, which is never supposed to show up (if I manually go to their hosting page with the TCH branding info in the URL, I see exactly what the screenshots above show). So he never actually signed up for hosting at TCH.

Hi Ven, Invision Board installer is located in your Scripts Library. If you don't see it, submit a help desk ticket to have someone enable the installer on your server.

Random usernames protect against hackers who attempt to bruteforce accounts that may have common or easily guessable usernames. Basically, it's a security measure... it helps protect your account from being compromised. Btw, if you ever forget your username, just submit a helpdesk ticket (put dontknow for the username) and someone will help get you the info.

http://example.com/webmail (where example.com is the domain they are in) They can change their password from the webmail client selection screen.

It looks like you got it now. The extension was in all caps (.JPG).

If you don't mind providing the URL, that would help greatly to diagnose.

Ahh...sorry, I didn't notice the "cgi-sys". That's a system alias. Submit a support ticket to have a tech investigate that server for abuse and possibly remove that script from the system.

Actually you do have a formmail clone installed: http://www.blackcat.bloggy.biz/cgi-sys/formmail.pl If you aren't using it, you should remove it.

I didn't say I'm not continuing, just that I don't meet with the committee on a biweekly basis like I did last year. I'm still looking at getting something in place for online donations, and I'm still quite involved. You can take CC numbers through your site securely, but that will required SSL certificate, as well as a secure database (basically make sure the information is not retrievable). You also take additional risk, however, if you store credit card numbers. If you use a payment processor, it's typically better to pass the credit card number straight to the payment processor (without storing the number on your server at all), get an authorization code from the payment processor, and only storing that.

Send your request into the help desk explaining what you want, and they can review it for possibly setting it up for you.

Not yet. I opted out of being on the event committee this year due to lack of spare time (just sticking with rider support and riding this year) so I don't get immediate feedback from the committee, and I also want to try to get something in place that will be a good multiyear decision, so I'm taking my time to research the options. I'll let you know what does pan out. All the options mentioned above have some merit to them.

As everyone stated, blogs are much more geared to "publishing" and forums are more geared to "community conversation". You can have community conversations in a blog but it takes more work (most blogs comment systems are meant to be easy and simple, and therefore tend to be somewhat primitive), and you can have a forum publish, but again, it takes a little more work. I have, however, seen people take the best of both worlds.... A blog for publishing entries, and then replaced the comment system of the blog by incorporating forum software into the comments. Not recommended for those new to either though as that takes a bit of configuration to make it work. Bottom line, though, if I were trying to decide between a blog and a forum... my primary basis would be on who is going to be creating the topics. If there's only 1 or very few authors creating the articles/topics (and then anyone can respond in comments), I would lean towards a blog. If you want anyone to be able to create topics for conversation, then a forum may be more appropriate.

Here Birdy!

Just to put a confirmation to that, yes, it only compresses text. Most images are already compressed, so attempting to compress them further would likely have a negative overall performance effect.