Has anyone created a way to add an "updated" image/tag/text to an event that is updated on a calendarx calendar? I haven't thought through how it would be implemented, but it might be useful to have text or an image associated with a calendar entry when it is changed, and then disappear a week later, or even by request url. The use case is a group calendar that shows users as they view the calendar what has changed with added text/image and what is still the same. An email could be sent out, but for those groups who visit the calendar infrequently, it would be useful to have this indication of an updated event.

Thanks!

Mark

I tried adding calendarX from http://svn.plone.org/svn/collective/Products.CalendarX to a fresh Plone 4.0.2 install without any buildout errors and got these errors when running plonecfg fg:

orca:/usr/local/Plone/zinstance# bin/plonectl fg
instance: 2011-01-06 06:49:55 INFO ZServer HTTP server started at Thu Jan  6 06:49:55 2011
    Hostname: 0.0.0.0
    Port: 4040
2011-01-06 06:49:55 INFO Zope Set effective user to "plone"
/usr/local/Plone/buildout-cache/eggs/Products.CalendarX-0.9.6stable-py2.6.egg/Products/CalendarX/__init__.py:46: DeprecationWarning: package_home is deprecated. import from App.Common instead
  from Globals import package_home
2011-01-06 06:49:57 ERROR Application Couldn't install CalendarX
Traceback (most recent call last):
  File "/usr/local/Plone/buildout-cache/eggs/Zope2-2.12.13-py2.6-linux-x86_64.egg/OFS/Application.py", line 671, in install_product
    initmethod(context)
  File "/usr/local/Plone/buildout-cache/eggs/Products.CalendarX-0.9.6stable-py2.6.egg/Products/CalendarX/__init__.py", line 72, in initialize
    import CalendarXFolder
  File "/usr/local/Plone/buildout-cache/eggs/Products.CalendarX-0.9.6stable-py2.6.egg/Products/CalendarX/CalendarXFolder.py", line 1407, in <module>
    class CalendarXFolder(BaseFolder):
  File "/usr/local/Plone/buildout-cache/eggs/Products.CalendarX-0.9.6stable-py2.6.egg/Products/CalendarX/CalendarXFolder.py", line 1412, in CalendarXFolder
    __implements__ = (BaseFolder.__implements__, (),)
AttributeError: type object 'BaseFolder' has no attribute '__implements__'
Traceback (most recent call last):
  File "/usr/local/Plone/buildout-cache/eggs/Zope2-2.12.13-py2.6-linux-x86_64.egg/Zope2/Startup/run.py", line 56, in <module>
    run()
  File "/usr/local/Plone/buildout-cache/eggs/Zope2-2.12.13-py2.6-linux-x86_64.egg/Zope2/Startup/run.py", line 21, in run
    starter.prepare()
  File "/usr/local/Plone/buildout-cache/eggs/Zope2-2.12.13-py2.6-linux-x86_64.egg/Zope2/Startup/__init__.py", line 87, in prepare
    self.startZope()
  File "/usr/local/Plone/buildout-cache/eggs/Zope2-2.12.13-py2.6-linux-x86_64.egg/Zope2/Startup/__init__.py", line 264, in startZope
    Zope2.startup()
  File "/usr/local/Plone/buildout-cache/eggs/Zope2-2.12.13-py2.6-linux-x86_64.egg/Zope2/__init__.py", line 47, in startup
    _startup()
  File "/usr/local/Plone/buildout-cache/eggs/Zope2-2.12.13-py2.6-linux-x86_64.egg/Zope2/App/startup.py", line 116, in startup
    OFS.Application.initialize(application)
  File "/usr/local/Plone/buildout-cache/eggs/Zope2-2.12.13-py2.6-linux-x86_64.egg/OFS/Application.py", line 251, in initialize
    initializer.initialize()
  File "/usr/local/Plone/buildout-cache/eggs/Zope2-2.12.13-py2.6-linux-x86_64.egg/OFS/Application.py", line 279, in initialize
    self.install_products()
  File "/usr/local/Plone/buildout-cache/eggs/Zope2-2.12.13-py2.6-linux-x86_64.egg/OFS/Application.py", line 492, in install_products
    return install_products(app)
  File "/usr/local/Plone/buildout-cache/eggs/Zope2-2.12.13-py2.6-linux-x86_64.egg/OFS/Application.py", line 523, in install_products
    folder_permissions, raise_exc=debug_mode)
  File "/usr/local/Plone/buildout-cache/eggs/Zope2-2.12.13-py2.6-linux-x86_64.egg/OFS/Application.py", line 671, in install_product
    initmethod(context)
  File "/usr/local/Plone/buildout-cache/eggs/Products.CalendarX-0.9.6stable-py2.6.egg/Products/CalendarX/__init__.py", line 72, in initialize
    import CalendarXFolder
  File "/usr/local/Plone/buildout-cache/eggs/Products.CalendarX-0.9.6stable-py2.6.egg/Products/CalendarX/CalendarXFolder.py", line 1407, in <module>
    class CalendarXFolder(BaseFolder):
  File "/usr/local/Plone/buildout-cache/eggs/Products.CalendarX-0.9.6stable-py2.6.egg/Products/CalendarX/CalendarXFolder.py", line 1412, in CalendarXFolder
    __implements__ = (BaseFolder.__implements__, (),)
