This is a snapshot of Indico's old Trac site. Any information contained herein is most probably outdated. Access our new GitHub site here.

#1484 closed defect (fixed)

ical export issue

Reported by: jdefaver Owned by:
Priority: normal Milestone: v1.1
Component: RSS/iCal/XML/Metadata Version: 0.98-dev
Keywords: Cc:

Description

Hi,

When trying to export a category as an ical, i get an internal error screen and the logs show

014-02-19 14:06:04,543 indico.requestHandler: ERROR    - Request 140318597981840 failed: "'Event' object has no attribute 'set'"
Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/indico-0.98.2-py2.6.egg/MaKaC/webinterface/rh/base.py", line 566, in process
    res = self._process()
  File "/usr/lib/python2.6/site-packages/indico-0.98.2-py2.6.egg/MaKaC/webinterface/rh/categoryDisplay.py", line 549, in _process
    data = serializer(resultFossil)
  File "/usr/lib/python2.6/site-packages/indico-0.98.2-py2.6.egg/indico/web/http_api/ical.py", line 165, in __call__
    mapper(cal, fossil, now)
  File "/usr/lib/python2.6/site-packages/indico-0.98.2-py2.6.egg/indico/web/http_api/ical.py", line 57, in serialize_event
    event.set('uid', '%s-%s@cern.ch' % (id_prefix, fossil['id']))
AttributeError: 'Event' object has no attribute 'set'

I could not find anything like this on this site.

Any ideas ?

Thanks,

Jerome

Change History (7)

comment:1 Changed 20 months ago by jbenito

  • Milestone set to v1.1
  • Status changed from new to infoneeded_new

Hi Jerome,

it seems to me like a problem of versioning. Can you make sure that you are using icalendar version 3.2?

Cheers,
Jose

comment:2 Changed 20 months ago by jdefaver

Hi,

Indeed, following my attempt at upgrading to 1.1 (#1483), the default icalendar had been set to 3.6. I did not see that when downgrading.

reverting to 3.2 solves the problem.

thanks !

comment:3 Changed 20 months ago by jbenito

  • Resolution set to fixed
  • Status changed from infoneeded_new to closed

comment:4 Changed 19 months ago by hoffmann

This problem is still present in 1.1.2. Should the recipe "downgrade to icalendar=3.2" be added to the installation instructions, or is there a better bug fix to come for 1.2?

comment:5 Changed 19 months ago by hoffmann

  • Resolution fixed deleted
  • Status changed from closed to new

comment:6 Changed 18 months ago by pferreir

This has been fixed in 723c8adfa9a86829425bddacdf86e9923434c8ab and 1.2 will bundle this fix.

Closing ticket.

Thanks!

comment:7 Changed 18 months ago by pferreir

  • Resolution set to fixed
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.