next »

[Shelley]

Hi,

My Web host was bought by another company and my entire site, including my wonderful calendar, was moved to a different server. I can no longer access it. I know that the two most important things are a correct path to perl and correct permissions and file endings.

I have reset all the permissions to the correct settings and changed the file endings of calendar.cgi and calendar_admin.cgi to calendar.pl and calendar_admin.pl, as instructed by my Web host.

However, the tech guy is telling me that my path to perl is not

#!/usr/bin/perl

as it previously was but that the perl application now resides in my cgi-bin directory and that the path to perl is

#!/cgi-bin/perl

Can that be? It doesn't make sense to me and it doesn't work.

My Web host is using a Unix-based Apache server.

What would be my best course of action? Should I remove the entire calendar scripts off the server and reinstall them?

Does that path to perl sound right?

Any information and help will be much appreciated.

Thanks,
Shelley

[DanO]

** #!/cgi-bin/perl - Can that be? **

I've never seen a path to Perl like that but anything's possible depending on how the server was set up. But maybe they misunderstood and though you were asking where you can put Perl scripts in your web space.

** changed the file endings of calendar.cgi and calendar_admin.cgi to calendar.pl and calendar_admin.pl, as instructed by my Web host. **

Than you'll also have to change the script URLs to .pl in the config.txt file located in the calendarscript directory.

Dan O.

[This message has been edited by DanO (edited June 28, 2004).]

[Shelley]

I have tried all the suggestions my Web host tech gave me. But these are not working and I really think he is misunderstanding what I mean when I am asking him for the correct path to perl. (i.e. I think he thinks I am asking where my perl scripts are, not that I need to know where the server's perl application is. I have tried to explain this in different ways to him.)

So I have changed my path to perl back to #!usr/bin/perl

and my calendar script files endings to .cgi  instead of .pl (including those in the config file).

All my calendarscript stuff is in my cgi-bin directory, so I don't think I have to change and activate the $BASE_DIR ="/path../". Is this correct?

Does anyone know what alternate "path to perl" might be used on an Apache server? Or, how can I explain to this guy what I need? I can't imagine that the problem is any more than this or wrong permissions.

Thanks for any help.

Shelley

------------------

[DanO]

** I don't think I have to change and activate the $BASE_DIR ="/path../". Is this correct? **

If their server is reporting the proper paths in the environment variables, no. If it isn't, yes you will need to set that variable appropriately.

Also, not all server setups allow data files to be located inside the cgi-bin directory. In that cause you'd have to put the calendarscript/ directory elsewhere and then set the $BASE_DIR variable to the correct path for them.

Dan O.

------------------

[Shelley]

Oh Happy Day!

I  finally have my calendar back. I changed server hosts because they just couldn't understand what I was saying to them. I now have a host that has really good support. I have a telnet shell and can figure out all the relevant paths and tap into the error logs easily to see what's what. I can also ftp easily into my site and I think they also have a virtual ftp set up. (Haven't used it yet.)

So, here's what I had to do:

1. Get a new server host. Verify the path to perl.

2. Re upload all my calendar files and scripts as text. Make sure ALL the necessary files were in the cgi-bin directory assigned to me. (Luckily, I have also set this calendar up on my Mac Apache WebServer, so I could see exactly what files were needed.)

3. Go in and set all the permissions correctly for each and every directory and file. (Very important.)

4. Put in the correct path to the Base Directory in the calendar.cgi and calendar_admin.cgi.

5. Make sure that the correct URL to my calendar site was in the config.txt file.

2  months of frustration are over!

Once again, thanks for a wonderful script and a great support forum.

------------------

[DanO]

** 3. Go in and set all the permissions correctly for each and every directory and file. (Very important.) **

I've yet to find that necessary. On all the installations I've done, I only needed to chmod the working files (calendar.pl, calendar_admin.pl and debug.pl) to 755. All the rest stayed as they were uploaded.

** 4. Put in the correct path to the Base Directory in the calendar.cgi and calendar_admin.cgi. **

The shouldn't usually be needed either as long as the server is reporting the proper paths in the environment variables or the data and other files are to be stored in directories other than the default paths CalendarScript comes set up in.

 Glad to hear you finally got it running though.

Dan O.

------------------