[sac-board] Re: Website Calendar

  • From: "Chris Hanrahan" <chris.hanrahan@xxxxxxx>
  • To: <sac-board@xxxxxxxxxxxxx>
  • Date: Wed, 5 Sep 2012 19:56:03 -0700

Two things:
1. Peter Argenziano kicks major @$$.  Thanks Peter for all your effort with
this crazy calendar thing.  I for one, appreciate it greatly.

2. I'm with Dr. Double-stars.  As we have no data in the calendar beyond
12-31-2012, it doesn't seem like a big deal.  If our calendar admin (Is that
Rick T?) has an issue with it, I'll input the remaining data for 2012.

Chris 




-----Original Message-----
From: sac-board-bounce@xxxxxxxxxxxxx [mailto:sac-board-bounce@xxxxxxxxxxxxx]
On Behalf Of Richard Harshaw
Sent: Wednesday, September 05, 2012 7:27 PM
To: sac-board@xxxxxxxxxxxxx
Subject: [sac-board] Re: Website Calendar

I suggest we go with option 2.  Suffering is good for character.  <g>



Richard Harshaw
Cave Creek, Arizona
Brilliant Sky Observatory

-----Original Message-----
From: sac-board-bounce@xxxxxxxxxxxxx [mailto:sac-board-bounce@xxxxxxxxxxxxx]
On Behalf Of Peter Argenziano
Sent: Wednesday, September 05, 2012 6:02 PM
To: SAC Board
Subject: [sac-board] Website Calendar

No doubt you've seen my update in the SAC Forum list. If not, don't fret -
it's copied below.

I'm posting here to seek input from the board. 
Our options, as I see them, are two:
1.) Live with our current, deprecated calendar
2.) Move to a new calendar that works within our website's environment and
suffer through the switch

OK, maybe a third option is that I can contact the current calendar's author
to see if they have one that works for us.

No hurry on the reply, as I'm heading to the cool country for a week.

Peter

==================
OK, now I think I know what we've got going on with the website calendar.
Our site was using PHP version 4.x and that is no longer supported. So, I
upgraded us to the current version (5.3). All well and good. Even fine and
dandy.
Now, it seems, our calendar application contains old code (generating the
'deprecated' errors). Not so good. or dandy.

The solution is going to be switching to a new calendar. Not a big problem -
except we will lose everything contained in the current one and someone (our
calendar admin) will have to re-populate the new one.




Other related posts: