CaLogic Support Site

Posted by Philip on 2004/11/20 15:41:00 (14297 reads)

Version 1.2.2
Sorry, I had been forgetting to update the News section.
=================
Started: 20 July 2004, Finished: 13 Nov 2004

* IMPORANT NOTE *

The CaLogic folder structure and placement of some of the CaLogic
files has changed as of CaLogic 1.2.2

When updating from 1.2.1 or earlier to 1.2.2 or higher, please
move the file "dbloader.php" from your CaLogic include folder to your
CaLogic admin folder before running the update.

Always read the updating.txt file when updating.

============================================

Changes in 1.2.2:

The mini cal plugin has been updated. Anyone using this feature should
see the mcpi-demo.php file for the changes. There is a new "block" that
has to be added to your html documents that include the mini cal plugin.

There is a new field in the _setup table called calogic_uid.
This filed is generated one time upon installation or during
an update if it has not yet been generated. It contains a
unique value called a GUID. This value can and must be used
for automating Admin functions. The calogic_uid is very important.
You should take great care not to expose the calogic_uid. Do not
use it in links. It is meant only to be used in php programs.

CaLogic now has an Automation API.

Functions that are automated:
Creating and deleting a user
Creating and deleting a calendar
Automatically logging a user on
Emulating a user

Emulating a user is already built in:
Admins can now "Emulate" or logon as other users without needing a password. To do this,
logon as admin, go to the user settings, select the user you want to emulate, then click
"Emulate User". Doing this will log the admin user off and log you on as the selected
user. This function is intended to help you support your users.

For instructions on how to automate CaLogic using the Automation API, read
the automating_calogic.txt file in the docs folder.

The CaLogic session handling has been somewhat modified.
CaLogic now sets a cookie that stores the session ID. This
takes care of a few problems that I have experienced over the
years. For example, the PHP setting use_trans_sid is now
irrelevant. Also, because of the cookie, the PHP Session ID
no longer has to be transmitted with links when use_trans_sid
is turned off. The bad part about this is, the user must
accept a cookie or the session will not be propagated from
page to page. CaLogic includes a P3P header stipulating
that no Personal Information is stored, and that the cookie
is only for session state.

CaLogic no longer requires the PHP setting of register_globals to be on.

Language tables have been updated a little.
Also, Language Table entries now get added dynamically,
so if you have done some adding your self, there should
be no conflicts with the uid field. Meaning any future
changes I make will not (should not) conflict with changes
you may have made, or may make.

Each user can now set thier own time zone offset in the user settings area.
And there is a new "time zone lock" feature, when activated, it ensures that
the time zone offset you enter does not get changed when logging on. This is
to correct the problems that some have reported, when being on hosted
systems that do not have the correct time zone set. (and thier provider was
unwilling to do anything about it).

Added the per calendar option to allow the showing of events in
"Out of Month cell blocks" in the month view and mini cal.
Those are the cell blocks in the month and mini calendar, that
belong to the previous and next month. In the standard setup,
they are white in color, and usualy only display the day number.
Well, if you enable this option, these cells will also display
any events for those days. To turn this on, a user must turn on
the option "Display Out of Month Day Numbers".
This was a user requested modification.

*Finally* added all of the "per calendar" configuration options that
were only available in the Admin config area, to the Calendar Config
area. This means, that if the site admin allows it, a calendar owner now
has more calendar configuration options. For example, the header
and footer banner settings can now be set on a per calendar basis.
Basically all the options in the admin config area, that are under the
headings of: "Site Look and Feel" and "Calendar Look and Feel" can
now also be set on a per calendar basis. And if you look close enuf
at previous versions, it is even stated there next to the heading in
the admin config area, that "these are the default values, and that they
can be changed in the calendar config area" by the calendar owners. But
that wasn't true up til now. Also, I've added options to those areas in the
admin config, that gives you, the admin, the option of turning these
options on or off for the calendar owners. Also, because these
are new options that the users have never had, they are turned off
by default. So if you want to allow your calendar owners to be able to
change any of the settings for thier own calendars, you will have to enable
the options that allow them to make the changes.
Note that admin users will always be able see the per calendar
settings in the calendar config area. I also know, that perhaps
a lot of normal users may be overwhelmed by the many new configuration
options. so, you as site admin may choose to just keep the settings
turned off.

