Version 1.2.0
=================
12 April 2004

(Download fle updated 18.04.2004. fixed a bug that caused a javascript error when adding events to private calendars. Thanks to every one who submitted the bug report.)

(Download file updated 14.04.2004, fixed an error in the setup routine. This error only happened durring a new installation. It did not affect updates. Thanks to justice for reporting the error.)


NOTE!!!
This is quite an extensive update. I highly urge you to make a backup
of your CaLogic Database and program files before updating. If something
goes wrong with the update, you will need to restore the database and
program files.

YOU HAVE BEEN WARNED!

As usual, I have tested CaLogic to the best of my ability. But because this
is such an enormous update, I expect there will be some bugs....
Now it's up to you to find and report them.

Fixed problems with the mini calendar plug in. I had made so many changes to
other parts of CaLogic, I forgot to update the mini cal. It is working now.
Please read the mcpi-demo.php file. This file is an example of how to
integrate a mini calendar into any php page. There are also new
variables that must be set in the file.

Fixed a bug that caused problems with events when more than 9 contacts
or groups were in the database.

fixed a bug that allowed events to be submitted, even when the check
conditions had not been met.

fixed a bug with the Event Collision Check. Thanks to Justice for submitting
this bug report.

fixed a bug in the user editor.

fixed the problem with week numbers not being consistant. also fixed the
week select box itself, it wasn't working properly.

fixed the language selection problem for public view. Now a "Guest" viewer
can select any language, and it won't conflict with other "Guest" users.

fixed a problem with the back ground color not be displayed.

the font and font color can now be set for each calendar individually. If it is
not set, then the global font and color will be used.

Added the Swedish language, many thanks to Christian Sahlé for the translation.

For security purposes, now only the event creator and admins can see the
email address of subscribers.

Optimized the Email Syntax checker.

Extended the demo mode to allow view of all options.

Added "multiple groups per contact". Now, a contact can belong to more than
one group. Also, contacts ang groups can now be shared with other users.

Added a "Forgot my Password" button to the logon screen. To request a new
password, a user must enter thier e-mail address. If the address is found
in the user table, an e-mail will be sent to them with a confirmation link.
Once the user clicks on the confirmation link, a new random password will
be generated and sent to them via e-mail. To prevent cracking, no error
message gets displayed if the requested e-mail does not exist in the user
table. As a matter of fact, it will look like request was succsessful.

Added "Remember my user name and password" check box to the logon screen.
Now it is possible to have your user name and pasword stored in a cookie
for one year.

User registration is also now an option. Admins can opt to not allow
for user registration.

Admins may now manually create users. Manually created users do not
have to confirm thier registration.

Added Extended Event Fields. This was a very difficult thing to do, and
it's one of the reasons this release took so long. And it was worth it!

Extended Event Fields are a way to allow you to define fields that can
be filled out when creating/editing an event. They are dynamic fields.
There is no limit to the number of fields you can define. There is also
no limit to the number of fields an event can have. You can define the
fields either when creating/editing an event, or in the Extended Event
Field Manager. You can define three types of fields. Input (a single line),
Textarea (multiple line), and Select fields. In select fields, you also
must supply the options. Fields can be defined as "required", meaning it
must be filled, or it can be standard, meaning it will automatically be
displayed but don't have to be filled in. Also, input fields
can be set for validation. Meaning that if it is filled, it must meet
certain requirements. there are 3 types of validation available;
Date, Number and Text. Also, Input fields have a max length option.
Any non required fields can be removed from an event. Also, non
required fields are automatically removed if empty.
As Admin, you can opt to allow users to create / add extended
fields in the CaLogic Config area.

Added Event Reminder Subscriptions. This feature allows anyone to
subscribe for an event reminder. It is also used for adding Registered
users to the reminder list. For this to work, reminders must be
turned on by an admin. And the event creator must then allow for
event reminder subscriptions by activating the check box when creating
or editing the event. If a person subscribes themself for a reminder,
they must confirm the subscription thru an automated email, much like
that when registering (double opt in). If a series event is subscribed for,
then an "unsubscribe" link is included in the reminder mail.

Event reminders are also now flexible. Meaning each contact can have
a different reminder interval set. This is also true for Event Reminder
Subscribers.

Using the Event Subscriptions function, it is now quite easy to create
multiple reminders for the same event. Just keep creating reminder
subscriptions for yourself.

Added User Password History. Now, an admin can define the amount of time
a password is valid, after that, a user must change their password before
logging on. There are no grace logons allowed. An admin can also define the
min length of passwords, as well as the use interval. Admins can now set
other users passwords. Or designate that the user must change their password
upon next login.

Added the ability to make "Exceptions" to series events.
Exceptions will allow you to exclude individual occurances of series events.
Each exception can be "re-instated".

Added a "history log". Now, (almost) all actions are recorded in the history log
table. The history log can only be viewed by admins. In a later version,
calendar owners will also be able to view the log, if the admin allows it.

A user can now copy or move events between it's calendars or to other
open/public calendars. An admin can copy/move an event to any calendar.
Event collisions are not checked during a copy/move, but the collision
will naturally display in a view. Copying an event creates a new event
on the calendar to which it is copied. The copied to event is not in any
way connected to the copied from event. Event reminders as well as Extended
Fields will be copied if restrictions permit. For example, if you
create an extended field for use only by you, on your own calendars, and then
copy an event that uses this extent to a calendar not owned by you, then the
extent won't (obviously can't) be copied. Also, Exceptions are not copied or moved.

The "Event Status Column" can now be turned on or off on a per calendar
basis.

Added a "Database Maintenance" section for admins. it is now possible
to backup and restore your CaLogic database right from within CaLogic.

Enhanced the Event Description Popup. Also, when holding the mouse over a day
on the mini cal which has an event will display a popup with the event information.


Whew! Time for a vacation!