Got any thoughts? I could really use some help here. My clients website is primarily visited for her calendar!
All the best,Laura Ruiz
==========This will be our reply to violence: To make music more intensely, more beautifully, more devotedly than ever before. -Leonard Bernstein==========
Check your server error logs to see if a more detailed error message was recorded or if you have shell access (telnet, SSH, etc.) try running the script from there to see what error(s) Perl reports.
Once you find a more detailed error message, if you can't figure out the problem, post that error message and we'll see what we can suggest.
Dan O.
------------------
[sh: /usr/bin/date: No such file or directory]
Does that sound right at all?
Laura
------------------Laura Ruizhttp://www.increDesign.com
Dr. Charles McGregorCardiology
Did you maybe have the base directory variable set in the old but not the new? Maybe the file(s) got corrupted like uploaded in binary instead of ascii? Maybe the .zip archive you downloaded got corrupted? Incorrect permissions set for tham?
Just some possibilities. The files DO work.
JFYI
[This message has been edited by DanO (edited August 16, 2004).]
All common causes of scripts not running. None of them true here.
However, I did download the entire program in addition to the Upgrade. I noticed that the config.txt file has a different format: one line longer and some line items are different.
Think I'll try the new-style config file....
When the upgrade fails to work properly, it is almost always one of:1) Files uploaded incorrectly (bin instead of asc)2) Old version has custom changes, such as base dir, which need to be made in new version3) Files are not really in the place you think they are, ie, you're updating the wrong files (this happens way more often than you'd think )4) Permissions are not set correctly on files after they have been uploaded.
The debug.pl script should help, as should the server's error log. The files themselves are fine - they've been used by many hundreds of sites by now!
------------------ScottCalendarScript.com
The old version (3.0) contains:require "Config.pm";
While the new version contains:require "ConfigFile.pm";
Nah, that would be too easy!
But that's exactly what it was!
Sometimes the obvious escapes me....
It hadn't occured to me that they might be trying to upgrade from version 3.0 directly to the current version. That subject is covered in a previous forum message titled "upgrade from 3.0"
BTW Matt, have you corrected the CalendarScript321_Upgrade files recently to include the new feedback.html and messages.txt files which are needed to do a proper upgrade? The feedback.html file contains new version # and messages.txt file has an added error message.