next »

[JR]

My Unix host (earthlink) disabled the 3.2 version and suggested an upgrade to 3.21.  After trying the simple 3.21 upgrade, the calendar did not work (unknown to me was that the .PM file was not uploaded as ASCII <sigh> ).  As my files were dated 11/2002 and the 3.21 files were dated 3/2004, assumed that there may have been some missing dependencies, so did a full install on top of the existing 3.2 using install.bat that *seemed* to go well (461759 bytes in 129 files transferred).  

Using WS_FTP Pro, changed all the files and folders to 755.

debug.pl said
Success!
No problems were found with your installation.
You should be able to run calendar and calendar_admin successfully!

Am able to access the admin page using the login/pw of the 3.2 installation so the good news appears to be that everything from the previous installation is still in tact.  The bad news is:

1- calendar_admin.pl?template=feedback.html *check for update* button tells me:
A new version is available!

The current version is: 3.21

Go to http://www.CalendarScript.com/  to get the latest version!

What does it use to make the version determination ?

2- calendar.pl gives ERROR PROCESSING TEMPLATE; full page is available at http://artlover.net/test/calendarscript.html

Not sure what other information is needed to fix the template error.  Please advise.

[JR]

On second glance, after a few hours of sleep, it appears that the install.bat overhaul did not take as most of the files display the initial install date of 11/2002.  This explains why the previous installation is still in tact.

Forgot to upload feedback.html which is where the version check is done.

Nonetheless, the template error still exists <sigh>

[DanO]

The error page also states "Maybe you didn't strip carriage returns after a network transfer?". Maybe some of the files where uploaded in binary mode instead of ascii?

** did a full install ... the good news appears to be that everything from the previous installation is still in tact. **

I'm surprised, it should have written over all the existing data files (except for new calendars which were created).

JFYI

Dan O.

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

[JR]

It always helps to be fully awake.

Don't know why the install.bat upload claimed to be successful but did not overwrite any existing files.  Nonetheless, that's goodness since an upgrade and not an overhaul was all that was really required.

Blame it on Auto-Detect.  Just installed WS_FTPPro9 and assumed it was intelligent.  After reading the CS error message, decided that templates/calendars/default was the culprit and consequently uploaded all the files in that directory.  Turns out that WS_FTPPro recognized PL, TXT and HTML as ASCII; but, not CSS <sigh>.  After transferring styles.css as ASCII, problem went away  

[DanO]

Glad to hear it.

Dan O.

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