TweezerMan

The instructions for how to run checksetup.pl non-interactively are contained within the checksetup.pl script (beginning at line 94): After creating the file with the above information in it, you could call it in your browser like this (assuming the above file is created as 'answers.pl' in the bugzilla directory): >http://www.my-TCH-domain.com/bugzilla/checksetup.pl ?/home/cpanelName/public_html/bugzilla/answers.pl (Line break added for readability only.)

Welcome to the forums, Dean!

Welcome to the forums, Camie!

Welcome to the forums, Filipe!

Welcome to the forums, Ron!

Welcome to the forums, Kewcee!

I am not aware of anyone who has successfully installed and used Bugzilla on a shared hosting account. You should be able to run the checksetup.pl script from a cron job, which you can set up in CPanel -> Cron Jobs. Be sure to configure a valid e-mail address in cron, as cron will e-mail the output from the script to you. Once cron has run the script, delete the cron job so the script won't be run again. I don't see anything in the Bugzilla documentation to indicate whether there would be any problems running Bugzilla on a TCH virtual hosting (shared) account. I will note though, that if Bugzilla consumes excessive server resources, or if Bugzilla is not properly secured and is subsequently compromised (hacked), your account could be suspended.

Duplicate topics merged and moved to appropriate forum. Please do not post topics in multiple forums (cross-posting) - it is against the Forum Guidelines.

Michael - TCH-Rob's comments were intended for you. A "remote directory" is just a directory on the server. TCH-Rob was suggesting that you test your FTP software by uploading one file and see what directory it goes into on the server.

I'm glad you were able to get it working! The www and public_html directories are the same directory, as www is a link to the public_html directory. The '/home/cpanelusername' part of the server path is hidden from FTP, so you would normally omit that from an FTP path setting.

1) I use ftp.my-TCH-domain.com myself. The default port number should be fine (I don't think you need to set anything for that). 2) The top level directory of your web space is /public_html. Your domain is not part of the path, so you would not include it. 3) If a log directory is created automatically, it looks to me like you don't need to do anything there.

Welcome to the forums, mizmamahaze!

1) I've seen the e-mail address showing a string of characters before - it appeared to me the cookie that stores the info sometimes gets garbled for some unknown reason. I've always just deleted the characters and re-entered the correct e-mail address, and that seemed to fix the problem. 2) MT displays the "You are not allowed to post comments." message when your IP is banned within MT. You might check the IP ban list (Weblog Config -> IP Banning) and make sure that you haven't banned yourself accidentally, or have a blank IP address banned (which bans everyone from posting comments). 3) I believe your comment form is not working correctly because there are line breaks in the comment form code that really should not be there. Some examples I see, just looking at the "View Source" HTML: This code: ><script type="text/javascript" src="http://moonjuice.us/mt/mt-comments.cgi?__mode=cmtr_name_js"></script><script>document.write(comme nter_name);</script>. ...should all be on one line: ><script type="text/javascript" src="http://moonjuice.us/mt/mt-comments.cgi?__mode=cmtr_name_js"></script><script>document.write(commenter_name);</script>. This form tag's code: ><form method="post" action="http://moonjuice.us/mt/mt-comments.cgi" name="comments_form" onsubmit="if (this.bakecookie[0].checked) rememberMe(this)"> ...should all be one line: ><form method="post" action="http://moonjuice.us/mt/mt-comments.cgi" name="comments_form" onsubmit="if (this.bakecookie[0].checked) rememberMe(this)"> All of this code: ><input type="radio" id="remember" name="bakecookie" /><label for="remember">Yes</label><input type="radio" id="forget" name="bakecookie" onclick="forgetMe(this.form)" value="Forget Info" style="margin-left: 15px;" /><label for="forget">No</label><br style="clear: both;" /> </p> ...is supposed to be on one line: ><input type="radio" id="remember" name="bakecookie" /><label for="remember">Yes</label><input type="radio" id="forget" name="bakecookie" onclick="forgetMe(this.form)" value="Forget Info" style="margin-left: 15px;" /><label for="forget">No</label><br style="clear: both;" /></p> This javascript code: > document.write('You are not signed in. You need to be registered to comment on this site. <a href="https://www.typekey.com/t/typekey/login?&lang=en&t=k1c4jseL4C5o1vs0CJFJ&v=1.1&_return=http://moonjuice.us/mt/mt-comments.cgi%3f__mode=handle_sign_in%26static=1%26entry_id=76"> Sign in</a>'); ...is supposed to be on one line: > document.write('You are not signed in. You need to be registered to comment on this site. <a href="https://www.typekey.com/t/typekey/login?&lang=en&t=k1c4jseL4C5o1vs0CJFJ&v=1.1&_return=http://moonjuice.us/mt/mt-comments.cgi%3f__mode=handle_sign_in%26static=1%26entry_id=76"> Sign in</a>'); If you go into your template and delete the extra line breaks at the places I've indicated, your comment form stand a much higher chance of working.

Welcome to the forums, dawheels!

It wasn't necessary to replace your Main Index template with Matt's - you could have simply created a new Index template and put Matt's code in there instead. I don't know what Wordpress does with a redirect.php file, but the redirect.php file outputs Redirect directives that shoud end up in an .htaccess file. There should be *no* html in the output of this file whatsoever. (I don't think you should use Matt's code with template code that contains HTML. ) Yeah, those are .htaccess directives that are supposed to redirect users hitting your old MT entry URLs to your new Wordpress entry URLs. Ummm....yes! The "/archives" URLs should be URLs to your old MT entry pages. It is a relative URL that should be equivalent to (for example): >http://www.chroniker.net/archives/79.html If your MT archives were not at URLs like above, then the redirects won't work.

The Alex King templates appear to be templates that replace MT's Individual Entry Archive template. Instead of uploading the template to your web site, what you're supposed to do is replace your existing Individual Entry Archive template with one of the supplied templates, edit the template as indicated in the instructions, save the new template, then rebuild your Individual Entry Archives. This will replace your existing Individual Entry Archive pages with pages that redirect users from the MT URL to the WP URL. For Matt's method, you don't "create a MT template in your WP root directory". What you would do is create a new Index template in MT and add the supplied code to the Template Body. Then you would set the template to *output* to 'redirect.php' in your WP root directory, and you can do this by specifying the full local server path and filename in the "Output File" field. Example: >/home/cpanelName/public_html/wp/redirect.php Save the template, then rebuild it, and you should have your redirect.php file in the WP root directory. Hope this helps...

You might take a look at that empty paragraph you have before the table: If you remove the paragraph, the table starts right at the top of the box.

Welcome to the forums, Mike!

Since this other person is in Germany, I don't think that any law enforcement (FBI) or government agency (FCC) in the U.S. would be able to help - they have no jurisdiction outside of the U.S. Since the threats were sent by e-mail, I'd suggest tracking down the ISP or hosting company they originated from and submit an abuse complaint.

I believe you should use 'https://www....' only if you have your own SSL certificate. If you are using the TCH shared certificate on the server, I believe you should use the following URL: >https://serverXX.totalchoicehosting.com/~username/... where XX=Your server number ~username = the username you use for cpanel Hope this helps...

I found this at the Wordpress site ("Common Installation Problems"):

You can add users to existing databases on that page, but I don't think this is what you need to do on this page. Usually, when you install a new script that needs a MySQL database, you perform three steps to set up the database: 1) Create a new database 2) Create a new MySQL user name (with password) 3) Add the new MySQL user to the new database This part of the page is for creating MySQL users to access your databases. When creating a user, you would not enter the parenthesis or the quotes as a part of the user name. In your example, you'd just enter wordpress. No, you won't use that section of the page for what you're trying to do. TCH has a movie tutorial illustrating how to set up a MySQL database. Hope this helps...

There's one other margin that I believe is throwing off your positioning and widths - the default margins on the HTML <body> element. Add the following to your stylesheet and see if it fixes your problem: >body { margin: 0px; }

Yes, TCH is affiliated with Wild West Domains. The e-mail you received is in response to your request to transfer your domain to TCH and from what you've described, it is a proper e-mail.

To my knowledge, a new DBD::mysql module has not been installed on TCH servers as there hasn't been a stable version of the driver available that CPanel could compile and install. To see if you're affected by the DBD::mysql module issue, run mt-check.cgi and see what version is reported for DBD::mysql (under "Checking for Data Storage Modules"). If the version reported is 3.0000, you have the buggy version of the module installed on your server. If the version is 2.9006, you're okay. If your server has the 3.0000 version of DBD::mysql installed, your best bet is to submit a Help Desk ticket and ask them to roll back DBD::mysql to the 2.9006 version. If you continue to receive the same error, then it would appear that you indeed have a separate issue with your MT installation.