From ben at alkaloid.net Mon Apr 21 11:44:32 2008 From: ben at alkaloid.net (Ben Klang) Date: Mon, 21 Apr 2008 07:44:32 -0400 Subject: [dev] [cvs] commit: framework/Date Date.php In-Reply-To: <20080420235622.139564w8l564tfok@technest.org> References: <20080419190159.6755B27BA0@nazik.horde.org> <20080420235622.139564w8l564tfok@technest.org> Message-ID: <025C21EE-6E9E-453E-A6A1-1C37C29D8C6E@alkaloid.net> On Apr 20, 2008, at 11:56 PM, Chuck Hagenbuch wrote: > Quoting Ben Klang : > >> Date Date.php >> Log: >> Also preserve the minutes field from Horde_Form_datetime > > Are you going to take care of merging these changes? We should not > have HEAD and FW_3 diverging at all at this point, except for the PHP > 5 libraries that are just previews for 3.2. Yes, I will merge these changes. Mostly I wanted to hold off a day or three and make sure I didn't break anything. Thanks for catching the array check by the way. /BAK/ -- Ben Klang Alkaloid Networks LLC ben at alkaloid.net 404.475.4850 http://projects.alkaloid.net From horde40 at volkerthen.com Tue Apr 22 16:14:54 2008 From: horde40 at volkerthen.com (Volker Then) Date: Tue, 22 Apr 2008 18:14:54 +0200 Subject: [dev] whups: Catchable fatal error, Object of class PEAR_Error could not be converted to string Message-ID: <20080422181454.36174w9mcws5t7ac@volker.then.net> Hi, we have a problem with a single ticket ID. A specific user cannot access the ticket history and he's getting Catchable fatal error: Object of class PEAR_Error could not be converted to string in /usr/share/php/Horde/Text/Filter/emails.php on line 130 instead. All other tickets work fine for any user. The debug log says: Apr 22 18:08:20 HORDE [debug] [whups] User simontemplar does not have READ permission for imp [pid 6904 on line 812 of "/usr/share/php/Horde/Registry.php"] Why should the user have read permissions for IMP, when reading tickets? Thanks in advance Volker From horde40 at volkerthen.com Tue Apr 22 17:16:09 2008 From: horde40 at volkerthen.com (Volker Then) Date: Tue, 22 Apr 2008 19:16:09 +0200 Subject: [dev] whups: Catchable fatal error, Object of class PEAR_Error could not be converted to string In-Reply-To: <20080422181454.36174w9mcws5t7ac@volker.then.net> References: <20080422181454.36174w9mcws5t7ac@volker.then.net> Message-ID: <20080422191609.106456w9flq4iz0o@volker.then.net> Quoting Volker Then : > > Hi, > > we have a problem with a single ticket ID. A specific user cannot > access the ticket history and he's getting > > Catchable fatal error: Object of class PEAR_Error could not be > converted to string in /usr/share/php/Horde/Text/Filter/emails.php on > line 130 > > instead. > > All other tickets work fine for any user. > > The debug log says: > > Apr 22 18:08:20 HORDE [debug] [whups] User simontemplar does not have > READ permission for imp [pid 6904 on line 812 of > "/usr/share/php/Horde/Registry.php"] > > > Why should the user have read permissions for IMP, when reading tickets? > The problem is, that the ticket content contains html code like this: xxxxx at xxx.xx whups is not able to render the email link for a user without imp permissions. Is this something for bugs.horde.org? Bye Volker From chuck at horde.org Tue Apr 22 19:14:25 2008 From: chuck at horde.org (Chuck Hagenbuch) Date: Tue, 22 Apr 2008 15:14:25 -0400 Subject: [dev] whups: Catchable fatal error, Object of class PEAR_Error could not be converted to string In-Reply-To: <20080422181454.36174w9mcws5t7ac@volker.then.net> References: <20080422181454.36174w9mcws5t7ac@volker.then.net> Message-ID: <20080422151425.1743861daey6baq8@technest.org> Quoting Volker Then : > we have a problem with a single ticket ID. A specific user cannot > access the ticket history and he's getting > > Catchable fatal error: Object of class PEAR_Error could not be > converted to string in /usr/share/php/Horde/Text/Filter/emails.php on > line 130 > Why should the user have read permissions for IMP, when reading tickets? Because we try to generate an IMP compose URL if possible. This commit should fix it for you and fall back to mailto: URLs: http://lists.horde.org/archives/cvs/Week-of-Mon-20080421/077610.html -chuck -- "I have concerns that we are not behaving like a mature, responsible, collection of interdependent organisms." - Rick O. From horde40 at volkerthen.com Wed Apr 23 07:17:03 2008 From: horde40 at volkerthen.com (Volker Then) Date: Wed, 23 Apr 2008 09:17:03 +0200 Subject: [dev] Fatal error: Cannot use object of type Horde_Date as array Message-ID: <20080423091703.149262bmfsf8nfk0@volker.then.net> Hi Ben, after today's CVS update of FRAMEWORK_3 and after installing the horde/framework packages I'm getting this error on login: Fatal error: Cannot use object of type Horde_Date as array in /usr/share/php/Horde/Date.php on line 108 Bye Volker From horde40 at volkerthen.com Wed Apr 23 08:17:51 2008 From: horde40 at volkerthen.com (Volker Then) Date: Wed, 23 Apr 2008 10:17:51 +0200 Subject: [dev] whups: Catchable fatal error, Object of class PEAR_Error could not be converted to string In-Reply-To: <20080422151425.1743861daey6baq8@technest.org> References: <20080422181454.36174w9mcws5t7ac@volker.then.net> <20080422151425.1743861daey6baq8@technest.org> Message-ID: <20080423101751.16876v892t15como@volker.then.net> Quoting Chuck Hagenbuch : > Quoting Volker Then : > >> we have a problem with a single ticket ID. A specific user cannot >> access the ticket history and he's getting >> >> Catchable fatal error: Object of class PEAR_Error could not be >> converted to string in /usr/share/php/Horde/Text/Filter/emails.php on >> line 130 > >> Why should the user have read permissions for IMP, when reading tickets? > > Because we try to generate an IMP compose URL if possible. This commit > should fix it for you and fall back to mailto: URLs: > > http://lists.horde.org/archives/cvs/Week-of-Mon-20080421/077610.html > > -chuck Thanks! Volker From ben at alkaloid.net Thu Apr 24 03:17:05 2008 From: ben at alkaloid.net (Ben Klang) Date: Wed, 23 Apr 2008 23:17:05 -0400 Subject: [dev] Fatal error: Cannot use object of type Horde_Date as array In-Reply-To: <20080423091703.149262bmfsf8nfk0@volker.then.net> References: <20080423091703.149262bmfsf8nfk0@volker.then.net> Message-ID: On Apr 23, 2008, at 3:17 AM, Volker Then wrote: > Hi Ben, > > after today's CVS update of FRAMEWORK_3 and after installing the > horde/framework packages I'm getting this error on login: > > Fatal error: Cannot use object of type Horde_Date as array in > /usr/share/php/Horde/Date.php on line 108 Fixed in CVS. Thanks! /BAK/ -- Ben Klang Alkaloid Networks LLC ben at alkaloid.net 404.475.4850 http://projects.alkaloid.net > > Bye > > Volker > > > -- > Horde developers mailing list - Join the hunt: http://horde.org/ > bounties/ > Frequently Asked Questions: http://horde.org/faq/ > To unsubscribe, mail: dev-unsubscribe at lists.horde.org From wrobel at pardus.de Sat Apr 26 16:51:56 2008 From: wrobel at pardus.de (Gunnar Wrobel) Date: Sat, 26 Apr 2008 18:51:56 +0200 Subject: [dev] [cvs] commit: kronolith/lib/Driver kolab.php In-Reply-To: <20080426113005.18767xehp71dvqtc@technest.org> (Chuck Hagenbuch's message of "Sat, 26 Apr 2008 11:30:05 -0400") References: <20080426064857.50FFA27BA0@nazik.horde.org> <20080426113005.18767xehp71dvqtc@technest.org> Message-ID: <8763u4eez7.fsf@home.pardus.de> Hi Chuck, Chuck Hagenbuch writes: > Quoting Gunnar Wrobel

