MikeJ

Send in a support ticket to customer service telling them you haven't received a welcome email, and someone will investigate it and make sure you get setup. Just put "NA" for the cpanel info.

Submit a help desk ticket (link at top of the forums) and someone will look into installing GD support for PHP.

Yep. Just take index.xml and rewrite it as whatever you want: >RewriteEngine On RewriteRule ^index\.xml$ index.php?rss=1 [L] ^index\.xml = the file request to rewrite index.php?rss=1 = what you are rewriting it to [L] = last rule... don't rewrite any farther The result is that it will look like index.xml exists as a file. More can be found here: URL Rewriting Guide mod_rewrite Reference Documentation

The font does not have to be on the server. The rendering of the page is all handled locally on the end user's PC. The css file should be the correct file. Just make sure you are changing it in all appropriate sections of the css file. There are probably multiple font definitions in there.

Your web root is: /home/youraccount/public_html "youraccount" is the account name you login to cPanel with.

I know for sure that phpCollab will work on TCH servers, as I've installed this to test it for someone else who's planning on using it at TCH. If anyone wants an extended demo, I can temporarily give you admin access to play with it in my test setup before I delete it all. Just PM me.

Will do. I'll give it the full workout shortly.

? is for "0 or 1 of the preceeding text" See the RewriteRule in the reference documentation.

I think this is what you are looking for: >RewriteCond %{HTTP_REFERER} !^http://(.*\.)?yoursite.com(/)?.*$ [NC] I believe that will cover all cases of ******, subdomain.yourdoman.com...

Did you setup a list of valid email addresses that can post?

Are you asking about phpBB or phpnuke (based on your mention of a themes directory)? PHP itself is just a scripting language. Anyway, the font that is displayed is based on what the end user has installed on his PC. So if you don't have agency on your PC, you won't see agency font on the page displayed. It's best to stick with common fonts for web pages.

$MTCGIPath$ *does* change appropriately if you rebuild after changing your mt.cfg. But if your intention was to just to move the blog pages to the root of your site, you only need to change the appropriate entries in your weblog config core setup and rebuild. You didn't need to move your cgi's, you can leave them where they are installed and still accomplish what I think you want to do.

Yes. But if you want to cover the cases without the trailing slash as well: >RewriteCond %{HTTP_REFERER} !^http://(www\.)?yoursite.com(/)?.*$ [NC]

If you could post your exact rules (if there's nothing you mind making public), or PM me a copy of your exact rules, I can play with it. Even what I posted above I only did limited testing with.

Actually... Sorry, I read it backwards... looks like "./modules/Forums/images/avatars/" directory is the one that needs 777 permissions. What permissions do you have currently on that directory?

Dedicated servers are good for those who have either high volume sites, are resellers with a large clientele, or more often those who need more control of their sites than cPanel allows. You get root access if you have your own dedicated server, which you have full control of your server so you can setup the server anyway you want. To quote Head Guru himself: "We will set up the server for you including cPanel and all the extras. We will maintain the kernel and apply any software patches that are needed. Also we will assist you in troubleshooting any software issues that may arrise. Also, we maintain and replace any defective hardware that may occur. Since you are leasing the server you incur no replacement hardware. Software installs and other non-covered are billed at $65 per hour." That's compared to fully-managed which includes software installs at no cost, and unmanaged, which means you get the base server configuration and you manage it yourself. Any software support above that is done at a billable rate. The unmanaged/semi-managed plans only apply to dedicated servers. As standard web hosting customers or resellers, you are always fully-managed.

Yep. Delete it. Many of those have attachments that will try to get you to fill out and send information. It's bogus.

Lemme know if you see any more quirks like that. I never did change anything.

In particular, /public_html/includes/ will need to be chmod to 777.

http://silentcorner.com Silent Corner Random musings of a Chicago geek. Link is in the footer. Many thanks.

I agree with you on the near monopoly on certificates. As for 128 bit encryption, that's available without a certificate... most web browsers anymore allow you to accept a dummy certificate so you don't repeatedly get a warning. However, the purpose of SSL certificates isn't to tell you that a company is good or not, it's to tell you that what you requested in your browser is what you got. Without it, someone could redirect your nice 128-bit encrypted connection to their server without you knowing it, and while you thought your connection was secure to company A (say your bank account), you could be typing your confidential information to someone harvesting it, instead of the intended server.

The system php.ini isn't in your account. You can see the system php.ini active settings by creating a .php file with this contents: ><?php phpinfo(); ?> Then access that page and it will show you all of the settings. If you want to change any settings for your account, you can do so by adding lines in your .htaccess file in your public_html directory. Use the format: "php_value setting_to_change value" So, as just an example, if you wanted to change the upload max filesize, you would put this in your .htaccess: >php_value upload_max_filesize 4M

Fill out a support ticket (Help Desk link at top of page) so someone can look at it directly.

Hi Aasha, As you may have figured out in your other thread, you'd have to get an SSL certificate for the domain you are using, or change your checkout to use the shared SSL setup. It's supposed to be scary looking because it means that the SSL certificate does not match what the user requested.

Yea. SSL certificates validate to the URL requested, so you are out of luck unless you purchase an SSL certificate that matches the web address the browser requests. No level of cloaking/masking wil help there.