Forum OpenACS Development: Re: Syncing OpenACS Calendar to external information sources

Collapse
3: Re: Syncing OpenACS Calendar to external information sources (response to 1)
Posted by Don Baccus on 03/23/04 07:04 PM
All you need is the package_id, the rest can be gotten from the site_nodes utilities.  This is important because they cache stuff and are fast.

One traditional way to handle this is to have API procs take an optional package_id parameter, which they default to [ad_conn package_id].

Since your code to insert items via an rpc-call "knows" that it is doing this, it could figure out the proper package_id and pass it in, no?

Collapse
4: Re: Syncing OpenACS Calendar to external information sources (response to 3)
Posted by Peter Alberer on 03/23/04 11:03 PM
There were only a few lines to change in fact... One small change in calendar::item::get and some more changes in calendar::do_notifications. Passing in the package_id would be an option, but then i had to change calendar::item::new as well and i wanted to make as few changes as possible. As Don pointed out, after querying the database for the package_id, all other info can be retrieved via site_node utils. How could i contribute that change (might be quite useful for others)? Make a patch for a bug-tracker item?
Collapse
6: Re: Syncing OpenACS Calendar to external information sources (response to 4)
Posted by Dirk Gomez on 03/24/04 03:42 PM
Peter - create a patch for bug-tracker.