Aside from mismatch module versions, and paths, it should be fairly simple to port a script from host a to b. My guess is that the web server configuration is different between the two hosts though. Sounds like in your old host, the extension for execcgi was both .pl and .cgi, while on the new one it's only cgi?<br>
<br>I'm sure there are other differences, I suggest you compare the two configs.<br><br>Dan<br><br><div class="gmail_quote">On Thu, Dec 18, 2008 at 12:29 PM, Walt Sanders <span dir="ltr"><<a href="mailto:wsanders@pacificwebdesign.org">wsanders@pacificwebdesign.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Am I the only one finding Perl porting to different web hosts a problem?<br>
<br>
I have one rather large website with about 400 pages, containing much user interaction handled with probably 50 or 60 perl.cgi programs scattered about in many directories. It all works beautifully.<br>
<br>
I recently thought to move the entire site to a different web host (for speed, cost and developer services improvements). I actually thought I could just move it all and tweak a few paths possibly and be done. So I tried putting up a few directories to see if everything will work ok. Aaaaugh! Perl won't work.<br>
<br>
First I find that permission must be precisely 755 instead of the previous 777 (this baffles me). Then only .pl instead of .cgi. or both. Ok, irritating, but not a big problem (I didn't ask them to reset it). But then only some of the perl programs would run.<br>
<br>
Investigating, I start finding oddities like: program A works, program B doesn't. I replace 100% of the content of program A with 100% of the content of program B, and program A then works fine. I then rename program A to program B and it works fine. OK, that one is fixed (not a clue as to why). Hmmmmm. If I take the original program B and simply change the name to program A (gotta work, right?), it doesn't work.<br>
<br>
I could list a dozen similarly silly tweaks that eventually got about half of the perl programs working, none of them having to do with the programming itself! I then tried to port to a 3rd large web host, thinking the 2nd host had some strange settings on its Apache server. There I found the same problem of very curious idiosyncrasies and curious illogical tweaks to make most of the Perl work, albeit different ones and none of it sensible.<br>
<br>
I'm wondering if I live alone in my own little world of "stay the hell away from perl if you want a peaceful life". On the first host, I had found perl to be wonderfully easy to program, totally reliable, and generally rock solid in the field. This is a sad development. Can anyone enlighten me a little as to what is going on?<br>
<br>
I don't really want to change languages, Walt.<br>
_______________________________________________<br>
SanFrancisco-pm mailing list<br>
<a href="mailto:SanFrancisco-pm@pm.org" target="_blank">SanFrancisco-pm@pm.org</a><br>
<a href="http://mail.pm.org/mailman/listinfo/sanfrancisco-pm" target="_blank">http://mail.pm.org/mailman/listinfo/sanfrancisco-pm</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>Dan Boger<br>