: > >> Log: >> Revert the recent ID changes and keep the History part. For the >> Kolab driver in general UID is equal to ID. Bug: 6646. > > So how do you handle the case where two people have the same > invitation on their calendars? I'm not certain what could be a possible error scenario here. Within Kolab the ID is local to each calendar and does not care much about the ID in other calendars. And I guess having the same UID across calendars is meant to be used that way or am I wrong? I admit that I'm not that certain why Horde actually uses two types of ID. Somehow I was unable to give both a very clear and precise meaning. Maybe you could clarify the exact meaning or give me a hint where to look it up as this is a central part for handling all the external data exchange correctly and I definitely want to get that part right. Cheers, Gunnar > > -chuck > > -- > To unsubscribe, mail: cvs-unsubscribe at lists.horde.org -- ____ http://www.pardus.de _________________ http://gunnarwrobel.de _ E-mail : p at rdus.de Dr. Gunnar Wrobel Tel. : +49 700 6245 0000 Bundesstrasse 29 Fax : +49 721 1513 52322 D-20146 Hamburg ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >> Mail at ease - Rent a kolab groupware server at p at rdus << ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ From chuck at horde.org Sat Apr 26 19:30:44 2008 From: chuck at horde.org (Chuck Hagenbuch) Date: Sat, 26 Apr 2008 15:30:44 -0400 Subject: [dev] [cvs] commit: kronolith/lib/Driver kolab.php In-Reply-To: <8763u4eez7.fsf@home.pardus.de> References: <20080426064857.50FFA27BA0@nazik.horde.org> <20080426113005.18767xehp71dvqtc@technest.org> <8763u4eez7.fsf@home.pardus.de> Message-ID: <20080426153044.14347h0r2ovbge80@technest.org> Quoting Gunnar Wrobel : >> So how do you handle the case where two people have the same >> invitation on their calendars? > > I'm not certain what could be a possible error scenario here. Within > Kolab the ID is local to each calendar and does not care much about > the ID in other calendars. And I guess having the same UID across > calendars is meant to be used that way or am I wrong? > > I admit that I'm not that certain why Horde actually uses two types of > ID. Somehow I was unable to give both a very clear and precise > meaning. Maybe you could clarify the exact meaning or give me a hint > where to look it up as this is a central part for handling all the > external data exchange correctly and I definitely want to get that > part right. In the SQL driver, all events are in one database table. When someone syncs with a device using SyncML, or receives an iCal invitation, we need to maintain the UID of the original event so that we can track updates to it later. Therefore the UID can't be the event_id, because if two people on the same Kronolith install received the same invitation, the uid for both events (as added to their personal calendars) will be the same. -chuck From wrobel at pardus.de Sat Apr 26 19:59:31 2008 From: wrobel at pardus.de (Gunnar Wrobel) Date: Sat, 26 Apr 2008 21:59:31 +0200 Subject: [dev] [cvs] commit: kronolith/lib/Driver kolab.php In-Reply-To: <20080426153044.14347h0r2ovbge80@technest.org> (Chuck Hagenbuch's message of "Sat, 26 Apr 2008 15:30:44 -0400") References: <20080426064857.50FFA27BA0@nazik.horde.org> <20080426113005.18767xehp71dvqtc@technest.org> <8763u4eez7.fsf@home.pardus.de> <20080426153044.14347h0r2ovbge80@technest.org> Message-ID: <871w4se6ak.fsf@home.pardus.de> Hi Chuck, Chuck Hagenbuch writes: > Quoting Gunnar Wrobel : > >>> So how do you handle the case where two people have the same >>> invitation on their calendars? >> >> I'm not certain what could be a possible error scenario here. Within >> Kolab the ID is local to each calendar and does not care much about >> the ID in other calendars. And I guess having the same UID across >> calendars is meant to be used that way or am I wrong? >> >> I admit that I'm not that certain why Horde actually uses two types of >> ID. Somehow I was unable to give both a very clear and precise >> meaning. Maybe you could clarify the exact meaning or give me a hint >> where to look it up as this is a central part for handling all the >> external data exchange correctly and I definitely want to get that >> part right. > > In the SQL driver, all events are in one database table. When someone > syncs with a device using SyncML, or receives an iCal invitation, we > need to maintain the UID of the original event so that we can track > updates to it later. > > Therefore the UID can't be the event_id, because if two people on the > same Kronolith install received the same invitation, the uid for both > events (as added to their personal calendars) will be the same. okay, then I think I got it right. The difference within Kolab is that the objects are lying seperated in different IMAP folders. Getting an event based on ID always acts within the confines of one single IMAP folder. So even if there are other folders holding an object with the same ID there should be no problem. If we do a UID search in the kolab driver this is limited to the users personal IMAP folders. Cheers, Gunnar > > -chuck > > -- > Horde developers mailing list - Join the hunt: http://horde.org/bounties/ > Frequently Asked Questions: http://horde.org/faq/ > To unsubscribe, mail: dev-unsubscribe at lists.horde.org -- ____ http://www.pardus.de _________________ http://gunnarwrobel.de _ E-mail : p at rdus.de Dr. Gunnar Wrobel Tel. : +49 700 6245 0000 Bundesstrasse 29 Fax : +49 721 1513 52322 D-20146 Hamburg ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >> Mail at ease - Rent a kolab groupware server at p at rdus << ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ From chuck at horde.org Sat Apr 26 20:45:28 2008 From: chuck at horde.org (Chuck Hagenbuch) Date: Sat, 26 Apr 2008 16:45:28 -0400 Subject: [dev] [cvs] commit: kronolith/lib/Driver kolab.php In-Reply-To: <871w4se6ak.fsf@home.pardus.de> References: <20080426064857.50FFA27BA0@nazik.horde.org> <20080426113005.18767xehp71dvqtc@technest.org> <8763u4eez7.fsf@home.pardus.de> <20080426153044.14347h0r2ovbge80@technest.org> <871w4se6ak.fsf@home.pardus.de> Message-ID: <20080426164528.80933gatc15mtzsw@technest.org> Quoting Gunnar Wrobel : > The difference within Kolab is that the objects are lying seperated in > different IMAP folders. Getting an event based on ID always acts > within the confines of one single IMAP folder. So even if there are > other folders holding an object with the same ID there should be no > problem. > > If we do a UID search in the kolab driver this is limited to the users > personal IMAP folders. Got it, sounds good. Thanks, -chuck