AttributeError: type object 'BaseFolder' has no attribute '__implements__'
orca:/usr/local/Plone/zinstance#

So then I tried the plone 4 branch (http://svn.plone.org/svn/collective/Products.CalendarX/branches/plone4-compatible/) and got the same errors:

orca:/usr/local/Plone/zinstance# bin/plonectl fg
instance: 2011-01-06 07:28:58 INFO ZServer HTTP server started at Thu Jan  6 07:28:58 2011
    Hostname: 0.0.0.0
    Port: 4040
2011-01-06 07:28:58 INFO Zope Set effective user to "plone"
/usr/local/Plone/buildout-cache/eggs/Products.CalendarX-0.9.6stable-py2.6.egg/Products/CalendarX/__init__.py:46: DeprecationWarning: package_home is deprecated. import from App.Common instead
  from Globals import package_home
2011-01-06 07:29:00 ERROR Application Couldn't install CalendarX
Traceback (most recent call last):
  File "/usr/local/Plone/buildout-cache/eggs/Zope2-2.12.13-py2.6-linux-x86_64.egg/OFS/Application.py", line 671, in install_product
    initmethod(context)
  File "/usr/local/Plone/buildout-cache/eggs/Products.CalendarX-0.9.6stable-py2.6.egg/Products/CalendarX/__init__.py", line 72, in initialize
    import CalendarXFolder
  File "/usr/local/Plone/buildout-cache/eggs/Products.CalendarX-0.9.6stable-py2.6.egg/Products/CalendarX/CalendarXFolder.py", line 1407, in <module>
    class CalendarXFolder(BaseFolder):
  File "/usr/local/Plone/buildout-cache/eggs/Products.CalendarX-0.9.6stable-py2.6.egg/Products/CalendarX/CalendarXFolder.py", line 1412, in CalendarXFolder
    __implements__ = (BaseFolder.__implements__, (),)
AttributeError: type object 'BaseFolder' has no attribute '__implements__'
Traceback (most recent call last):
  File "/usr/local/Plone/buildout-cache/eggs/Zope2-2.12.13-py2.6-linux-x86_64.egg/Zope2/Startup/run.py", line 56, in <module>
    run()
  File "/usr/local/Plone/buildout-cache/eggs/Zope2-2.12.13-py2.6-linux-x86_64.egg/Zope2/Startup/run.py", line 21, in run
    starter.prepare()
  File "/usr/local/Plone/buildout-cache/eggs/Zope2-2.12.13-py2.6-linux-x86_64.egg/Zope2/Startup/__init__.py", line 87, in prepare
    self.startZope()
  File "/usr/local/Plone/buildout-cache/eggs/Zope2-2.12.13-py2.6-linux-x86_64.egg/Zope2/Startup/__init__.py", line 264, in startZope
    Zope2.startup()
  File "/usr/local/Plone/buildout-cache/eggs/Zope2-2.12.13-py2.6-linux-x86_64.egg/Zope2/__init__.py", line 47, in startup
    _startup()
  File "/usr/local/Plone/buildout-cache/eggs/Zope2-2.12.13-py2.6-linux-x86_64.egg/Zope2/App/startup.py", line 116, in startup
    OFS.Application.initialize(application)
  File "/usr/local/Plone/buildout-cache/eggs/Zope2-2.12.13-py2.6-linux-x86_64.egg/OFS/Application.py", line 251, in initialize
    initializer.initialize()
  File "/usr/local/Plone/buildout-cache/eggs/Zope2-2.12.13-py2.6-linux-x86_64.egg/OFS/Application.py", line 279, in initialize
    self.install_products()
  File "/usr/local/Plone/buildout-cache/eggs/Zope2-2.12.13-py2.6-linux-x86_64.egg/OFS/Application.py", line 492, in install_products
    return install_products(app)
  File "/usr/local/Plone/buildout-cache/eggs/Zope2-2.12.13-py2.6-linux-x86_64.egg/OFS/Application.py", line 523, in install_products
    folder_permissions, raise_exc=debug_mode)
  File "/usr/local/Plone/buildout-cache/eggs/Zope2-2.12.13-py2.6-linux-x86_64.egg/OFS/Application.py", line 671, in install_product
    initmethod(context)
  File "/usr/local/Plone/buildout-cache/eggs/Products.CalendarX-0.9.6stable-py2.6.egg/Products/CalendarX/__init__.py", line 72, in initialize
    import CalendarXFolder
  File "/usr/local/Plone/buildout-cache/eggs/Products.CalendarX-0.9.6stable-py2.6.egg/Products/CalendarX/CalendarXFolder.py", line 1407, in <module>
    class CalendarXFolder(BaseFolder):
  File "/usr/local/Plone/buildout-cache/eggs/Products.CalendarX-0.9.6stable-py2.6.egg/Products/CalendarX/CalendarXFolder.py", line 1412, in CalendarXFolder
    __implements__ = (BaseFolder.__implements__, (),)
