Home of gigCalendar for Joomla + Mambo

gigCalendar moving to JoomlaCode.org SOON

Be aware that the gigCalendar project is in the process of moving all development to a new home at JoomlaCode.org. We expect to have everything operational there by the end March, '07.The new home of gigCal development at JoomlaCode.org is:
http://joomlacode.org/gf/project/gigcalendar/

gigCalendar General Updates

gigCalendar 1.0.x has been out for a year and a half and continues to enjoy a lot of use. I recently estimated over 116,000 downloads in the past year from our J!Forge project page. Unfortunately, we have not been very timely about releasing bug fixes for the 1.0.x series. No reason to make excuses for why this is - no one who has volunteered has had time. Luckily for us, MOST users seem to be using a server that is compatible with our initial release series and have been able to look past the usability bugs.

This is not an ideal situation and I have continue to look into releasing a bug fix version of the 1.0.x series. I recently received a patched version of gigCalendar 1.0.x that looks VERY promising. It addresses a number of the bugs that have been posted here on the forums. In fact, many of the fixes are listed in these forums as the code came from a forum user. Problems addressed include the year bug in the backend, date navigation links in the full calendar and others.

There are two main issues with this patch:

1. includes new features that are not controllable in the gigConfig
2. does not address the problems that many users have with our initial SQL installation code

You're probably thinking, "Who cares if I can control a new feature in the gigConfig?" We created gigCalendar to be as flexible as possible and adding features that you cannot control in some way does not continue in this tradition. I don't have the coding know-how to add these features to the gigConfig....so I'm looking for PHP developers to help here.

I believe that there has been a forum post in the past that contained a fix for the SQL issues  but I'm not sure if it still exists. Honestly, I don't have access to any servers that have this problem so it will be difficult for me to test. Any help that you can offer me on that front would be greatly appreciated! Should we form a beta team? Let's discuss this in the Forum !

Cheers-
Graham Spice (aka Capt. gigCal)