MikeJ

Hello fromsitepoint, PHP should be just as easy to use as from your current host. Just place the files there, and they are ready to go. Phpmyadmin which you may have seen reference to, is a tool for mysql administration, it doesn't really have anything to do with PHP other than that it's written in PHP. To actually transfer the domain from registerfly to TCH, you can't get around the 60 day limit. However, that won't prevent you from using the domain immediately. All you need to do once you get an account with TCH, is through registerfly set the nameserver host entries to TCH's nameservers, and you will be ready to go within 72 hours max. If there's anything else we can answer, please ask.

It looks nice. Thumbs Up I'll definitely have to check it out. I play in a weekly game.

Try this instead: <!--#exec cgi="/poll_it/Poll_It_SSI_v2.05.cgi" --> It should work then.

My recommendations... use the full library installation. Best guarantee of full compatibility. The primary difference between lite and full, is that lite depends on the server to have all the libraries it needs. I would recommend installing MT cgi's under your main domain. Then you can decide to put your blog under a subdomain, primary domain, primary domain subdirectory, or whatever... and move it around in the future without requiring MT to be reinstalled (you just change the destination of where the blog files are written).

Do you have hotlinking protection enabled for those directories and maybe missing allowing blog.zoblue.com? Actually, I see you do have it enabled... "I had to add the subdomain to the Hotlink Protection & htaccess" It seems like that's where your problem is. I would double check your .htaccess settings.

Probably because the only version of RedHat that is still available (and still officially supported by RedHat after April 30), is RedHat Enterprise, which is not free. Fedora Legacy supports the older versions still though.

Mostly just because some people have different preferences. If you want both to be a particular theme, just submit a help desk ticket for the one you want changed.

Ok.... after reading your post on webhostingtalk, I think I know more about what you are asking. Have you successfully done any backup that FTP'd to your home machine? It sounded like you were still working that out. The address for your FTP is going to be your router's IP address, and you will have to allow FTP through your router to your PC (how depends on your router, look for port forwarding in the configuration). Since you are on a cable modem, it's going to be more difficult to use an automated script because your FTP address can change. Is that where you are getting hung up, though?

Yes please! Btw, I haven't forgotten about this. I had the flu all last week so I didn't get to doing much of anything I wanted to during that time. Once I finish my last minute tax stuff I'll get to it.

My script (and PHP) doesn't actually do any FTP. All it does is tell cPanel to run the backup and do the FTP, so it's the cPanel process that is FTPing to you. All my script does is pass parameters to cPanel. I'd recommend doing a backup manually (without the script) and try troubleshooting the problem that way. Once you have it confirmed working again, then reenable the script. If it works fine without the script, double check all of the values you have set. Let me know if you find anything.

Yea, you can use a standard (or "straight through patch") ethernet cable to connect the hub to the switch. Just plug *one* end into an uplink port. Now, for the technical description, should you want to know why, or you want to put yourself to sleep: Standard ethernet uses two pairs of wires, one send pair (wires 1 and 2) and one receive pair (wires 3 and 6). In order for Computer A to communicate with Computer B, those pairs have to be reversed (so that the send pair on Computer A connects to the receive pair on Computer B, therefore allowing Computer B to receive data sent by Computer A). Standard Ethernet cables are essentially straight through, which means that if you were to connect the cable between two computers, they won't be able to communicate. A hub or switch port automatically reverses the pairs so that the hub or switch can communicate with the PC on the port, which is why often ports will be listed as MDIX (medium dependent interface crossover) ports, the X representing the crossover... i.e., it exchanges the pairs. The uplink, or MDI port, does not. When you connect two hubs or switches together, if you plug both ends of a standard cable into an MDIX port, you end up cancelling out the crossover. This is why one end needs to be in an uplink, or MDI port (non-crossover port). This also explains why, for those doing the cheap 2 system network, you can take a crossover cable (pair 1,2 on one end is wired to pair 3,6 respectively on the other, and 3,6 is wired to 1,2) and plug the two systems directly into each other without any hub or switch.

Since it's not immediately obvious on their website where it's at, here's the direct link to their free tools: http://www.foundstone.com/resources/freetools.htm

Off the top of my head, things that will give you a hint.... Do a whois on the domain name, see what the name servers are set to (you might have to whois on those domains to follow the trail). Traceroute as Lisa said, that will at least tell you which datacenter it is. Do a whois lookup on the IP address to see who the IP address is allocated to (one whois client you can use for that: http://www.geektools.com/whois.php ). Those are at least some preliminary ways you attempt to find out who the hosting provider is.

MX is your mail exchanger. It's where your mail goes when someone attempts to send you email. When you send an email, say through your server (via SMTP), the mail system on that server does an MX lookup for the domain you are sending to to figure out where to send that mail (what server is handling mail for that domain). Same goes for when people send email to you. Since your website and email are all on the same server cPanel defaults to setting your MX to your domain. In your case, all three of those domains go to the same server, so it's essentially telling all mail for any of your 3 domains to go to the same server.

You'll need to open a new ticket and have the help desk straighten it out. Looks like a little oversight in the change.

To answer your question, basically yes. But that's a rather vague question. It depends on what level of anonymity you are looking for. As far as search engines, you can use robots.txt file to tell them not to index you. Not every search engine pays attention to it, but all the major ones do.

Awww, man..... Here I thought it was actually a game where they would sting you (btw, they are mosquitos) if you let them get to close. After 3,033 killed where not a single one crossed the screen more than twice, I gave up, and they just keep flying around. <_< At least it was pretty neat killing the close ones.

They may still be experiencing DDOS attacks today. I can't access their site right now either. www.2co.com seems to be working and includes support numbers:

Sorry, HCSS, if it came across as a little inappropropriate. I know people who are huge fans of Anime and there is nothing sexual about their interest, so that's the perspective I see that sculpture from. What is unfortunate is events in society today are making things like that start to take on different meaning.

Another thing I would be checking is the contents of $article.

Pointing domains at subfolders could be used to turn a standard account into a reseller account. That's the primary reason for the rule. There is quite a difference between "coolpocketpclinks.com" showing up in the browser when you hit a page, and "www.svpocketpc.com/svvgppclinks.html" showing up when you hit a page. Even if you redirect the former to the latter, the browser will still display "www.svpocketpc.com/svvgppclinks.html" when the user gets to the site, and therefore would be more difficult for someone to resell. It would also be difficult for TCH to confirm that add-on domains (pointing domains to subfolders) was not being used to resell since TCH has no way of confirming what you do on your end. The bottom line, though, is these rules aren't in place to try and make life difficult for the customers. It's just that TCH's prices are pretty darn low already, so the little restrictions put on the extensibility of the accounts is not exactly a major point. $8 or $12 a month is still incredibly cheap for the level of service you gain with TCH over most similarly priced hosting providers.

The main thing to remember is that PHP scripts used as your webpages run as the user of the webserver (user "nobody"), not as your account. So you have to make sure that the user "nobody" can do what it needs to do, which usually involves world access rights. For example, if you have a directory called "test" owned by you that has permissions 755 - world has read and execute (listing) permissions - and you access the following PHP script within it: <?php mkdir("phpmade",0755); ?> You will get a permission denied. If you change the permissions on "test" to 777 (so world has write access), you will get a directory like as follows: drwxr-xr-x 2 nobody nobody 4096 Apr 12 00:37 phpmade As you'll notice, it's owned by the user nobody because the webserver created it via your PHP script. To then upload files to that directory via PHP, you don't need 777 permission on THAT directory because the webserver is the owner (but you WILL have to change it to 777 or at least 757 in order for you yourself to write to the directory). If you let PHP create directories for you, just keep in mind you will have to deal with directories that aren't owned by you, and you can't change the owner of (only the permissions). The exception to that would be any PHP scripts you run from the command line (such as a cron job, not a web based page).

Even if you had a me@justbishop.com listed in the forwarding, as long as me@justbishop.com exists as an actual mailbox, it should still be getting email. Make sure you aren't running into a quota limit. You may want to request a help desk ticket, though, so someone can take a quick look at your setup and might spot something quickly that is misconfigured.

Now this is nuts.... Life size anime case

There really isn't a way around it with PHP. The php pages run under the webserver user "nobody" so you have to leave the directory the upload process writes to as world writable. You can't change the owner of your directories, and even changing the owner to nobody would do little for your security, since everyone on the same server has access to the nobody user through their web pages. You could look into alternative methods that allow uploads via cgi so it can run as your user account, but that has it's own security issues (and in my opinion, more serious security issues). Uploading in general via a web page is inherently insecure for the directories people are allowed to upload to.