AttributeError: type object 'BaseFolder' has no attribute '__implements__'
orca:/usr/local/Plone/zinstance#

Does anyone have calendarX running on Plone 4? How did you do it?

Thanks!

I have found the windowZ product to be very useful for bringing external content into my Plone site. I am trying to figure out how to use it with calendarX.

For example, I schedule four to five months of tournaments for our softball teams so parents can plan for the games. About 3 days before the tournament, the brackets are released. I would like to create a window for these brackets instead of retyping them into the event for that day. Also, this approach means I don't have to make any updates if the brackets change for some reason, which happens from time to time.

The basic problem is that I would like to display some external content within an event object, and I am not sure how to do that. I realize that this is not really a calendarX issue, but perhaps others have wanted to display external content linked to an event in a calendar, so this is a stab in the dark to see if anyone has any ideas. I am running Plone 2.5.

Thanks!

Mark

Hi Victor,
   That's not a newbie/rookie error at all, you did exactly right.  However, there is not yet an egg for a Plone4-compatible release of CalendarX.  I hope that soon there will be... it's not that big of a job, near as I can tell.  There are two main things needed to change from the existing egg:
   1. Change the default setting to use the standard Zope query functions instead of Dieter's AdvancedQuery functions.  AQ was standard issue with Plone3 but has been removed from Plone4.
   2. Refactor how the CSS and JS that CalendarX uses are registered with Plone... the old way that worked since Plone2 does not work anymore.

Other than those changes, I believe that CalendarX will work just fine in Plone4, from my preliminary look at things.  I know how to do #1 (trivial), but #2 is not yet clear to me.  I got a version in Plone4 betaXX running after changing #1, but CSS and JS were not being applied, so the calendar doesn't look much like a calendar.  But it seemed to be working other than that.  Yay!

Anybody out there on the CalendarX-users list want to help figure out how to get #2 to work?  I will be satisfied with a simple approach that makes a basic CSS stylesheet get registered and applied to the calendar (and all its view templates).  The current CalendarX allows managers to modify CSS from within the Manage tab interface, but this will very likely be deprecated and disappear from the Plone4 version of CalendarX with the loss of DTML use in CSS files.  So all we need is to know how to register CSS and JS files for this product with Plone4 when it loads up.

I would love to jump in with both feet, but (1) I am in the midst of a major project release for my employer, and (2) my small farm is deep into organic tomato harvest time, hence (3) I have nearly zero time for this at the moment.  Fortunately, there is a svn branch started for Plone4 compatibility in the Collective, so feel free to jump right in and help get it done... and please keep me in the loop on how and what you do in there.  Keep us all informed, via this user list please.

Thanks team,
+lupa+

Am I seeing things, or is something strange happening on my CalendarX installation for October 31? I have 2 Oct 31 dates on the calendar! How do I get rid of it? You can see it at http://www.azheatwavesoftball.com - click on the Calendar tab and jump to October.

If I remove the event on Oct 31, I still have 2 Oct 31 boxes....Nov is shifted over, but the highlights for each cell go to the right cell. This is wierd! Lupa.....are you playing tricks on us for an early Halloween spoof????

Thanks!

Mark

Does anyone know how to import a file of iCal events into Plone events? I would like to import my google calendar events into my Plone site which uses CalendarX.

Thanks,

Mark