crpcalendar

  1. crpCalendar administration
    1. Categories
    2. Settings
      1. General
      2. Images
      3. Other modules
      4. PermaLinks?
      5. crpCalendar feed
    3. Administrative list
    4. Creation and Modification forms

crpCalendar administration

A fast introduction to main administrative functions and tasks.

Categories

It's not mandatory, but higly recommended to "enable categorisation" in module's settings.

First thing to check is the categories config. Once installed, crpCalendar create his own categories tree (under the root category/modules branch), with the property "Main" set on this value. The "Main" category registry could be changed choosing another branch, but the property managed by the module is only the "Main" (so creating an eg. "Secondary" registry property on another categories branch, will not take effect).

How to colorize your categories: it's really simple, edit your categories under the crpCalendar tree and create a property named "Color" (as shown in red on fig. cat1.png) with the values you want. The colors choosed will be displayed beside events or categories titles, according to layouts templates.

Settings

These are very important as they affects the whole crpCalendar system.

General

  • Enable categorization : self explanatory
  • Items per page : self explanatory
  • Max upload image size (bytes) : the max size (in bytes) allowed for event's image
  • Max upload document size (bytes) : the max size (in bytes) allowed for event's attachment
  • crpCalendar theme : could change the set of color used (not much, for now)
  • Calendar start Year : the year used as start for select choices or datepicker start limit
  • Notification for user's creation (none if empty) : self explanatory, when enabling user's submission of events filling this field will produce a notification e-mail
  • Enable user's partecipation to events : enabling this permit every user to signal his attendance at the events of the calendar (and to display the related pages)

Images

  • GD Library : automatic check of GD Library instalation, if not found it's not possible to use them
  • crpCalendar use GD Library : self explanatory, if not enabled resize is made by the browser
  • Show thumbnails in user list : if enabled, every list view have the column showing the events resized images
  • Event image width : the width (pixels) on the display page
  • User list thumbnail width : the width (pixels) of the thumbnail

Other modules

  • Enable Locations : active only if locations module is available; when checked event could have manually or locations based values (locations based have the priority)
  • Add category title to PermaLink? : self explanatory

crpCalendar feed

  • Enable RSS feed : if checked the whole RSS generation is enabled (through link or address bar), othersiwe, not
  • Display link to RSS feed : show link to global feed into user menu
  • Feed format : self explanatory

Administrative list

Eg. shown in list1.png: the list could be filtered by category (if categorisation is enabled) and/or by status using the submit and clear (which reload the unfiltered list) buttons. Events with bold and red titles are upcoming (based on start date); green status means active (available for the public), yellow means pending and red rejected. When status is green or yellow can be "swapped" clicking on the images, while when is red (rejected) must be changed through the complete modification form. Display, edit and delete are self-explanatory actions, while Copy (between Edit and Delete) means a creation of a clone event (same category, dates, images, content, etc) with a "Copy of ..." title and a pending status: an available base to be modified for very similar events.

Last but not least there is a curious button which says "Paypal donate". I think it deserves a click.

Creation and Modification forms

Forms are pretty simple: mandatory fields are "Title" and "Content" (dates being selects, can't be forgetted), and many of the others are self-explanatory: location, URL(start with http:// ...), contact, organiser.

If Zikula's Ajax framework is available (and the browser allow javascript), checking the "Day event" field will hide the "end date" field (the event will have a start, but being a day event there's no need to input an end). Both "start" and "end" could use an unobtrusive datepicker (which start year is configured in module's settings).

Event's image field accept gif,jpg and png mimetypes (with limitations on size), while event document have no limitations on mymetypes. When editing an existing event, already included images and attachment could be viewed (images with lightbox, files can be downloaded), deleted (in this case the event will not have an image or a attachment anymore) or overwritten (simply choosing another file).

Attachments