Solgema.fullcalendar

by Fabien Moret last modified Nov 10, 2011 08:05 AM

Solgema Fullcalendar is a complete Agenda for Plone based on Adam Shaw's javascript Fullcalendar. This is more than a simple calendar view: you can create and edit your events directly from the calendar.

Project Description

Solgema.fullcalendar is a complete implementation of Adam Shaw Fullcalendar into Plone. (More info on Fullcalendar here: http://arshaw.com/fullcalendar )

This calendar allows you to display event type objects in a powerfull and fast ajax agenda. You will be also able to add, edit and more generally manage your events throught the Calendar with a strong AJAX framework.

The calendar is a view you can choose on a Topic.The view is named "solgemafullcalendar_view". After that, a new object action permits you to set up the basics parameters for the calendar. The calendar is strongly linked to the Topic as the events it displays are searched by the Topic and it's criterias. In addition to the calendar, there is a small query form you can display in the bottom of the calendar to choose which event you want to display. The fields in this query form are taken from the Topic's Criterions.

To install it, just add "Solgema.fullcalendar" in the eggs and zcml parts of your bouildout.cfg.

 

First steps after installation:

 

  1. Create a topic
  2. Add the criterions in your topic so that it searches the content you want to display in your calendar.
    (you can for example add a Type Criterion with "Event" selected and another criterion with "Subjects" and the subjects you want to display.
  3. Choose the solgemafullcalendar_view as display for your Topic.
  4. Now you should see the events displayed in a javascript calendar.

You can now click on the new "Calendar View" action to set the basic parameters of the calendar (as start hour, default calendar view and so on)

Calendar view is coming in 3 groups : "Calendar", "Query" and "Colors"

"Calendar" group is the global settings for the calendar display.

"Query" group is where you will be able to set which informations from the topic's criterias will be displayed in the query form at the bottom of the calendar.

"Colors" group is where you can set the colors linked to the criterions set in the topic.

In the "Query" form in the field "Search Criterias" you can also choose wich of the topic's criterions you want to show in the query form in the bottom of the calendar.

Back into the calendar view, you can drop and resize events as you want (at least if you are allowed to edit that particualr event)

A simple right click on a event should open a drop down menu (as the standard content actions menu). From that menu you can Edit (AJAX), Copy, Paste, Cut and transition workflow all through AJAX.

If you select an empty slot in the calendar, you'll see an overlay where the standard Event add form is displayed. So you can add content very easily through the calendar.

The new content is added into the folder defined in the "target folder" field in the "Calendar View" tab.

 

Installation Note

--------

You might encounter a conflict error with a wrong version of zope.i18n ( coming from z3c.form ) when buildout. If so, edit your buildout.cfg and in the [version] part, ping the zope.i18n version to 3.6

[versions]
...
zope.i18n = 3.6

 

Customizing the skin

--------

You can easyly customize de calendar skin: Go to http://jquieryui.com and click on the Themes tab. There you can create or choose an existing theme. After that, download it to your computer by selecting only: All UI Core, all UI Interactions and Dialog in UI Widgets. Unzip and copy the css file and all images in you portal_skins/custom folder.

Self-Certification

[X] Internationalized

[ ] Unit tests

[ ] End-user documentation

[ ] Internal documentation (documentation, interfaces, etc.)

[X] Existed and maintained for at least 6 months

[X] Installs and uninstalls cleanly

[X] Code structure follows best practice

Current Release
Solgema.fullcalendar 2.1.0

Released May 15, 2012 — tested with Plone 4.1, Plone 4, Plone 3

Added gcal (google calendar) support, Added new "Split" view, Added fullcalendar view for Folders (interesting with subfolders), bug fix and s.o.
More about this release…

Download file Get Solgema.fullcalendar for all platforms
Product Package
If you are using Plone 3.2 or higher, you probably want to install this product with buildout. See our tutorial on installing add-on products with buildout for more information.

All Releases

Version Released Description Compatibility Licenses Status
solgema.fullcalendar-2.0.3.3 Apr 13, 2012 In this release: Added gcal (google calendar) support, Added new "Split" view, Added fullcalendar view for Folders (interesting with subfolders), bug fix and s.o. More about this release…
Plone 4.1
Plone 4
Plone 3
GPL final
solgema.fullcalendar-2.0.3.1 Apr 12, 2012 More about this release… GPL final
solgema.fullcalendar-2.0.3 Apr 12, 2012 More about this release… GPL final
2.1.0 May 15, 2012 Added gcal (google calendar) support, Added new "Split" view, Added fullcalendar view for Folders (interesting with subfolders), bug fix and s.o. More about this release…
Plone 4.1
Plone 4
Plone 3
GPL final
2.0 Nov 10, 2011 Major release of Solgema.fullcalendar which adds the ability to collect events for different sources and makes the calendar works 10 times faster! More about this release…
Plone 4.1
Plone 4
Plone 3
GPL final
1.9 Jun 17, 2011 Based on fullcalendar v.1.5.1, Lot of bug fixed, Support for recurring events, Added the ability to choose your short day name format More about this release…
Plone 4
Plone 3
GPL final
1.7 Jan 10, 2011 Bugs fixed and upgraded to fullcalendar v 1.4.10 More about this release…
Plone 4
Plone 3
GPL final
1.6 Nov 19, 2010 -Fixed wrong call to getUrl method and completed with here/absolute_url -Fixed bad condition expression in actions (Thanks to Thomas Desvanain) -Added some steps to be sure (as sure as possible) that solgemafullcalendar_view remains in topic views More about this release…
Plone 4
Plone 3
GPL final
1.5 Nov 09, 2010 Bug fixed ( plone.app.discussion, javascript content type, and other ) More about this release…
Plone 4
Plone 3
GPL final
1.4 Oct 19, 2010 -Now based on Fullcalendar v 1.4.8 -Fixed IE7 bug (thanks to Kyle Homstead) -Added the subtopics display in solgemafullcalendar_view (thanks to Christian Ledermann) -Added a tag in solgemafullcalendar_view so that events are display even if javascript is not enabled. This can be disabled in Calendar View settings. (thanks to Christian Ledermann) More about this release…
Plone 4
Plone 3
GPL final
1.3 Oct 08, 2010 Added the ability to choose your own colors for each topic's criterion. Bug fix ( content menu displayed under calendar events ) More about this release…
Plone 4
Plone 3
GPL final
1.2 Oct 05, 2010 Bugs fixed (calendar height) Based on jquery ui 1.8.5 More about this release…
Plone 4
Plone 3
GPL final
1.10 Aug 16, 2011 Fixed some translation bugs. Thanks to davidjb More about this release…
Plone 4
Plone 3
GPL final
1.1 Sep 30, 2010 Several bug fixed (dialog height, recursion error with jquery.js) and other improvements. More about this release…
Plone 4
Plone 3
GPL final
1.0 Sep 22, 2010 Several bug fixes. Added a relative start hour and relative start day. More about this release…
Plone 4
Plone 3
GPL final
0.3 Sep 09, 2010 Several minor fixes, Dependencies automatic installation. More about this release…
Plone 4
Plone 3
GPL release-candidate
0.2 Sep 09, 2010 Added a topicRelativeUrl in the javascript vars to fix cookie path. ( there were an issue with mulitple cookies when the topic was default view of a folder .) More about this release…
Plone 4
Plone 3
GPL release-candidate
0.1 Sep 08, 2010 Solgema Fullcalendar is a complete Agenda based on Adam Shaw's Fullcalendar for Plone. More about this release…
Plone 4
Plone 3
GPL release-candidate

Comments (7)

Thomas Desvenain Oct 05, 2010 08:41 AM
Very good product, easy to install and use and highly customizable. Full french translated. Thanks !!
Miguel Gomez Dec 13, 2010 04:16 PM
Looks like a nice product, but couldn´t install it using eggs.
I did point the i18 version to 3.6 as indicated in the Installation Notice, but I still get error messages stating wrong version. Any ideas?
Thanks.
Mr. Khan Jan 19, 2011 08:23 PM
What error are you seeing? I came across the same problem and bumped up the version # to get it to install.
Alejandro Pereira Dec 20, 2010 07:52 PM
Hi, excelent product. I got one problem. I can't set the default view as month. The currently is day but i dont want this. According to what you describe and what i understand, this should be set in the "calendar view" tab. But only appears two buttons: Label_save and label_cancel and i can't do anything, when i click on label_save says "There were some errors".
Also, i can't see the groups "Query", "calendar" and "Colors" that you mention. Thanks
Brad Gordon Feb 08, 2011 01:57 PM
I was also unable to install on a fresh 4.0.2 plone instance, including using the zope.i18n = 3.6 pin ... until I pinned zope.schema == 3.7.1 (the current version on PyPi). this brought in some other dependencies that haven't seemed to cause a problem yet...
wy Apr 16, 2011 06:37 PM
It looks great! Thanks for sharing your work. I had trouble installing because of the zope schema version conflict as other people but found a solution. Please check this site where the solution is explained at the end.

http://skins.quintagroup.com/plone4-theme-install

Briefly, here is the copy from the page.
-------------------------
In case you get zope-schema-related version conflict (Error: There is a version conflict. We already have: zope.schema 3.5.4 but z3c.form 2.4.2 requires 'zope.schema>=3.6.0) during buildout re-run, please add the following address to the list of extends in your buildout.cfg file:

[buildout]
...
extends =
...
http://good-py.appspot.com/release/plone.app.registry/1.0b2
Eric Wohnlich Mar 15, 2012 06:21 PM
Using 2.0.2 we seem to get an IE bug with the add event dialog modal. It looks like it was addressed in 0.3 but it's not working properly still. We had to change three lines in SFAjax_base_edit.cpt that reference jq("html").height() to jq(document).height() instead.