The Standard Default Calendar Option has been moved from the Calendar Config
Area to the CaLogic Admin Config Area. This is where it belongs anyway.

The Email format for reminders can now be set individually for users, contacts,
and event subscribers. There are 3 types of email format: plain text, HTML and
SMS. SMS is a short plain text format that will not excede 150 characters. It is
used for sending mail to PDAs or cell phones (handy) or other devices that may
have a charcter limit. The Email Format Setting field in the CaLogic Config Area
was used to set all current users, contacts and subscribers. Now, it's only use
is for the site owner notification mails that get sent out. All other System mail
settings are still used, like the "User Name in Email" setting for example.
In order for anonymous subscribers to be able to make use of the SMS option
a site admin must enable the new "Allow Anonymous Subscriber SMS" option in
the CaLogic config area. Thanks to Gerry for helping me figure out how to get
this option rolling.
This was (partially) a user requested modification.

The Calendar Title and user name has been removed from the upper part of the header.
This is because it is now an option to have the title shown.

Admins can now see/configure/delete calendars of other users. However
the user events on a private calendar will not be seen by the editing admin.
This was a user requested modification.

Added the admin option to turn off the functions menu for non admin users.

Added the admin option for the text used to name the functions menu.
This was a user requested modification.

Rearranged the Admin Config Area a little, so that the "site" options are
separated from the "per calendar default" options.

Added font and color configuration options for the popups. User customisation
of these options can also be turned on or off.

The Week, Month and Year view "Pull down" menus as well as the calendar pull
down menu have all been replaced with a new menu. This new "Horizontal Bar Menu"
is designed to save space and look nice. The colors and fonts of this menu are configurable
in the CaLogic Admin Config Area, and if allowed, in the individual calendar configurations.
The Side Bar "Sliding Functions Menu" can now either be placed in the new
Horizontal Menu Bar, or be left on the side or both.
This was (partly) a user requested modification.

The Popup and Menu color configurations for the individual calendars has made up
a new area in the CaLendar Config Area.

Added options to control the displaying of the mini calendar in each view.
The options are: Left, Right, Both or none. If left or right is selected then
the current month will be displayed. If both is chosen then the previous and
next months will be displayed. Guess what happens if you chose none?
These options are also user customisable in the View Areas of the Calendar Config Area.
This was a user requested modification.

A calendar owner can now specify, if conflicting events can be saved or not.
This was a user requested modification.

The contacts list is now sorted by last name, first name. The list of
reminder contacts is also now sorted in the event view.

The word "in all areas that allow for user input. This is to stop hacking.
Because CaLogic allows for HTML in the description, it was possible to enter
a bogus description that could cause anything from endless popups to relocating.
I did this because a Guestbook of mine was hacked in this manner. I tested to
see if I could do the same thing with CaLogic and I could. So I modified it to the
extent I think will effectively prevent such misuse.

There is now a "Check for Updates" link on the CaLogic Config form" Click it to check
if there are updates available. The check will open in its own window.

Fixed a bug in the week view that caused a clicked event to show the wrong date.
Thanks to Kate for the report *and* the fix!

Fixed a probelm that, when the week view is defined as the starting view,
it was not showing the correct dates, and the Week Pull Down dates
were all wrong upon startup. Thanks to all who reported this bug.

Fixed a bug that appeared only when the Default Calendar Option was turned
on, and then the Public View Option was turned on. Thanks to Mitch for his
help in getting this error fixed.

fixed a security leak that allowed any user (even the guest user) to delete
any event on any calendar. I also found this same kind of "bug" in other
areas and killed it as well.

Fixed some bugs I found on the contacts form. Also, selecting Association mode no
longer clears the selected contacts/groups.

Fixed a bug that caused some repeating events to be shown on the wrong day.

Read More... | 4 comments

New Releases : CaLogic Release 1.2.0

Posted by Philip on 2004/4/13 3:35:19 (27789 reads)

After nearly a year in the making.... CaLogic 1.2.0 is finally released.

I hope it was worth the wait.

If I didn't get a feature request built into this version, please drop me a mail or add a post on the forum. I will try to get it in the next version. I also promise not to try and do too much at one time with each new version... maybe just one thing at a time. That way, the new releases will get out faster.

Here's what's new:

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

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!