PHP-Calendar Changelog

New in version 2.0

January 30th, 2014
  • The UI was vastly improved.
  • JQuery and JQuery UI are used for theming.
  • A more sensible and powerful event form was added.
  • Multiple calendars are now supported.
  • User support was improved, including admins for specific calendars and user groups.
  • Support for timezones was added, with user selectable language/timezone.
  • Translation support was improved.
  • A script was included for building translation objects.
  • Built-in get text support is now longer required.

New in version 2.0 RC2 (January 22nd, 2013)

  • This version is a quick follow-up to 2.0-rc1 to address a critical bug.
  • 2.0 RC1 added a setting for the date format and improved the timezone selector UI.

New in version 2.0 Beta 11 (January 4th, 2013)

  • This version features persistent logins, timezone and language settings for anonymous users, and improved date and time input widgets.
  • It also includes numerous bugfixes and UI improvements.

New in version 2.0 Beta 8 (June 15th, 2010)

  • There's not really much to talk about here in the way of features. A couple of new translations, Danish and Chinese. Not too many bug fixes. No DB changes. The big changes here are all security related. I added a check to protect against CSRF, fixed a few XSS and an SQL injection or two. Thanks to Teemu Vesala at Qentinel and the folks at Skipfish for helping find them. The update scripts from 1.x series have been removed as they were another attack vector.
  • There was a published vulnerability about the update scripts that I was never notified about. I'm pretty disappointed about how they handled that situation. The security advisory. Despite the fact that the bulletin says I was notified and the rep from said he notified me, I was not notified. If you're using an older version of PHP-Calendar, mainly version 1.1, please delete the update08.php and update10.php files.

New in version 2.0 Beta 6 (March 13th, 2010)

  • I fixed some bugs that I created in the last release. Specifically, some of the SQL statements with categories weren't quite right and when I fixed anonymous users, I broke one of the admin pages. Nothing really earth-shattering there, but they were stupid mistakes nonetheless. More noteworthy is that just because you have a table and the fields set as UTF-8 does not mean that MySQL is going to generate UTF-8 strings for you. I thought the entire calendar was UTF-8 before, but I was sorely mistaken. For those that don't know, UTF-8 is a character encoding that allows Western and non-Western characters to coexist. So if your Japanese friends want to post to your calendar in Japanese... now they can! Also, accented characters in the description broke the hover thing in the month view; that's now fixed.
  • I wrote a really simple and stupid script to generate the translation files. It's in the install directory. All of the translations are horribly out of date. I'm really sorry. If you have a favorite language and you want to create a translation or you're having trouble getting the translations working, please visit I wrote that up today for the release.

New in version 2.0 Beta 1 (June 27th, 2009)

  • The new features include a vastly improved permissions system. Site admins can create users and give them permissions (read, write, admin, etc) on distinct calendars. Running multiple calendars may not be perfect yet, but I would like feedback from anyone who wants to try it. I decided to release before I finished the code to delete users/calendars; that will be available in the next release.
  • The DB format is not finalized and there is unlikely to be an updater for the next version. This version is strictly for feedback. If you plan on updating your calendar when the next version comes out and you want to keep your events, wait. If you want to help me get the next version out, try this calendar, but understand it's going to be a difficult or strictly manual process to update.
  • The updater doesn't work for this version. It's unlikely that I'm going to write an updater to version 2.0. The user schema shouldn't change, but the event schema is going to change to the previous development line by the final version. There's too much installation dependent code to make an easy updater. If someone wants to take on the task, I will certainly be a guide, but I think improving the installer or other code would be time better spent.

New in version 1.1 (January 7th, 2009)

  • Switch from XHTML 1.0 to HTML 4.01 Strict
  • remove create_xhtml() which had become a misnomer and move the functionality to index.php where it is more accessible.
  • Created non-admin users who can only modify/delete their own events (and all of the infrastructure to go with this)
  • Prevent a user/admin from logging into one calendar and having the same priviledges on another calendar on the same host.