CGI Script for Go Daddy hosting

Question

I just transferred my website to GoDaddy web hosting. I m
trying to figure out what script or code to use for my Form, but
nothing seems to work. Does anybody know about this? Also, what to
put into the Property Inspector for Form Action and Method and Enc
Type. Many,many thanks!

Answer 1

Just ignore the naysayers?
Why? Are our experience with GoDaddy invalid, trivial or a
fluke compared to yours?
"With difficulty on the way"..... Why? Is this something that
might have been avoided without so many restrictions on server
functionality? I had some very friendly reps there try to help, and
they were great, but they couldn't resolve a some "known" issues.
Is the "difficulty" you experienced something a person new to
building websites would find more difficult than you did? Do you
use other hosts where you can say you have experienced the same
difficulty?
Please don't take me wrong.
I used to be in the same position as you. I had a few sites,
including 2 Cartweaver sites, hosted there with no problem. I think
the reason I had no problems was in large part to the fact that I
didn't need support in setting up things like database connections
and so on. I was able to figure out how to do things on the servers
from experience, with some work arounds.
I do remember thinking a few times that it would have been
very difficult doing some of the things I did if I were still
learning, especially with a couple ecommerce sites. That's the
point.
I saw many complaints and issues in this forum as well as
others, including Cartweaver's newsgroups, about dynamic sites
there and I didn't "ignore" all of the naysayers even though I
hadn't had trouble yet.
I figured there must be some truth to their experience. They
certainly weren't making things up.
Besides, who was I to say my experience was the norm and
others should expect the same because that's how it is for me?
I did have better support and service, with less "difficulty"
and restrictions at a few other hosts I was using, but it wasn't a
big issue as I wasn't having major trouble at GD.
Unfortunately, my luck ran out.
However, because I didn't ignore the naysayers I had decided
to test them longer before migrating more sites. It's a good thing
I did, and I'm grateful to those who shared their experiences,
because I only had to move a few sites off and not many more.
The latest was a "known issue" on a certain server causing an
HTTP error intermittently, for hours. For weeks, I went back and
forth as it was "fixed" and reappeared again. This was a Cartweaver
site.
Obviously, the client pulled the plug. You can't hang an
"Open intermittently" sign on an online store.
The site was moved, with no changes what-so-ever to any code,
to another host. The problem immediately disappeared, and has
remained gone.
I do still have 1 CW site hosted with them that hasn't had
major trouble yet. It's on another server and low traffic.
The point is, I have experienced trouble too many times that
cost time and money and shouldn't have.
There is value to this experience, and others who have had
the same.
You can certainly say you've had no trouble, and that's
great. There's value in that, as well.
However, telling someone relatively new to just "ignore"
issues that others have had doesn't make sense to me.
If some web developers have reported trouble, isn't it a good
idea to do some research or at least see how one site works there
for a while before putting up a lot more?
Experiences others have had, especially when they are trying
to help someone new, shouldn't be ignored just because yours is
different. You can't guarantee the person will have the same
experience as you, so all points of view should be listened to and
weighed.
Take care,
Tim