So right now I am trying to come up with a good name for this.  I think I might actually sell it to other schools if I can get it working well enough.  I have tried it against a few other school’s calendars and it works great.

I added better handling for malformed events, now instead of ignoring them, they get changed to an all day event and “****” gets added to the front of the title with a message at the end of the title telling the user to verify event details manually the old fashioned way on the web calendar.

I also added a lot of debugging code, logging code, and statistics code and the ability to turn them on and off.  So now the admin can turn the logging code on and off so they don’t end up with tons of logs they don’t need.  Why create a debug log with 4+ lines per event when you aren’t debugging?  Most of the logs will be completely disabled in the production release anyway.

I also changed the way parameters get passed to the program through the URL.  Instead of just calendar.php?Calendar_name, its now calendar.php?cal=Calendar_name.  This will allow me to easily add other parameters and the order of them wont matter.  Been thinking of adding a manual start and end dates but I’m not sure I should even bother.

Maybe I should add some way of turning logging on and off through the URL and some sort of username/password.  We’ll see.  A few more features to add  before I go live like that.

I feel that I have made it far enough to call this a release.  Each file was given a release version of 1.0 while the overall program has gotten a release of 0.1 Beta.  I hope to be at 1.0 Beta by the end of May.  Though I expect it to be sooner.  Right now (as I’ve said earlier) it only works for Stevens Institute of Technology, however, since I do plan on selling it, it could be coming to your school one day.  If you like the idea of subscribing to your school’s calendar, let me know and I’ll see if they would be interested.