mtiwebmaster

I'm in the process of migrating a website to TCH from another hosting service. I have a bunch of Perl scripts that were working perfectly on the other host, but I'm having trouble getting them running on TCH. When I check the error log in cPanel it says: "Premature end of script headers: <path to script file>" I'm wondering if the shebang line that points to the perl interpreter is different on TCH. On the old host #!/usr/bin/perl5 worked. Does it need to be something different on TCH? I'm I barking up the wrong tree? I've never seen this error message before. Thanks in advance for any help!

I'm not sure if this is the right forum for this topic, but here goes. I just signed up with TCH. I am the webmaster for a community theater group, and we currently have a website on a different hosting service that we are looking to migrate to TCH. It provides information on our group, upcoming productions, and allows patrons to purchase tickets, etc. My problem is that I need to get everything uploaded to the TCH host and test it out before changing the DNS entries for our domain so that they point to the TCH servers. I have uploaded some of our pages to the TCH server using the "<IP address>/<username>/". I can access the pages there, but the problem is that all of the internal links are wrong. If I have a link that starts with a "/", the server tries to find it in the document root, which appears to be /usr/local/apache/htdocs. Of course, the file doesn't exist there, it's in /home/<username>/public_html. I can't change all my links to relative links (not starting with "/") because many of them are in php include files which are included into files that are at various places in the site's directory hierarchy. I'm told the document root will change to /home/<username>/public_html when I switch th DNS entries and am accessing TCH's server through my domain name. So I have a chicken and egg problem. I can't test out my site until I switch my DNS entries to point to TCH, but I don't want to switch the DNS entries until I have tested the site. Any suggestions? I can't believe I'm the first one to come across this problem! Erick Pew Music Theatre of Idaho webmaster

I didn't set up our account with our current host (in fact I've never gone through this process before) so I wasn't aware exactly how the SSL was working there. After some digging I've discovered that we don't have our own certificate, but are instead using shared SSL on the current host. I'm thinking we will want to go the same way here since it is free. So with the free shared SSL with TCH, when you link to a page through the https://www.sslX.com/userid URL, is the www directory still the root directory? In other words, if I wanted to access a page that was in www/ssl/somepage.html, would the URL be https://www.sslX.com/userid/ssl/somepage.html? Just trying to make sure I understand how this all works! Also, is the free shared SSL enabled by default on all TCH accounts, or do I need to request it when I sign up? Thanks, Erick

I have a couple of questions about how TCH handles secure sites. With our current host, the secure portion of our website is accessed by our customers through a totally different url, as opposed to being under our own domain name. Would that be the same with TCH? It's not a big deal since the customer is normally accessing the secure stuff through links from the non-secure pages, but I was wondering how it works here. From my point of view as webmaster, when I ftp in to our current site there are two subdirectories: www for non-secure stuff, and ssl for secure stuff. How does that work with TCH? Lastly, how do I go about transferring the certificate from our current host? I wasn't the webmaster when the site was set up, and I'm not even sure where they got their certificate from, so I'm not real familiar with how this process goes. Thanks, Erick Pew Music Theatre of Idaho webmaster

I'm the webmaster for a community theater company. I'm looking at moving our website from our current webhost (not happy with there performance), and I'm wondering about some of the issues involved in this process. I'm aware that I will need to modify the DNS entries with our domain name host, and I'm aware that it takes a period of time for the new entries to propagate across the net. I'm assuming that before I make the DNS changes I would be able to upload our files to the your host using the IP address directly. Included in our website is an on-line ticket purchasing system. I'm wondering how to handle transferring the sales database for this application (it's currently implemented just through flat filesystem files, although I'm hoping to move it to MySQL on the new host). I'm assuming that there's some (hopefully short) period of time as the new DNS info is propagating out that I can't be sure which host a user will get when they type in our domain name. Is that correct? I'm guessing that what I will have to do is disable the ticket ordering pages on the old host, transfer the database files to the new host, and then make the DNS changes. Now if a user gets the old host from an old DNS entry they will just get a page telling them the ticket ordering service is temporarily down, and if they get the new host they will be able to go ahead with the order and the data will be recorded on the new host's filesystem. Did I miss anything here? Will this work? How long should I wait for the DNS info to percolate through before I cancel my old hosting account? Also, what's the best way to get all the files transferred from one host to the other? Will I have to download everything to my personal computer, and then upload them back to your host, or do you have some utility that will easily ftp the files straight across from the old host? Thanks in advance for any suggestions you have on this process! Erick Pew webmaster for Music Theatre of Idaho