Follow-up Comment #1, bug #13205 (project phpgroupware):
One thing that I did to get around this, which is of course a gross, insecure
hack, but may be a decent starting-point for a real solution, is as follows:
1) remove the need for authentication from ical.php
2) hardcode (ewwww) a login and password for a real phpgw user, who would
preferably have read-only access. I'm not sure how else to get database
access, i.e. a $sessionid.
3) add a parameter to the URL, i.e. calendar/ical.php?vilhuber would refer to
the calendar by vilhuber.
This allows ANYONE to view anybody else's calendar at present.
Obvious improvements are to have a setting in a user's profile (or relevant
calendar) that allows viewing by the ical.php program. Also, one could use
vilhuber.Home instead of just 'vilhuber' to refer to a calendar called 'Home'
by user 'vilhuber'. Not sure if phpgroupware has such a concept, though I
think multiple calendars are allowed. If so, each calendar should, of course,
have a 'allow export' flag of some sort. Other variantions of the
calendar-access naming are of course possible.
That still seems a bit of a hack, but one can always improve later.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?func=detailitem&item_id=13205>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
_______________________________________________
Phpgroupware-tracker mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/phpgroupware-tracker
