From ballier at mail.schule.de Mon Oct 26 08:34:28 2015 From: ballier at mail.schule.de (Ralph Ballier) Date: Mon, 26 Oct 2015 09:34:28 +0100 Subject: [horde] Blank lines in the mail In-Reply-To: <20151022151307.Horde.UEWu82N5hVFFB_dvtXi6yq_@h4.theupstairsroom.com> References: <20151019152726.Horde.XA1ZBqR1knhW4mvXuj8nbWo@horde.osz-lise-meitner.eu> <20151020121745.Horde.mc68GkCN5Jd5ilKAUmE2rEN@horde.osz-lise-meitner.eu> <20151020121038.Horde.qn1pGcdBIWyHsWfUUJralDR@h4.theupstairsroom.com> <20151022170539.Horde.sGecae_1TeUbh7u2L-vWaoJ@horde.osz-lise-meitner.eu> <20151022151307.Horde.UEWu82N5hVFFB_dvtXi6yq_@h4.theupstairsroom.com> Message-ID: <20151026093428.Horde.qQlINfMhkKw2evDQ94KsRKt@horde.osz-lise-meitner.eu> Zitat von Michael J Rubinsky : > Quoting Ralph Ballier : > >> Zitat von Michael J Rubinsky : >> >>> Quoting Ralph Ballier : >>> >>>> Zitat von Steffen : >>>> >>>>> On Mon, 19 Oct 2015, Ralph Ballier wrote: >>>>> >>>>>> Date: Mon, 19 Oct 2015 15:27:26 +0200 >>>>>> From: Ralph Ballier >>>>>> To: horde at lists.horde.org >>>>>> Subject: [horde] Blank lines in the mail >>>>>> >>>>>> Hello, >>>>>> >>>>>> if I forward or reply a mail in HTML format,?sometimes, but not >> >> always >>>> I >>>>>> get many blank lines. >>>>>> >>>>>> Look below. This is the beginning of a mail, when I start to forward >> >> or >>>>>> to >>>>>> reply. It don't depend on the browser. >>>>>> >>>>>> In Outlook there is no problem to answer. >>>>> >>>>> How does the "raw" body of the message looks like? Is it a HTML >>>>> message >>>>> with alternate text/plain part? How does either part looks like? >>>>> >>>>> Me first bet is that there are alternate parts the MUAs reply to or >> >> that >>>>> the HTML part contains tags, which cause these many blank lines. >>>> >>>> In a folder with a content of 30 mails I found about 6 mails with many >>>> blank lines, if I try to answer. If I click at the "Text" button, I >>>> downloaded the follow text as example. I have?anonymize some words. >>>> >>>> Perhaps this ist helpful. >>>> >>>> Ralph >>>> >>>> ----------------------------------------------- download after click at >>>> button "Text" >> >> ---------------------------------------------------------------------------------------------------------------------------------------------------- >>>> >>> xmlns:o="urn:schemas-microsoft-com:office:office" >>>> xmlns:w="urn:schemas-microsoft-com:office:word" >>>> xmlns="http://www.w3.org/TR/REC-html40"> >>>> ? >>>> >>>> >>>> >>>> >>>> >>>> >>>> ? >>>> >>>> ? >>>>
>>>> ? >>>>

> >> style='font-size:10.0pt; >>>> font-family:Arial'>Hier das Medienkonzept nebst den >>>> Spezifikationen.

>>>> ? >>>>

> >> style='font-size:10.0pt; >>>> font-family:Arial'> 

>>>> ? >>>>

> >> style='font-size:10.0pt; >>>> font-family:Arial'> 

>>>> ? >>>>

>>> style='font-size:10.0pt; >>>> font-family:Verdana'>Mit freundlichen >> >> Gr??en

>>>> ? >>>>

>>> style='font-size:10.0pt; >>>> font-family:Verdana'>Im Auftrag>>> style='font-family:Verdana'>

>>>> ? >>>>

>>> style='font-size:12.0pt; >>>> font-family:Verdana'> 

>>>> ? >>>>

>>> style='font-size:10.0pt; >>>> font-family:Verdana'>Nomen Nescio>>> style='font-family:Verdana'>

>>>> ? >>>>

>>> style='font-size: >>>> 12.0pt'> 

>>>> ? >>>>

>>> style='font-size: >>>> 10.0pt'>Technischer Leiter

>>>> ? >>>>

>>> style='font-size: >>>> 10.0pt'>der XXXXXX-Schule
>>>> XXXXXXX Str. YY
>>>> 10000 Berlin
>>>> Tel.: 030/888888-88
>>>> Fax: 030/888888-89

>>>> ? >>>>

>>> style='font-size: >>>> 12.0pt'> 

>>>> ? >>>>
>>>> ? >>>> >>>> ? >>>> >>>> -- >>>> Horde mailing list >>>> Frequently Asked Questions: http://horde.org/faq/ >>>> To unsubscribe, mail: horde-unsubscribe at lists.horde.org >>> >>> This is a well known issue with emails generated by Microsoft products >>> such as Outlook. You can search the archives but the bottom line is it's >>> a combination of the Outlook namespaced elements like e.g., >>> and linting code that keeps things clean and more secure for viewing >>> in-line in a web browser. >>> >>> -- >>> mike >>> The Horde Project >>> http://www.horde.org >>> https://www.facebook.com/hordeprojecthttps://www.twitter.com/hordeproject >> >> and it is not possible to do something against it?? > > No, not really. > > -- > mike > The Horde Project > http://www.horde.org > https://www.facebook.com/hordeprojecthttps://www.twitter.com/hordeproject > ? Today I got a mail with two attachments (PDF). In Outlook I see the mail body (1 page, no more) and above the links to the attachments. In Horde I see the message at begin of the mail body and above the links to the attachments. That's ok, but after the message follow many many blank lines. If I scroll the mouse wheel about 35 times(!!) down, then I see the preview of the boths PDF attachments. I think this is not ok. Ralph From ballier at mail.schule.de Mon Oct 26 09:58:54 2015 From: ballier at mail.schule.de (Ralph Ballier) Date: Mon, 26 Oct 2015 10:58:54 +0100 Subject: [horde] Horde and NetDrive Message-ID: <20151026105854.Horde.K_kBkIW9-ZDJOYXdx_l2D2P@horde.osz-lise-meitner.eu> Hallo, is it possible to connect the file manager of Horde over NetDrive to get a cloud drive? Thanks Ralph From merlin.schumacher at gmail.com Mon Oct 26 13:45:33 2015 From: merlin.schumacher at gmail.com (Merlin Schumacher) Date: Mon, 26 Oct 2015 14:45:33 +0100 Subject: [horde] Issues storing calendars in IMAP Message-ID: Hey, I'm setting up a horde installation on a system i'm administrating. I'm currently trying to get horde to use the IMAP-storage for calendars. The system is a Ubuntu 14.04 with dovecot. I configured dovecot to the best of my knowledge, but horde isn't able to properly create the folders in the maildir, but seems to store the list of folders it tried to create. Creating an event in the calendar fails also. The system uses IMAP as authentication. There is no LDAP available. This is my dovecot configuration: http://pastebin.com/3uFcHpz1 This is my horde configuration http://pastebin.com/TvK5hZxm I'd be thankful for every help -- Merlin Schumacher Sedanstra?e 28 31134 Hildesheim +491716714810 Zebrabutter - Das Beste im Netz seit 1679 http://www.zebrabutter.net Der Popkulturkalender - Jeden Tag ein H?ppchen Popkultur http://popkulturkalender.blogspot.com PGP Fingerprint: 8201 8716 EF71 081B 901C F8AD 3738 FEE8 C06C 57DA From mrubinsk at horde.org Mon Oct 26 14:27:02 2015 From: mrubinsk at horde.org (Michael J Rubinsky) Date: Mon, 26 Oct 2015 14:27:02 +0000 Subject: [horde] Issues storing calendars in IMAP In-Reply-To: Message-ID: <20151026142702.Horde.CgSIwPegLrkiF-zawbLn0q2@h4.theupstairsroom.com> Quoting Merlin Schumacher : > Hey, > > I'm setting up a horde installation on a system i'm administrating. > I'm currently trying to get horde to use the IMAP-storage for > calendars. The system is a Ubuntu 14.04 with dovecot. I configured > dovecot to the best of my knowledge, but horde isn't able to properly > create the folders in the maildir, but seems to store the list of > folders it tried to create. Creating an event in the calendar fails > also. The system uses IMAP as authentication. There is no LDAP > available. > This is my dovecot configuration: > http://pastebin.com/3uFcHpz1 > This is my horde configuration > http://pastebin.com/TvK5hZxm > > I'd be thankful for every help Without a more detailed description of the actual error that is being logged/thrown, it's hard to say for sure. My first guess would be something with the vendor annotations. I usually use cyrus when working with the IMAP storage backend, but IIRC ubuntu has the dovecot-metadata-plugin package. Not sure if you need to manually add the annotation types of not, but for cyrus, I configure /vendor/kolab/folder-type and /vendor/horde/share-params. -- mike The Horde Project http://www.horde.org https://www.facebook.com/hordeproject https://www.twitter.com/hordeproject -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5751 bytes Desc: S/MIME Signature URL: From wahnes at uni-koeln.de Mon Oct 26 14:43:47 2015 From: wahnes at uni-koeln.de (Jens Wahnes) Date: Mon, 26 Oct 2015 15:43:47 +0100 Subject: [horde] Sharing user information between hooks In-Reply-To: <20151002191428.Horde.9wk_cyFiBx0MkiODsqQ0Xcl@h4.theupstairsroom.com> References: <20151002095841.GD31122@coredump.rrz.uni-koeln.de> <20151002191428.Horde.9wk_cyFiBx0MkiODsqQ0Xcl@h4.theupstairsroom.com> Message-ID: <20151026144347.GB12631@coredump.rrz.uni-koeln.de> On Fri, Oct 02 2015, at 19:14:28 +0000, Michael J Rubinsky wrote: > Quoting Jens Wahnes : >> To customize the user experience, we are using hooks in our Horde >> installation. Among others, we are using preauth-Hooks both within the >> "horde" scope (.../config/hooks.php) and within the "imp" scope >> (.../imp/config/hooks.php). So far, these hooks work completely >> independent from each other. However, we would like to change that and >> access information that has been generated by Horde's preauth hook from >> within IMP's preauth hook. What is the best way to share such >> information between these hooks? Should I add some key-value pair to >> the user's session? If so, how should I go about that? Should I use >> PHP's $_SESSION variable? Or is there a preferred way to do that >> through some interface the Horde framework provides? > IIRC, depending on the context, it's possible for the preauth hooks to > be executed before the session is created, so you may or may not be able > to utilize the horde session within those hooks. For what we are trying to achieve, storing things within the session works quite well. To me, it looks like all of Horde's hooks are executed before any of IMP's hooks are executed (using LDAP authentication, that is - might be different when using IMAP authentication through IMP). So we are off just fine as long as we look into IMP preauth requests only if they have got a $userId set. Now we are just dependend on the fact that IMP's hooks are run after Horde's, so I hope that things will stay that way for a while. :-) > For the record, though, you should access the session using the > $GLOBALS['session'] object, not the raw php $_SESSION variable. Just in case anyone else is interested in doing something like this, I got this working using statements like these: $GLOBALS['session']->set('RRZK', 'foo', 'bar'); $foo = $GLOBALS['session']->get('RRZK', 'foo'); However, now that this is working, I'm already off to try something else. The reason to introduce code to write things into the session was to save unnecessary LDAP requests that would otherwise have to be executed in both Horde's hooks and IMP's hooks. The bulk of LDAP requests we see, however, seems to stem from the fact that a complete session is set up (including hooks being run) whenever there is a request through CalDAV or such. And not only is a session created for the user performing the CalDAV request, but also for all users that have granted this user access to their calendars, plus all users that this user is granting access to his or her calendars. All in all, that's a lot of sessions with lots of LDAP requests. (Consider, for example, a group of just 5 people granting calendar access to each other's personal calendar. Then you've got 5 LDAP requests per every CalDAV request. If everyone within the group is accessing all 5 calendars via CalDAV, that's 5*5*5 = 125 LDAP requests for just 5 people.) So I came to the idea to use memcache to cache the LDAP data, since we make heavy use of memcache anyways. I dug around the Horde API docs a bit and came up with some code that looks like this (not exactly, but close enough): $memcache = $GLOBALS['injector']->getInstance('Horde_Core_Factory_HashTable')->create($GLOBALS['injector']); $memcachekey = "rrzk_foo_$username"; if (!($foo = $memcache->get($memcachekey))) { # some code here that sets $foo from LDAP $memcache->set($memcachekey, $foo, array('expire' => $expirytime, 'replace' => 1)); } This does in fact work, but there is one problem: Calling the memcache methods this way does not seem to honor the prefix for memcache keys that can be set through $conf['hashtable']['params']['prefix']. Since other configuration options are actually picked up (e.g. the hostnames set in $conf['hashtable']['params']['hostspec']), there must be some error in the above code. Can anyone spot it? Do I have to call other (more generic) methods to make use of the prefix for memcache keys? Or is prefixing the key for memcache left up to the function calling the memcache set and get functions? If so, how would I access the name of the memcache prefix from within a hook? Jens -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: Digital signature URL: From mrubinsk at horde.org Mon Oct 26 15:01:38 2015 From: mrubinsk at horde.org (Michael J Rubinsky) Date: Mon, 26 Oct 2015 15:01:38 +0000 Subject: [horde] Sharing user information between hooks In-Reply-To: <20151026144347.GB12631@coredump.rrz.uni-koeln.de> References: <20151002095841.GD31122@coredump.rrz.uni-koeln.de> <20151002191428.Horde.9wk_cyFiBx0MkiODsqQ0Xcl@h4.theupstairsroom.com> <20151026144347.GB12631@coredump.rrz.uni-koeln.de> Message-ID: <20151026150138.Horde.gi9GCSJfF6wSlkrjP8m4_l2@h4.theupstairsroom.com> Quoting Jens Wahnes : > On Fri, Oct 02 2015, at 19:14:28 +0000, Michael J Rubinsky wrote: > >> Quoting Jens Wahnes : >>> To customize the user experience, we are using hooks in our Horde >>> installation. Among others, we are using preauth-Hooks both within the >>> "horde" scope (.../config/hooks.php) and within the "imp" scope >>> (.../imp/config/hooks.php). So far, these hooks work completely >>> independent from each other. However, we would like to change that and >>> access information that has been generated by Horde's preauth hook from >>> within IMP's preauth hook. What is the best way to share such >>> information between these hooks? Should I add some key-value pair to >>> the user's session? If so, how should I go about that? Should I use >>> PHP's $_SESSION variable? Or is there a preferred way to do that >>> through some interface the Horde framework provides? > >> IIRC, depending on the context, it's possible for the preauth hooks to >> be executed before the session is created, so you may or may not be able >> to utilize the horde session within those hooks. > > For what we are trying to achieve, storing things within the session > works quite well. To me, it looks like all of Horde's hooks are > executed before any of IMP's hooks are executed (using LDAP > authentication, that is - might be different when using IMAP > authentication through IMP). So we are off just fine as long as we > look into IMP preauth requests only if they have got a $userId set. > Now we are just dependend on the fact that IMP's hooks are run after > Horde's, so I hope that things will stay that way for a while. :-) > >> For the record, though, you should access the session using the >> $GLOBALS['session'] object, not the raw php $_SESSION variable. > > Just in case anyone else is interested in doing something like this, I > got this working using statements like these: > > $GLOBALS['session']->set('RRZK', 'foo', 'bar'); > > $foo = $GLOBALS['session']->get('RRZK', 'foo'); > > However, now that this is working, I'm already off to try something > else. > > The reason to introduce code to write things into the session was to > save unnecessary LDAP requests that would otherwise have to be executed > in both Horde's hooks and IMP's hooks. The bulk of LDAP requests we > see, however, seems to stem from the fact that a complete session is > set up (including hooks being run) whenever there is a request through > CalDAV or such. And not only is a session created for the user > performing the CalDAV request, but also for all users that have granted > this user access to their calendars, plus all users that this user is > granting access to his or her calendars. All in all, that's a lot of > sessions with lots of LDAP requests. (Consider, for example, a group > of just 5 people granting calendar access to each other's personal > calendar. Then you've got 5 LDAP requests per every CalDAV request. > If everyone within the group is accessing all 5 calendars via CalDAV, > that's 5*5*5 = 125 LDAP requests for just 5 people.) > > So I came to the idea to use memcache to cache the LDAP data, since we > make heavy use of memcache anyways. I dug around the Horde API docs a > bit and came up with some code that looks like this (not exactly, but > close enough): > > > $memcache = > $GLOBALS['injector']->getInstance('Horde_Core_Factory_HashTable')->create($GLOBALS['injector']); This should be: $GLOBALS['injector']->getInstance('Horde_HashTable'); The Horde_Core_Factory_HashTable class is registered with the injector as the factory to use to create the hash table driver. If interested, this is done in Horde_Registry::__construct(). -- mike The Horde Project http://www.horde.org https://www.facebook.com/hordeproject https://www.twitter.com/hordeproject -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5751 bytes Desc: S/MIME Signature URL: From mrubinsk at horde.org Mon Oct 26 15:04:11 2015 From: mrubinsk at horde.org (Michael J Rubinsky) Date: Mon, 26 Oct 2015 15:04:11 +0000 Subject: [horde] Horde and NetDrive In-Reply-To: <20151026105854.Horde.K_kBkIW9-ZDJOYXdx_l2D2P@horde.osz-lise-meitner.eu> Message-ID: <20151026150411.Horde.mMvYh3l4mEsmaKx7OtacLJa@h4.theupstairsroom.com> Quoting Ralph Ballier : > Hallo, > > is it possible to connect the file manager of Horde over NetDrive to get a > cloud drive? I haven't used NetDrive, but a quick glance at their website shows that it supports FTP access? If so, you could configure Gollem to use a FTP VFS. See gollem/config/backends.php for more details on the configuration options. -- mike The Horde Project http://www.horde.org https://www.facebook.com/hordeproject https://www.twitter.com/hordeproject -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5751 bytes Desc: S/MIME Signature URL: From mrubinsk at horde.org Mon Oct 26 16:00:23 2015 From: mrubinsk at horde.org (Michael J Rubinsky) Date: Mon, 26 Oct 2015 16:00:23 +0000 Subject: [horde] Blank lines in the mail In-Reply-To: <20151026093428.Horde.qQlINfMhkKw2evDQ94KsRKt@horde.osz-lise-meitner.eu> References: <20151019152726.Horde.XA1ZBqR1knhW4mvXuj8nbWo@horde.osz-lise-meitner.eu> <20151020121745.Horde.mc68GkCN5Jd5ilKAUmE2rEN@horde.osz-lise-meitner.eu> <20151020121038.Horde.qn1pGcdBIWyHsWfUUJralDR@h4.theupstairsroom.com> <20151022170539.Horde.sGecae_1TeUbh7u2L-vWaoJ@horde.osz-lise-meitner.eu> <20151022151307.Horde.UEWu82N5hVFFB_dvtXi6yq_@h4.theupstairsroom.com> <20151026093428.Horde.qQlINfMhkKw2evDQ94KsRKt@horde.osz-lise-meitner.eu> Message-ID: <20151026160023.Horde.sTFy02l2UTek1lDnfwlsVK2@h4.theupstairsroom.com> Quoting Ralph Ballier : > Zitat von Michael J Rubinsky : > >> Quoting Ralph Ballier : >> >>> Zitat von Michael J Rubinsky : >>> >>>> Quoting Ralph Ballier : >>>> >>>>> Zitat von Steffen : >>>>> >>>>>> On Mon, 19 Oct 2015, Ralph Ballier wrote: >>>>>> >>>>>>> Date: Mon, 19 Oct 2015 15:27:26 +0200 >>>>>>> From: Ralph Ballier >>>>>>> To: horde at lists.horde.org >>>>>>> Subject: [horde] Blank lines in the mail >>>>>>> >>>>>>> Hello, >>>>>>> >>>>>>> if I forward or reply a mail in HTML format,?sometimes, but not >>> >>> always >>>>> I >>>>>>> get many blank lines. >>>>>>> >>>>>>> Look below. This is the beginning of a mail, when I start to forward >>> >>> or >>>>>>> to >>>>>>> reply. It don't depend on the browser. >>>>>>> >>>>>>> In Outlook there is no problem to answer. >>>>>> >>>>>> How does the "raw" body of the message looks like? Is it a HTML >>>>>> message >>>>>> with alternate text/plain part? How does either part looks like? >>>>>> >>>>>> Me first bet is that there are alternate parts the MUAs reply to or >>> >>> that >>>>>> the HTML part contains tags, which cause these many blank lines. >>>>> >>>>> In a folder with a content of 30 mails I found about 6 mails with many >>>>> blank lines, if I try to answer. If I click at the "Text" button, I >>>>> downloaded the follow text as example. I have?anonymize some words. >>>>> >>>>> Perhaps this ist helpful. >>>>> >>>>> Ralph >>>>> >>>>> ----------------------------------------------- download after click > at >>>>> button "Text" >>> >>> > ---------------------------------------------------------------------------------------------------------------------------------------------------- >>>>> >>>> xmlns:o="urn:schemas-microsoft-com:office:office" >>>>> xmlns:w="urn:schemas-microsoft-com:office:word" >>>>> xmlns="http://www.w3.org/TR/REC-html40"> >>>>> ? >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> ? >>>>> >>>>> ? >>>>>
>>>>> ? >>>>>

>> >>> style='font-size:10.0pt; >>>>> font-family:Arial'>Hier das Medienkonzept nebst den >>>>> Spezifikationen.

>>>>> ? >>>>>

>> >>> style='font-size:10.0pt; >>>>> font-family:Arial'> 

>>>>> ? >>>>>

>> >>> style='font-size:10.0pt; >>>>> font-family:Arial'> 

>>>>> ? >>>>>

>>>> style='font-size:10.0pt; >>>>> font-family:Verdana'>Mit freundlichen >>> >>> Gr??en

>>>>> ? >>>>>

>>>> style='font-size:10.0pt; >>>>> font-family:Verdana'>Im Auftrag>>>> style='font-family:Verdana'>

>>>>> ? >>>>>

>>>> style='font-size:12.0pt; >>>>> font-family:Verdana'> 

>>>>> ? >>>>>

>>>> style='font-size:10.0pt; >>>>> font-family:Verdana'>Nomen Nescio face=Verdana>>>>> style='font-family:Verdana'>

>>>>> ? >>>>>

>>>> style='font-size: >>>>> 12.0pt'> 

>>>>> ? >>>>>

>>>> style='font-size: >>>>> 10.0pt'>Technischer Leiter

>>>>> ? >>>>>

>>>> style='font-size: >>>>> 10.0pt'>der XXXXXX-Schule
>>>>> XXXXXXX Str. YY
>>>>> 10000 Berlin
>>>>> Tel.: 030/888888-88
>>>>> Fax: 030/888888-89

>>>>> ? >>>>>

>>>> style='font-size: >>>>> 12.0pt'> 

>>>>> ? >>>>>
>>>>> ? >>>>> >>>>> ? >>>>> >>>>> -- >>>>> Horde mailing list >>>>> Frequently Asked Questions: http://horde.org/faq/ >>>>> To unsubscribe, mail: horde-unsubscribe at lists.horde.org >>>> >>>> This is a well known issue with emails generated by Microsoft products >>>> such as Outlook. You can search the archives but the bottom line is > it's >>>> a combination of the Outlook namespaced elements like e.g., >>>> and linting code that keeps things clean and more secure for viewing >>>> in-line in a web browser. >>>> >>>> -- >>>> mike >>>> The Horde Project >>>> http://www.horde.org >>>> > https://www.facebook.com/hordeprojecthttps://www.twitter.com/hordeproject >>> >>> and it is not possible to do something against it?? >> >> No, not really. >> >> -- >> mike >> The Horde Project >> http://www.horde.org >> https://www.facebook.com/hordeprojecthttps://www.twitter.com/hordeproject >> ? > > Today I got a mail with two attachments (PDF). In Outlook I see the mail > body (1 page, no more) and above the links to the attachments. > > In Horde I see the message at begin of the mail body and above the links to > the attachments. That's ok, but after the message follow many many blank > lines. If I scroll the mouse wheel about 35 times(!!) down, then I see the > preview of the boths PDF attachments. > > I think this is not ok. Feel free to come up with a solution and provide a patch that works, doesn't strip actual content or other formatting, and doesn't pose a security risk. Bottom line, Word generates completely broken HTML that is only designed to work in Microsoft products, when the Word specific CSS is included. -- mike The Horde Project http://www.horde.org https://www.facebook.com/hordeproject https://www.twitter.com/hordeproject -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5751 bytes Desc: S/MIME Signature URL: From torben at dannhauer.info Mon Oct 26 19:18:23 2015 From: torben at dannhauer.info (Torben Dannhauer) Date: Mon, 26 Oct 2015 20:18:23 +0100 Subject: [horde] Problems with Active Sync and Outlook 2013/2016 In-Reply-To: <20151023160632.Horde.TC8SkiT2rw4PuBU43IYuls6@h4.theupstairsroom.com> References: <00c701d10d23$768a8120$639f8360$@wb7.eu> <20151023032622.Horde.HwkYsxyVmVmli64-UygJsKQ@h4.theupstairsroom.com> <002901d10d91$9e6abf70$db403e50$@wb7.eu> <20151023155430.Horde.1uWPXEwAUzsxu6t_E-eAaCg@h4.theupstairsroom.com> <004001d10dab$9e5bf390$db13dab0$@wb7.eu> <20151023160632.Horde.TC8SkiT2rw4PuBU43IYuls6@h4.theupstairsroom.com> Message-ID: <01d301d11023$15974530$40c5cf90$@dannhauer.info> I use Horde EAS with Outlook 2016 and it works as expected. Regards, Torben -----Urspr?ngliche Nachricht----- Von: horde [mailto:horde-bounces at lists.horde.org] Im Auftrag von Michael J Rubinsky Gesendet: Freitag, 23. Oktober 2015 18:07 An: Lucas (wb7) Cc: horde at lists.horde.org Betreff: Re: [horde] Problems with Active Sync and Outlook 2013/2016 Please do not top post. Quoting Lucas (wb7) : > Here is a debug log with a few connection tries from OL 2016: > http://pastebin.com/H8wNXz5q > > A wiretrace is not so easy, because of the usage of HTTPS, but I'll > try my best, if you need one. Wireshark allows you to provide it with a copy of the certificate. > Does the debug log show something irregular? Unfortunately, no. It's very strange. I have no issues with OL2013. Hopefully it's not something silly that OL2016 is doing. I don't have access to it to test. > -----Urspr?ngliche Nachricht----- > Von: horde [mailto:horde-bounces at lists.horde.org] Im Auftrag von > Michael J Rubinsky > Gesendet: Freitag, 23. Oktober 2015 17:55 > An: horde at lists.horde.org > Betreff: Re: [horde] Problems with Active Sync and Outlook 2013/2016 > > > Quoting Lucas (wb7) : > >> Hi Michael, >> >> thank you for your response. My horde log shows >> >> Oct 23 14:42:28 isogramm HORDE: [imp] Login success for >> test at domain.com (79.204.123.123) to {imap://horde.server.de/} [pid >> 28966 on line 157 of >> "/var/www/horde/htdocs/horde-base/imp/lib/Auth.php"] >> >> for about 4 times per second if I start outlook and while it trys to >> sync. Do you need a debug log? The webserver log is clear; there are >> no errors. > > Debug log *might* show something. If you can get a wiretrace, though, > that would be even better. > > > > -- > mike > The Horde Project > http://www.horde.org > https://www.facebook.com/hordeproject > https://www.twitter.com/hordeproject -- mike The Horde Project http://www.horde.org https://www.facebook.com/hordeproject https://www.twitter.com/hordeproject From ballier at mail.schule.de Tue Oct 27 07:31:41 2015 From: ballier at mail.schule.de (Ralph Ballier) Date: Tue, 27 Oct 2015 08:31:41 +0100 Subject: [horde] Issue with VFS Message-ID: <20151027083141.Horde.eirCC0DxEbwUuTGucXkU9Ca@horde.osz-lise-meitner.eu> Hello, if I try to move a file in VFS to an other folder, then I get the following error message. But it is possible to delete the same file. Ralph A FATAL ERROR HAS OCCURRED UNABLE TO DELETE VFS FILE. 1. Gollem::moveFile() /www/htdocs/horde2/gollem/manager.php:169 2. Gollem::_copyFile() /www/htdocs/horde2/gollem/lib/Gollem.php:480 3. Gollem::moveFile() /www/htdocs/horde2/gollem/manager.php:169 4. Gollem::_copyFile() /www/htdocs/horde2/gollem/lib/Gollem.php:480 5. Horde_Vfs_Sql->deleteFile() /www/htdocs/horde2/gollem/lib/Gollem.php:557 DETAILS The Full Error Message Is Logged In Horde's Log File, And Is Shown Below Only To Administrators. Non-administrative Users Will Not See Error Details. Gollem_Exception Object ( [details] => [logged] => 1 [_logLevel:protected] => 0 [message:protected] => Unable to delete VFS file. [string:Exception:private] => [code:protected] => 0 [file:protected] => /www/htdocs/horde2/gollem/lib/Gollem.php [line:protected] => 560 [trace:Exception:private] => Array ( [0] => Array ( [file] => /www/htdocs/horde2/gollem/lib/Gollem.php [line] => 480 [function] => _copyFile [class] => Gollem [type] => :: [args] => Array ( [0] => move [1] => sqlhome [2] => /home/admin [3] => Dok1.pdf [4] => sqlhome [5] => /home/admin/Folder_1 ) ) [1] => Array ( [file] => /www/htdocs/horde2/gollem/manager.php [line] => 169 [function] => moveFile [class] => Gollem [type] => :: [args] => Array ( [0] => sqlhome [1] => /home/admin [2] => Dok1.pdf [3] => sqlhome [4] => /home/admin/Folder_1 ) ) ) [previous:Exception:private] => Horde_Vfs_Exception Object ( [details] => [logged] => [_logLevel:protected] => 0 [message:protected] => Unable to delete VFS file. [string:Exception:private] => [code:protected] => 0 [file:protected] => /usr/lib/php/Horde/Vfs/Sql.php [line:protected] => 303 [trace:Exception:private] => Array ( [0] => Array ( [file] => /www/htdocs/horde2/gollem/lib/Gollem.php [line] => 557 [function] => deleteFile [class] => Horde_Vfs_Sql [type] => -> [args] => Array ( [0] => /home/admin [1] => Dok1.pdf ) ) [1] => Array ( [file] => /www/htdocs/horde2/gollem/lib/Gollem.php [line] => 480 [function] => _copyFile [class] => Gollem [type] => :: [args] => Array ( [0] => move [1] => sqlhome [2] => /home/admin [3] => Dok1.pdf [4] => sqlhome [5] => /home/admin/Folder_1 ) ) [2] => Array ( [file] => /www/htdocs/horde2/gollem/manager.php [line] => 169 [function] => moveFile [class] => Gollem [type] => :: [args] => Array ( [0] => sqlhome [1] => /home/admin [2] => Dok1.pdf [3] => sqlhome [4] => /home/admin/Folder_1 ) ) ) [previous:Exception:private] => ) ) From hellermann at we-do.com Wed Oct 28 09:10:11 2015 From: hellermann at we-do.com (Jens Hellermann) Date: Wed, 28 Oct 2015 10:10:11 +0100 Subject: [horde] Update questions Horde Webmail Message-ID: <563090F3.1010704@we-do.com> Dear Horde List members, I have a question concerning updates of Horde Webmail. As I didn't know better at first (just googled update horde howto), I updated Horde Webmail following an article in a german debianforum: |pear upgrade -f -a -B -c horde and afterwards it was recommended to execute some scripts again: ||pear run-scripts horde/Horde_Role| But now I read in a mail from Michael Rubinsk that I should have used: pear upgrade -a -B horde/webmail I guess that is also why I lost some php extensions after upgrading. In my last update I did follow the method Michael suggested, but I'm still facing instability issues with the webinterface and connectivity issues to active sync (which dissapear, when I restart the whole server). My questions now are, how bad is it, I used the wrong update method? Can these problems result from that and can the process be reversed somehow, even by installating over the existing installation? I any case I need to preserve the settings and the active-sync status of the clients, as I have a testing group involved there. Kind regards, Jens. From mrubinsk at horde.org Wed Oct 28 12:37:12 2015 From: mrubinsk at horde.org (Michael J Rubinsky) Date: Wed, 28 Oct 2015 12:37:12 +0000 Subject: [horde] Update questions Horde Webmail In-Reply-To: <563090F3.1010704@we-do.com> Message-ID: <20151028123712.Horde.c9s-zl54VvReP9F4ddV8ZKb@h4.theupstairsroom.com> Quoting Jens Hellermann : > Dear Horde List members, > > I have a question concerning updates of Horde Webmail. As I didn't > know better at first (just googled update horde howto), I updated > Horde Webmail following an article in a german debianforum: > > |pear upgrade -f -a -B -c horde > > and afterwards it was recommended to execute some scripts again: > > ||pear run-scripts horde/Horde_Role| > > But now I read in a mail from Michael Rubinsk that I should have used: > > pear upgrade -a -B horde/webmail > > I guess that is also why I lost some php extensions after upgrading. > > In my last update I did follow the method Michael suggested, but I'm > still facing instability issues with the webinterface and > connectivity issues to active sync (which dissapear, when I restart > the whole server). > > My questions now are, how bad is it, I used the wrong update method? > Can these problems result from that and can the process be reversed > somehow, even by installating over the existing installation? What does: pear list -c horde show? > I any case I need to preserve the settings and the active-sync > status of the clients, as I have a testing group involved there. > > Kind regards, Jens. > -- > Horde mailing list > Frequently Asked Questions: http://horde.org/faq/ > To unsubscribe, mail: horde-unsubscribe at lists.horde.org -- mike The Horde Project http://www.horde.org https://www.facebook.com/hordeproject https://www.twitter.com/hordeproject -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5751 bytes Desc: S/MIME Signature URL: From hellermann at we-do.com Wed Oct 28 14:17:53 2015 From: hellermann at we-do.com (Jens Hellermann) Date: Wed, 28 Oct 2015 15:17:53 +0100 Subject: [horde] Update questions Horde Webmail In-Reply-To: <20151028123712.Horde.c9s-zl54VvReP9F4ddV8ZKb@h4.theupstairsroom.com> References: <20151028123712.Horde.c9s-zl54VvReP9F4ddV8ZKb@h4.theupstairsroom.com> Message-ID: <5630D911.30502@we-do.com> Am 28.10.2015 um 13:37 schrieb Michael J Rubinsky: > > Quoting Jens Hellermann : > >> Dear Horde List members, >> >> I have a question concerning updates of Horde Webmail. As I didn't >> know better at first (just googled update horde howto), I updated >> Horde Webmail following an article in a german debianforum: >> >> |pear upgrade -f -a -B -c horde >> >> and afterwards it was recommended to execute some scripts again: >> >> ||pear run-scripts horde/Horde_Role| >> >> But now I read in a mail from Michael Rubinsk that I should have used: >> >> pear upgrade -a -B horde/webmail >> >> I guess that is also why I lost some php extensions after upgrading. >> >> In my last update I did follow the method Michael suggested, but I'm >> still facing instability issues with the webinterface and >> connectivity issues to active sync (which dissapear, when I restart >> the whole server). >> >> My questions now are, how bad is it, I used the wrong update method? >> Can these problems result from that and can the process be reversed >> somehow, even by installating over the existing installation? > > > What does: > > pear list -c horde > > show? > Installed packages, channel pear.horde.org: =========================================== Package Version State Horde_ActiveSync 2.30.0 stable Horde_Alarm 2.2.5 stable Horde_Argv 2.0.11 stable Horde_Auth 2.1.10 stable Horde_Autoloader 2.1.1 stable Horde_Browser 2.0.10 stable Horde_Cache 2.5.0 stable Horde_Cli 2.0.6 stable Horde_Compress 2.1.3 stable Horde_Compress_Fast 1.1.0 stable Horde_Constraint 2.0.2 stable Horde_Controller 2.0.3 stable Horde_Core 2.22.1 stable Horde_Crypt 2.6.1 stable Horde_Crypt_Blowfish 1.1.0 stable Horde_CssMinify 1.0.2 stable Horde_Css_Parser 1.0.7 stable Horde_Data 2.1.3 stable Horde_Date 2.1.1 stable Horde_Date_Parser 2.0.4 stable Horde_Dav 1.1.2 stable Horde_Db 2.2.3 stable Horde_Editor 2.0.4 stable Horde_ElasticSearch 1.0.3 stable Horde_Exception 2.0.6 stable Horde_Feed 2.0.3 stable Horde_Form 2.0.11 stable Horde_Group 2.0.5 stable Horde_HashTable 1.2.3 stable Horde_History 2.3.5 stable Horde_Http 2.1.5 stable Horde_Icalendar 2.1.1 stable Horde_Idna 1.0.3 stable Horde_Image 2.3.3 stable Horde_Imap_Client 2.29.3 stable Horde_Imsp 2.0.8 stable Horde_Injector 2.0.4 stable Horde_Itip 2.1.0 stable Horde_JavascriptMinify 1.1.2 stable Horde_JavascriptMinify_Jsmin 1.0.1 stable Horde_Kolab_Format 2.0.7 stable Horde_Kolab_Server 2.0.4 stable Horde_Kolab_Session 2.0.2 stable Horde_Kolab_Storage 2.1.4 stable Horde_Ldap 2.3.1 stable Horde_ListHeaders 1.2.2 stable Horde_Lock 2.1.1 stable Horde_Log 2.1.2 stable Horde_LoginTasks 2.0.5 stable Horde_Mail 2.6.2 stable Horde_Mail_Autoconfig 1.0.2 stable Horde_Mapi 1.0.5 stable Horde_Memcache 2.0.7 stable Horde_Mime 2.9.2 stable Horde_Mime_Viewer 2.1.1 stable Horde_Mongo 1.0.3 stable Horde_Nls 2.1.0 stable Horde_Notification 2.0.3 stable Horde_Oauth 2.0.3 stable Horde_OpenXchange 1.0.0 stable Horde_Pack 1.0.5 stable Horde_Pdf 2.0.6 stable Horde_Perms 2.1.5 stable Horde_Prefs 2.7.4 stable Horde_Queue 1.1.3 stable Horde_Rdo 2.0.4 stable Horde_Role 1.0.1 stable Horde_Routes 2.0.4 stable Horde_Rpc 2.1.5 stable Horde_Scribe 2.0.2 stable Horde_Secret 2.0.5 stable Horde_Serialize 2.0.4 stable Horde_Service_Facebook 2.0.8 stable Horde_Service_Gravatar 1.0.0 stable Horde_Service_Twitter 2.1.5 stable Horde_Service_Weather 2.3.0 stable Horde_SessionHandler 2.2.5 stable Horde_Share 2.0.7 stable Horde_Smtp 1.9.1 stable Horde_Socket_Client 2.0.0 stable Horde_SpellChecker 2.1.2 stable Horde_Stream 1.6.2 stable Horde_Stream_Filter 2.0.3 stable Horde_Stream_Wrapper 2.1.2 stable Horde_Stringprep 1.0.2 stable Horde_Support 2.1.4 stable Horde_SyncMl 2.0.5 stable Horde_Template 2.0.2 stable Horde_Test 2.5.1 stable Horde_Text_Diff 2.1.1 stable Horde_Text_Filter 2.3.2 stable Horde_Text_Filter_Jsmin 1.0.1 stable Horde_Text_Flowed 2.0.2 stable Horde_Thrift 2.0.2 stable Horde_Timezone 1.0.9 stable Horde_Token 2.0.7 stable Horde_Translation 2.2.0 stable Horde_Tree 2.0.4 stable Horde_Url 2.2.4 stable Horde_Util 2.5.6 stable Horde_Vfs 2.3.0 stable Horde_View 2.0.5 stable Horde_Xml_Element 2.0.3 stable Horde_Xml_Wbxml 2.0.2 stable content 2.0.5 stable gollem 3.0.6 stable horde 5.2.8 stable horde_lz4 1.0.8 stable imp 6.2.11 stable ingo 3.2.7 stable kronolith 4.2.11 stable mnemo 4.2.8 stable nag 4.2.6 stable timeobjects 2.1.0 stable trean 1.1.3 stable turba 4.2.10 stable webmail 5.2.11 stable >> I any case I need to preserve the settings and the active-sync status >> of the clients, as I have a testing group involved there. >> >> Kind regards, Jens. >> -- >> Horde mailing list >> Frequently Asked Questions: http://horde.org/faq/ >> To unsubscribe, mail: horde-unsubscribe at lists.horde.org > > > > > From mrubinsk at horde.org Wed Oct 28 14:57:00 2015 From: mrubinsk at horde.org (Michael J Rubinsky) Date: Wed, 28 Oct 2015 14:57:00 +0000 Subject: [horde] Update questions Horde Webmail In-Reply-To: <5630D911.30502@we-do.com> References: <20151028123712.Horde.c9s-zl54VvReP9F4ddV8ZKb@h4.theupstairsroom.com> <5630D911.30502@we-do.com> Message-ID: <20151028145700.Horde.Gov4j_coX10u6mbnelmuxHV@h4.theupstairsroom.com> Quoting Jens Hellermann : > Am 28.10.2015 um 13:37 schrieb Michael J Rubinsky: >> >> Quoting Jens Hellermann : >> >>> Dear Horde List members, >>> >>> I have a question concerning updates of Horde Webmail. As I didn't >>> know better at first (just googled update horde howto), I updated >>> Horde Webmail following an article in a german debianforum: >>> >>> |pear upgrade -f -a -B -c horde >>> >>> and afterwards it was recommended to execute some scripts again: >>> >>> ||pear run-scripts horde/Horde_Role| >>> >>> But now I read in a mail from Michael Rubinsk that I should have used: >>> >>> pear upgrade -a -B horde/webmail >>> >>> I guess that is also why I lost some php extensions after upgrading. >>> >>> In my last update I did follow the method Michael suggested, but >>> I'm still facing instability issues with the webinterface and >>> connectivity issues to active sync (which dissapear, when I >>> restart the whole server). >>> >>> My questions now are, how bad is it, I used the wrong update >>> method? Can these problems result from that and can the process be >>> reversed somehow, even by installating over the existing >>> installation? >> >> >> What does: >> >> pear list -c horde >> >> show? >> > Installed packages, channel pear.horde.org: > =========================================== > Package Version State > Horde_ActiveSync 2.30.0 stable > Horde_Alarm 2.2.5 stable > Horde_Argv 2.0.11 stable > Horde_Auth 2.1.10 stable > Horde_Autoloader 2.1.1 stable > Horde_Browser 2.0.10 stable > Horde_Cache 2.5.0 stable > Horde_Cli 2.0.6 stable > Horde_Compress 2.1.3 stable > Horde_Compress_Fast 1.1.0 stable > Horde_Constraint 2.0.2 stable > Horde_Controller 2.0.3 stable > Horde_Core 2.22.1 stable > Horde_Crypt 2.6.1 stable > Horde_Crypt_Blowfish 1.1.0 stable > Horde_CssMinify 1.0.2 stable > Horde_Css_Parser 1.0.7 stable > Horde_Data 2.1.3 stable > Horde_Date 2.1.1 stable > Horde_Date_Parser 2.0.4 stable > Horde_Dav 1.1.2 stable > Horde_Db 2.2.3 stable > Horde_Editor 2.0.4 stable > Horde_ElasticSearch 1.0.3 stable > Horde_Exception 2.0.6 stable > Horde_Feed 2.0.3 stable > Horde_Form 2.0.11 stable > Horde_Group 2.0.5 stable > Horde_HashTable 1.2.3 stable > Horde_History 2.3.5 stable > Horde_Http 2.1.5 stable > Horde_Icalendar 2.1.1 stable > Horde_Idna 1.0.3 stable > Horde_Image 2.3.3 stable > Horde_Imap_Client 2.29.3 stable > Horde_Imsp 2.0.8 stable > Horde_Injector 2.0.4 stable > Horde_Itip 2.1.0 stable > Horde_JavascriptMinify 1.1.2 stable > Horde_JavascriptMinify_Jsmin 1.0.1 stable > Horde_Kolab_Format 2.0.7 stable > Horde_Kolab_Server 2.0.4 stable > Horde_Kolab_Session 2.0.2 stable > Horde_Kolab_Storage 2.1.4 stable > Horde_Ldap 2.3.1 stable > Horde_ListHeaders 1.2.2 stable > Horde_Lock 2.1.1 stable > Horde_Log 2.1.2 stable > Horde_LoginTasks 2.0.5 stable > Horde_Mail 2.6.2 stable > Horde_Mail_Autoconfig 1.0.2 stable > Horde_Mapi 1.0.5 stable > Horde_Memcache 2.0.7 stable > Horde_Mime 2.9.2 stable > Horde_Mime_Viewer 2.1.1 stable > Horde_Mongo 1.0.3 stable > Horde_Nls 2.1.0 stable > Horde_Notification 2.0.3 stable > Horde_Oauth 2.0.3 stable > Horde_OpenXchange 1.0.0 stable > Horde_Pack 1.0.5 stable > Horde_Pdf 2.0.6 stable > Horde_Perms 2.1.5 stable > Horde_Prefs 2.7.4 stable > Horde_Queue 1.1.3 stable > Horde_Rdo 2.0.4 stable > Horde_Role 1.0.1 stable > Horde_Routes 2.0.4 stable > Horde_Rpc 2.1.5 stable > Horde_Scribe 2.0.2 stable > Horde_Secret 2.0.5 stable > Horde_Serialize 2.0.4 stable > Horde_Service_Facebook 2.0.8 stable > Horde_Service_Gravatar 1.0.0 stable > Horde_Service_Twitter 2.1.5 stable > Horde_Service_Weather 2.3.0 stable > Horde_SessionHandler 2.2.5 stable > Horde_Share 2.0.7 stable > Horde_Smtp 1.9.1 stable > Horde_Socket_Client 2.0.0 stable > Horde_SpellChecker 2.1.2 stable > Horde_Stream 1.6.2 stable > Horde_Stream_Filter 2.0.3 stable > Horde_Stream_Wrapper 2.1.2 stable > Horde_Stringprep 1.0.2 stable > Horde_Support 2.1.4 stable > Horde_SyncMl 2.0.5 stable > Horde_Template 2.0.2 stable > Horde_Test 2.5.1 stable > Horde_Text_Diff 2.1.1 stable > Horde_Text_Filter 2.3.2 stable > Horde_Text_Filter_Jsmin 1.0.1 stable > Horde_Text_Flowed 2.0.2 stable > Horde_Thrift 2.0.2 stable > Horde_Timezone 1.0.9 stable > Horde_Token 2.0.7 stable > Horde_Translation 2.2.0 stable > Horde_Tree 2.0.4 stable > Horde_Url 2.2.4 stable > Horde_Util 2.5.6 stable > Horde_Vfs 2.3.0 stable > Horde_View 2.0.5 stable > Horde_Xml_Element 2.0.3 stable > Horde_Xml_Wbxml 2.0.2 stable > content 2.0.5 stable > gollem 3.0.6 stable > horde 5.2.8 stable > horde_lz4 1.0.8 stable > imp 6.2.11 stable > ingo 3.2.7 stable > kronolith 4.2.11 stable > mnemo 4.2.8 stable > nag 4.2.6 stable > timeobjects 2.1.0 stable > trean 1.1.3 stable > turba 4.2.10 stable > webmail 5.2.11 stable This seems fine. Whatever is going on with your server doesn't seem to be an issue with incorrect packages installed. >>> I any case I need to preserve the settings and the active-sync >>> status of the clients, as I have a testing group involved there. >>> >>> Kind regards, Jens. >>> -- >>> Horde mailing list >>> Frequently Asked Questions: http://horde.org/faq/ >>> To unsubscribe, mail: horde-unsubscribe at lists.horde.org >> >> >> >> >> > > -- > Horde mailing list > Frequently Asked Questions: http://horde.org/faq/ > To unsubscribe, mail: horde-unsubscribe at lists.horde.org -- mike The Horde Project http://www.horde.org https://www.facebook.com/hordeproject https://www.twitter.com/hordeproject -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5751 bytes Desc: S/MIME Signature URL: From claudioml at mediaservice.net Wed Oct 28 15:37:55 2015 From: claudioml at mediaservice.net (Claudio ML) Date: Wed, 28 Oct 2015 16:37:55 +0100 Subject: [horde] Kronolith invite mail twice Message-ID: <5630EBD3.9070604@mediaservice.net> Hello all, I have a recent problem with kronolith, version 4.2.9 and Thunderbird 38.2.0 with Lightning 4.0.2.1. When a user make a new event, and invite someone, the invited person recieve two invites: one from the Thunderbird Client, and one from the Horde Server. The strange thing is i have some clients sending only one invite (from Thunderbird), and others sending 2 invites. Note: the configuration of thunderbird is the same, also, if i put a calendar which usually sends two invitation into a clean system, it sends two invitation. Into the same Client, if i put a calendar which usually send only one invitation, it sends one. I think is a server setting, but i don't know where to look. I have also searched for similar problems on Internet, but found nothing. Any ideas ? Claudio. From mrubinsk at horde.org Wed Oct 28 16:17:49 2015 From: mrubinsk at horde.org (Michael J Rubinsky) Date: Wed, 28 Oct 2015 16:17:49 +0000 Subject: [horde] Kronolith invite mail twice In-Reply-To: <5630EBD3.9070604@mediaservice.net> Message-ID: <20151028161749.Horde.jhH69GkxT-kEKQRa1bEuB32@h4.theupstairsroom.com> Quoting Claudio ML : > Hello all, > > I have a recent problem with kronolith, version 4.2.9 and Thunderbird > 38.2.0 with Lightning 4.0.2.1. When a user make a new event, and invite > someone, the invited person recieve two invites: one from the > Thunderbird Client, and one from the Horde Server. > > The strange thing is i have some clients sending only one invite (from > Thunderbird), and others sending 2 invites. > > Note: the configuration of thunderbird is the same, also, if i put a > calendar which usually sends two invitation into a clean system, it > sends two invitation. Into the same Client, if i put a calendar which > usually send only one invitation, it sends one. I think is a server > setting, but i don't know where to look. I have also searched for > similar problems on Internet, but found nothing. > > Any ideas ? > > Claudio. > > -- > Horde mailing list > Frequently Asked Questions: http://horde.org/faq/ > To unsubscribe, mail: horde-unsubscribe at lists.horde.org When operating over dav, it is the server's responsibility to send the iTip message. Thunderbird should not be sending them. No idea why one calendar is doing it and another is not though. There is no configuration on Horde's side to enable/disable sending them. -- mike The Horde Project http://www.horde.org https://www.facebook.com/hordeproject https://www.twitter.com/hordeproject -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5751 bytes Desc: S/MIME Signature URL: From jens.gruentjes at ebira.de Wed Oct 28 19:48:33 2015 From: jens.gruentjes at ebira.de (Jens =?utf-8?b?R3LDvG50amVz?=) Date: Wed, 28 Oct 2015 19:48:33 +0000 Subject: [horde] PHP-related errors in Horde after upgrading to Debian Jessie In-Reply-To: <20150908074943.Horde.sruEdbu98U7xv44r94xVj3B@localhost> References: <20150903102125.Horde.hmcwIM95EVZlUvKvB-MXkUG@mail.ebira.de> <20150903141115.Horde.GvlFfDUcFUlfZOeUtVgCRDg@h4.theupstairsroom.com> <20150903162138.Horde.WljtrmDg20gcemrNM5wVux4@mail.ebira.de> <20150908063241.Horde.EXf746s0jdo2ld4Aav9AF9Q@mail.ebira.de> <20150908074943.Horde.sruEdbu98U7xv44r94xVj3B@localhost> Message-ID: <20151028194833.Horde.82LlwNbciSu2ptVEkhY9EPD@mail.ebira.de> Zitat von Michael J Rubinsky : > Quoting Jens Gr?ntjes : > >> Zitat von Jens Gr?ntjes : >> >>> Zitat von Michael J Rubinsky : >>> >>>> Quoting Jens Gr?ntjes : >>>> >>>>> Hello list, >>>>> >>>>> after I upgraded my server to Debian Jessie I have problems with >>>>> horde. I'm quite sure this isn't a Horde bug but I'm hoping that >>>>> some of you experts have some hints for me. >>>>> >>>>> I'm having trouble when calling https://mydomain.de/horde/services/portal >>>>> >>>>> The log show this stack trace >>>>> >>>>> >>>>> 2015-09-03T10:05:16+02:00 DEBUG: HORDE [kronolith] Horde_Prefs: >>>>> Storing preference value (display_external_cals) [pid 1693 on >>>>> line 532 of "/var/www/horde/kronolith/lib/CalendarsManager.php"] >>>>> 2015-09-03T10:05:16+02:00 DEBUG: HORDE [kronolith] Horde_Prefs: >>>>> Storing preference value (display_remote_cals) [pid 1693 on line >>>>> 615 of "/var/www/horde/kronolith/lib/CalendarsManager.php"] >>>>> 2015-09-03T10:05:16+02:00 DEBUG: HORDE [kronolith] PHP ERROR: >>>>> Non-static method Date_TimeZone::isValidID() should not be >>>>> called statically, assuming $this from incompatible context [pid >>>>> 1693 on line 4717 of "/usr/share/php/Date/TimeZone.php"] >>>>> 2015-09-03T10:05:16+02:00 DEBUG: HORDE 1. >>>>> Horde_Core_Block_Layout_View->toHtml() >>>>> /var/www/horde/services/portal/index.php:35 >>>>> 2. Horde_Core_Block->getContent() >>>>> /usr/share/php/Horde/Core/Block/Layout/View.php:98 >>>>> 3. Horde_Core_Block->_call() /usr/share/php/Horde/Core/Block.php:175 >>>>> 4. Kronolith_Block_Summary->_content() >>>>> /usr/share/php/Horde/Core/Block.php:278 >>>>> 5. Kronolith::listCalendars() >>>>> /var/www/horde/kronolith/lib/Block/Summary.php:95 >>>>> 6. Kronolith_CalendarsManager->get() >>>>> /var/www/horde/kronolith/lib/Kronolith.php:1109 >>>>> 7. Kronolith_CalendarsManager->_getAllHolidays() >>>>> /var/www/horde/kronolith/lib/CalendarsManager.php:201 >>>>> 8. class_exists() /var/www/horde/kronolith/lib/CalendarsManager.php:546 >>>>> 9. spl_autoload_call() >>>>> 10. Horde_Autoloader_Cache->loadClass() >>>>> 11. Horde_Autoloader->loadClass() >>>>> /usr/share/php/Horde/Autoloader/Cache.php:126 >>>>> 12. Horde_Autoloader->_include() /usr/share/php/Horde/Autoloader.php:65 >>>>> 13. include() /usr/share/php/Horde/Autoloader.php:128 >>>>> 14. require_once() /usr/share/php/Date/Holidays.php:39 >>>>> 15. require_once() /usr/share/php/Date.php:55 >>>>> 16. Horde_ErrorHandler::errorHandler() >>>>> /usr/share/php/Date/TimeZone.php:4717 >>>>> >>>>> 2015-09-03T10:05:16+02:00 DEBUG: HORDE [kronolith] PHP ERROR: >>>>> Non-static method Date_TimeZone::setDefault() should not be >>>>> called statically, assuming $this from incompatible context [pid >>>>> 1693 on line 4718 of "/usr/share/php/Date/TimeZone.php"] >>>>> 2015-09-03T10:05:16+02:00 DEBUG: HORDE 1. >>>>> Horde_Core_Block_Layout_View->toHtml() >>>>> /var/www/horde/services/portal/index.php:35 >>>>> 2. Horde_Core_Block->getContent() >>>>> /usr/share/php/Horde/Core/Block/Layout/View.php:98 >>>>> 3. Horde_Core_Block->_call() /usr/share/php/Horde/Core/Block.php:175 >>>>> 4. Kronolith_Block_Summary->_content() >>>>> /usr/share/php/Horde/Core/Block.php:278 >>>>> 5. Kronolith::listCalendars() >>>>> /var/www/horde/kronolith/lib/Block/Summary.php:95 >>>>> 6. Kronolith_CalendarsManager->get() >>>>> /var/www/horde/kronolith/lib/Kronolith.php:1109 >>>>> 7. Kronolith_CalendarsManager->_getAllHolidays() >>>>> /var/www/horde/kronolith/lib/CalendarsManager.php:201 >>>>> 8. class_exists() /var/www/horde/kronolith/lib/CalendarsManager.php:546 >>>>> 9. spl_autoload_call() >>>>> 10. Horde_Autoloader_Cache->loadClass() >>>>> 11. Horde_Autoloader->loadClass() >>>>> /usr/share/php/Horde/Autoloader/Cache.php:126 >>>>> 12. Horde_Autoloader->_include() /usr/share/php/Horde/Autoloader.php:65 >>>>> 13. include() /usr/share/php/Horde/Autoloader.php:128 >>>>> 14. require_once() /usr/share/php/Date/Holidays.php:39 >>>>> 15. require_once() /usr/share/php/Date.php:55 >>>>> 16. Horde_ErrorHandler::errorHandler() >>>>> /usr/share/php/Date/TimeZone.php:4718 >>>>> >>>>> 2015-09-03T10:05:16+02:00 DEBUG: HORDE [kronolith] PHP ERROR: >>>>> Non-static method Date_TimeZone::isValidID() should not be >>>>> called statically, assuming $this from incompatible context [pid >>>>> 1693 on line 192 of "/usr/share/php/Date/TimeZone.php"] >>>>> 2015-09-03T10:05:16+02:00 DEBUG: HORDE 1. >>>>> Horde_Core_Block_Layout_View->toHtml() >>>>> /var/www/horde/services/portal/index.php:35 >>>>> 2. Horde_Core_Block->getContent() >>>>> /usr/share/php/Horde/Core/Block/Layout/View.php:98 >>>>> 3. Horde_Core_Block->_call() /usr/share/php/Horde/Core/Block.php:175 >>>>> 4. Kronolith_Block_Summary->_content() >>>>> /usr/share/php/Horde/Core/Block.php:278 >>>>> 5. Kronolith::listCalendars() >>>>> /var/www/horde/kronolith/lib/Block/Summary.php:95 >>>>> 6. Kronolith_CalendarsManager->get() >>>>> /var/www/horde/kronolith/lib/Kronolith.php:1109 >>>>> 7. Kronolith_CalendarsManager->_getAllHolidays() >>>>> /var/www/horde/kronolith/lib/CalendarsManager.php:201 >>>>> 8. class_exists() /var/www/horde/kronolith/lib/CalendarsManager.php:546 >>>>> 9. spl_autoload_call() >>>>> 10. Horde_Autoloader_Cache->loadClass() >>>>> 11. Horde_Autoloader->loadClass() >>>>> /usr/share/php/Horde/Autoloader/Cache.php:126 >>>>> 12. Horde_Autoloader->_include() /usr/share/php/Horde/Autoloader.php:65 >>>>> 13. include() /usr/share/php/Horde/Autoloader.php:128 >>>>> 14. require_once() /usr/share/php/Date/Holidays.php:39 >>>>> 15. require_once() /usr/share/php/Date.php:55 >>>>> 16. Date_TimeZone->setDefault() /usr/share/php/Date/TimeZone.php:4718 >>>>> 17. Horde_ErrorHandler::errorHandler() >>>>> /usr/share/php/Date/TimeZone.php:192 >>>>> >>>>> >>>>> It goes on with a some more lines like these. >>>>> >>>>> The browser displays only "500 - Internal Server Error". When I >>>>> manually enter in the browser https://mydomain.de/horde/imp I >>>>> can read and write mails as usual. >>>>> >>>>> Has anyone a hint for me what is going wrong in my setup? Or do >>>>> you need further information? I'm running the latest pear >>>>> packages of horde. PHP Version is: >>>>> >>>>> boromir /var/www/horde/config # php -v >>>>> PHP 5.6.12-0+deb8u1 (cli) (built: Aug 26 2015 12:23:30) >>>>> Copyright (c) 1997-2015 The PHP Group >>>>> Zend Engine v2.6.0, Copyright (c) 1998-2015 Zend Technologies >>>>> with XCache v3.2.0, Copyright (c) 2005-2014, by mOo >>>>> with Zend OPcache v7.0.6-dev, Copyright (c) 1999-2015, by Zend >>>>> Technologies >>>>> with Xdebug v2.2.5, Copyright (c) 2002-2014, by Derick Rethans >>>>> with XCache Optimizer v3.2.0, Copyright (c) 2005-2014, by mOo >>>>> with XCache Cacher v3.2.0, Copyright (c) 2005-2014, by mOo >>>>> with XCache Coverager v3.2.0, Copyright (c) 2005-2014, by mOo >>>>> >>>>> The webserver is lighttpd: >>>>> boromir /var/www/horde/config # lighttpd -v >>>>> lighttpd/1.4.35 (ssl) - a light and fast webserver >>>>> Build-Date: Nov 2 2014 03:43:48 >>>> >>>> Try removing the PEAR Date_Holiday package. It has a dependency >>>> on PEAR Date package, which is unmaintained, and is the source of >>>> the errors you list. >>> >>> Thanks for the quick reply. I uninstalled the packages >>> Date_Holidays and all related packages (Date_Holidays_German, >>> ...). If I got yout point the actual reason for the errors ist the >>> Date package which I also uninstalled. Then I receive the >>> following error in the log (and similar in the browser window): >>> >>> 2015-09-03T18:09:33+02:00 EMERG: HORDE [kronolith] Class >>> 'Date_Calc' not found [pid 1367 on line 115 of >>> "/var/www/horde/kronolith/lib/Day.php"] >>> 2015-09-03T18:09:33+02:00 DEBUG: HORDE 1. >>> Horde_ErrorHandler::catchFatalError() >>> >>> Maybe I was wrong with uninstalling the Date package so I >>> reinstalled it. Then I get the previously mentionend "500 - >>> Internal Server Error". The log shows: >>> >>> 2015-09-03T18:19:02+02:00 DEBUG: HORDE [kronolith] PHP ERROR: >>> Non-static method Date_Calc::dateDiff() should not be called >>> statically, assuming $this from incompatible context [pid 1372 on >>> line 115 of "/var/www/horde/kronolith/lib/Day.php"] >>> 2015-09-03T18:19:02+02:00 DEBUG: HORDE 1. >>> Horde_Core_Block_Layout_View->toHtml() >>> /var/www/horde/services/portal/index.php:35 >>> 2. Horde_Core_Block->getContent() >>> /usr/share/php/Horde/Core/Block/Layout/View.php:98 >>> 3. Horde_Core_Block->_call() /usr/share/php/Horde/Core/Block.php:175 >>> 4. Kronolith_Block_Summary->_content() >>> /usr/share/php/Horde/Core/Block.php:278 >>> 5. Kronolith_Day->diff() /var/www/horde/kronolith/lib/Block/Summary.php:157 >>> 6. Horde_ErrorHandler::errorHandler() >>> /var/www/horde/kronolith/lib/Day.php:115 >>> >>> 2015-09-03T18:19:02+02:00 DEBUG: HORDE [kronolith] PHP ERROR: >>> Non-static method Date_Calc::isValidDate() should not be called >>> statically, assuming $this from incompatible context [pid 1372 on >>> line 2061 of "/usr/share/php/Date/Calc.php"] >>> 2015-09-03T18:19:02+02:00 DEBUG: HORDE 1. >>> Horde_Core_Block_Layout_View->toHtml() >>> /var/www/horde/services/portal/index.php:35 >>> 2. Horde_Core_Block->getContent() >>> /usr/share/php/Horde/Core/Block/Layout/View.php:98 >>> 3. Horde_Core_Block->_call() /usr/share/php/Horde/Core/Block.php:175 >>> 4. Kronolith_Block_Summary->_content() >>> /usr/share/php/Horde/Core/Block.php:278 >>> 5. Kronolith_Day->diff() /var/www/horde/kronolith/lib/Block/Summary.php:157 >>> 6. Date_Calc->dateDiff() /var/www/horde/kronolith/lib/Day.php:116 >>> 7. Horde_ErrorHandler::errorHandler() /usr/share/php/Date/Calc.php:2061 >>> >>> 2015-09-03T18:19:02+02:00 DEBUG: HORDE [kronolith] PHP ERROR: >>> Non-static method Date_Calc::isValidDate() should not be called >>> statically, assuming $this from incompatible context [pid 1372 on >>> line 2064 of "/usr/share/php/Date/Calc.php"] >>> 2015-09-03T18:19:02+02:00 DEBUG: HORDE 1. >>> Horde_Core_Block_Layout_View->toHtml() >>> /var/www/horde/services/portal/index.php:35 >>> 2. Horde_Core_Block->getContent() >>> /usr/share/php/Horde/Core/Block/Layout/View.php:98 >>> 3. Horde_Core_Block->_call() /usr/share/php/Horde/Core/Block.php:175 >>> 4. Kronolith_Block_Summary->_content() >>> /usr/share/php/Horde/Core/Block.php:278 >>> 5. Kronolith_Day->diff() /var/www/horde/kronolith/lib/Block/Summary.php:157 >>> 6. Date_Calc->dateDiff() /var/www/horde/kronolith/lib/Day.php:116 >>> 7. Horde_ErrorHandler::errorHandler() /usr/share/php/Date/Calc.php:2064 >>> >>> So it's a different error but the same result. Have you any more hints? >>> >>> Greetings >>> Jens >> >> Instead fo fixing the error I could maybe change the >> error_reporting level for PHP. Unfortunately I cannot see the horde >> config page because it raises similar errors. Can I set it to >> >> error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT >> >> manually in one of horde's config files? > > horde/config/conf.php - 'debug_level' I just found the time to take care of that annoying bug in my installation. I set the error_reporting to the values above in conf.php but nothing changed regarding my bug. So I checked the value for "error_reporting" in the phpinfo()-screen which I called from Horde's test.php. The "Local value" is 32767 (which I think is E_ALL) and the "Master value" is 22527 (which I think is E_ALL & ~E_DEPRECATED & ~E_STRICT). When I call phpinfo() from a php-file outside of Horde both the Local and the Master value are at 22527. When I call phpinfo() in the Horde PHP Shell I get a Local value of 30711 (which I think is E_ALL & ~E_STRICT & ~E_NOTICE). The Master value is again 22527. Now I'm very confused where these different values come from or where I probably defined them. In /etc/php5/cgi/php.ini I set error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT. Are there other places where I should have a look? Any help is greatly appreciated. -- Yours Jens From ballier at mail.schule.de Wed Oct 28 20:26:27 2015 From: ballier at mail.schule.de (Ralph Ballier) Date: Wed, 28 Oct 2015 21:26:27 +0100 Subject: [horde] Horde and NetDrive Message-ID: <20151028212627.Horde.KuqKuWJPtMHAsBQhGPhF51Q@horde.osz-lise-meitner.eu> Zitat von Michael J Rubinsky : > Quoting Ralph Ballier : > >> Hallo, >> >> is it possible to connect the file manager of Horde over NetDrive to >> get a >> cloud drive? > > I haven't used NetDrive, but a quick glance at their website shows that > it supports FTP access? If so, you could configure Gollem to use a FTP > VFS. See gollem/config/backends.php for more details on the > configuration options. > > -- > mike > The Horde Project > http://www.horde.org > https://www.facebook.com/hordeprojecthttps://www.twitter.com/hordeproject Hello, thanks for your hints. It works very well with FTP and NetDrive. But I miss the possibility to give single users or groups rights for single files or directories. Therefore I go back to 'sqlhome'. Ralph Ralph Ballier Abteilungsleiter an der Lise-Meitner-Schule Rudower Stra?e 184 12351 Berlin Tel.: +49 30 660689-25/-24/-0 From ballier at mail.schule.de Thu Oct 29 11:47:39 2015 From: ballier at mail.schule.de (Ralph Ballier) Date: Thu, 29 Oct 2015 12:47:39 +0100 Subject: [horde] Shall I use ActiveSync? Message-ID: <20151029124739.Horde.i9i6DkZTqmPDDr4NbkVY7Jt@horde.osz-lise-meitner.eu> Hello, I use from Android so far the apps "CALDAV sync" and "CARDDav sync" and it seems to work very well. Now I had heared that ActiveSync is a world wide standard and it isn't necessary to install several apps. I have try it. For mail it works very well, but for calenders it mixed all calenders in one. This is not better, when I cross "separate calender". Or it show my own calender only. I use Android 5.1.1. Where is the big advantage to use ActiveSync? Ralph From mrubinsk at horde.org Thu Oct 29 12:08:42 2015 From: mrubinsk at horde.org (Michael J Rubinsky) Date: Thu, 29 Oct 2015 12:08:42 +0000 Subject: [horde] Shall I use ActiveSync? In-Reply-To: <20151029124739.Horde.i9i6DkZTqmPDDr4NbkVY7Jt@horde.osz-lise-meitner.eu> Message-ID: <20151029120842.Horde.p_kqKSke5pSAL4M7CSFAewv@h4.theupstairsroom.com> Quoting Ralph Ballier : > Hello, > > I use from Android so far the apps "CALDAV sync" and "CARDDav sync" and it > seems to work very well. > > Now I had heared that ActiveSync is a world wide standard and it isn't > necessary to install several apps. I have try it. > > For mail it works very well, but for calenders it mixed all calenders in > one. This is not better, when I cross "separate calender". Or it show my > own calender only. This is because some versions of ActiveSync only support synchronizing the user's single main calendar (or addressbook, notepad etc...). We purposely "multiplex" all of the user's personal calendars together into a single calendar to sync with the client when this is the case. More and more clients are supporting separate collections now though, so the option to use them is present in the prefs. Since any user may have multiple devices attached to their account, we also attempt to sniff out the client in use and automatically turn off this ability when we know the client does not support it. That being said, last I checked Android 5.0 supported individual calendars - but no other individual collections. The opposite of what you are reporting. After checking the "separate calendars" preference, have you made sure that all of the calendars you wish to sync are included in the "synchronization" prefs? Have you re-created the account on the client (depending on the client it might not pick up the change automatically). > I use Android 5.1.1. > > Where is the big advantage to use ActiveSync? The biggest advantages, IMO, are that ActiveSync clients are built in to just about every mobile client you can think of out of the box, plus some non-mobile clients like Microsoft Outlook and Windows Mail. It (usually) integrates nicely with other software on the devices, and only requires a single account to be configured that sets up Mail, Calendar, Notes, Tasks, and Contacts (which usually will only require a single email address and password if the server is setup correctly). If the client is fully featured, you can do things that you can't normally do with just a *dav connection. Things like setting your out of office message, viewing a user's freebusy times when scheduling a meeting, integration between email/calendar when handling iTips etc... Replying to or forwarding a large email potentially uses less bandwidth because the ActiveSync client will only send the new part of the email - building the reply message on the server by getting the original email directly from the IMAP server. In fact, bandwidth usage will typically be smaller for ANY information synchronized when compared to *dav since ActiveSync uses wbxml - a binary encoded/compressed form of xml. The biggest disadvantage is that there are a LOT of buggy clients out there, and some minor inconsistencies in the protocol itself but this is getting better and better every year. -- mike The Horde Project http://www.horde.org https://www.facebook.com/hordeproject https://www.twitter.com/hordeproject -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5751 bytes Desc: S/MIME Signature URL: From mtecles at biof.ufrj.br Thu Oct 29 12:39:15 2015 From: mtecles at biof.ufrj.br (Mauricio Jose T. Tecles) Date: Thu, 29 Oct 2015 10:39:15 -0200 Subject: [horde] Installation on Debian 8 (Pear) Wiki Message-ID: <20151029103915.Horde.R6T_uMPk0qR9vwiD8zlKpg2@webmail.biof.ufrj.br> Hi all. I have created a Wiki entry on how to install Horde on Debian 8 (Jessie), the way I do it. I've been installing Horde applications separetedly for so long (+10 years) that I forget Webmail blundle. Consider installing Webmail blundle, it's much less work and takes care of most of the tasks on the page. http://wiki.horde.org/DebJessieHorde5?referrer=HowTo Thank you Michael for the note and corrections. Mauricio Maur?cio Jos? T. Tecles N?cleo de Inform?tica Instituto de Biof?sica Carlos Chagas Filho - UFRJ Av. Carlos Chagas Filho, 373 mtecles at biof.ufrj.br Tel.: (21) 3938-6526 ou 3938-6544 From mrubinsk at horde.org Thu Oct 29 12:54:53 2015 From: mrubinsk at horde.org (Michael J Rubinsky) Date: Thu, 29 Oct 2015 12:54:53 +0000 Subject: [horde] PHP-related errors in Horde after upgrading to Debian Jessie In-Reply-To: <20151028194833.Horde.82LlwNbciSu2ptVEkhY9EPD@mail.ebira.de> References: <20150903102125.Horde.hmcwIM95EVZlUvKvB-MXkUG@mail.ebira.de> <20150903141115.Horde.GvlFfDUcFUlfZOeUtVgCRDg@h4.theupstairsroom.com> <20150903162138.Horde.WljtrmDg20gcemrNM5wVux4@mail.ebira.de> <20150908063241.Horde.EXf746s0jdo2ld4Aav9AF9Q@mail.ebira.de> <20150908074943.Horde.sruEdbu98U7xv44r94xVj3B@localhost> <20151028194833.Horde.82LlwNbciSu2ptVEkhY9EPD@mail.ebira.de> Message-ID: <20151029125453.Horde.WqFSU50WmlmQEFiKPmlrypT@h4.theupstairsroom.com> Quoting Jens Gr?ntjes : > Zitat von Michael J Rubinsky : > >> Quoting Jens Gr?ntjes : >> >>> Zitat von Jens Gr?ntjes : >>> >>>> Zitat von Michael J Rubinsky : >>>> >>>>> Quoting Jens Gr?ntjes : >>>>> >>>>>> Hello list, >>>>>> >>>>>> after I upgraded my server to Debian Jessie I have problems >>>>>> with horde. I'm quite sure this isn't a Horde bug but I'm >>>>>> hoping that some of you experts have some hints for me. >>>>>> >>>>>> I'm having trouble when calling >>>>>> https://mydomain.de/horde/services/portal >>>>>> >>>>>> The log show this stack trace >>>>>> >>>>>> >>>>>> 2015-09-03T10:05:16+02:00 DEBUG: HORDE [kronolith] Horde_Prefs: >>>>>> Storing preference value (display_external_cals) [pid 1693 on >>>>>> line 532 of "/var/www/horde/kronolith/lib/CalendarsManager.php"] >>>>>> 2015-09-03T10:05:16+02:00 DEBUG: HORDE [kronolith] Horde_Prefs: >>>>>> Storing preference value (display_remote_cals) [pid 1693 on >>>>>> line 615 of "/var/www/horde/kronolith/lib/CalendarsManager.php"] >>>>>> 2015-09-03T10:05:16+02:00 DEBUG: HORDE [kronolith] PHP ERROR: >>>>>> Non-static method Date_TimeZone::isValidID() should not be >>>>>> called statically, assuming $this from incompatible context >>>>>> [pid 1693 on line 4717 of "/usr/share/php/Date/TimeZone.php"] >>>>>> 2015-09-03T10:05:16+02:00 DEBUG: HORDE 1. >>>>>> Horde_Core_Block_Layout_View->toHtml() >>>>>> /var/www/horde/services/portal/index.php:35 >>>>>> 2. Horde_Core_Block->getContent() >>>>>> /usr/share/php/Horde/Core/Block/Layout/View.php:98 >>>>>> 3. Horde_Core_Block->_call() /usr/share/php/Horde/Core/Block.php:175 >>>>>> 4. Kronolith_Block_Summary->_content() >>>>>> /usr/share/php/Horde/Core/Block.php:278 >>>>>> 5. Kronolith::listCalendars() >>>>>> /var/www/horde/kronolith/lib/Block/Summary.php:95 >>>>>> 6. Kronolith_CalendarsManager->get() >>>>>> /var/www/horde/kronolith/lib/Kronolith.php:1109 >>>>>> 7. Kronolith_CalendarsManager->_getAllHolidays() >>>>>> /var/www/horde/kronolith/lib/CalendarsManager.php:201 >>>>>> 8. class_exists() /var/www/horde/kronolith/lib/CalendarsManager.php:546 >>>>>> 9. spl_autoload_call() >>>>>> 10. Horde_Autoloader_Cache->loadClass() >>>>>> 11. Horde_Autoloader->loadClass() >>>>>> /usr/share/php/Horde/Autoloader/Cache.php:126 >>>>>> 12. Horde_Autoloader->_include() /usr/share/php/Horde/Autoloader.php:65 >>>>>> 13. include() /usr/share/php/Horde/Autoloader.php:128 >>>>>> 14. require_once() /usr/share/php/Date/Holidays.php:39 >>>>>> 15. require_once() /usr/share/php/Date.php:55 >>>>>> 16. Horde_ErrorHandler::errorHandler() >>>>>> /usr/share/php/Date/TimeZone.php:4717 >>>>>> >>>>>> 2015-09-03T10:05:16+02:00 DEBUG: HORDE [kronolith] PHP ERROR: >>>>>> Non-static method Date_TimeZone::setDefault() should not be >>>>>> called statically, assuming $this from incompatible context >>>>>> [pid 1693 on line 4718 of "/usr/share/php/Date/TimeZone.php"] >>>>>> 2015-09-03T10:05:16+02:00 DEBUG: HORDE 1. >>>>>> Horde_Core_Block_Layout_View->toHtml() >>>>>> /var/www/horde/services/portal/index.php:35 >>>>>> 2. Horde_Core_Block->getContent() >>>>>> /usr/share/php/Horde/Core/Block/Layout/View.php:98 >>>>>> 3. Horde_Core_Block->_call() /usr/share/php/Horde/Core/Block.php:175 >>>>>> 4. Kronolith_Block_Summary->_content() >>>>>> /usr/share/php/Horde/Core/Block.php:278 >>>>>> 5. Kronolith::listCalendars() >>>>>> /var/www/horde/kronolith/lib/Block/Summary.php:95 >>>>>> 6. Kronolith_CalendarsManager->get() >>>>>> /var/www/horde/kronolith/lib/Kronolith.php:1109 >>>>>> 7. Kronolith_CalendarsManager->_getAllHolidays() >>>>>> /var/www/horde/kronolith/lib/CalendarsManager.php:201 >>>>>> 8. class_exists() /var/www/horde/kronolith/lib/CalendarsManager.php:546 >>>>>> 9. spl_autoload_call() >>>>>> 10. Horde_Autoloader_Cache->loadClass() >>>>>> 11. Horde_Autoloader->loadClass() >>>>>> /usr/share/php/Horde/Autoloader/Cache.php:126 >>>>>> 12. Horde_Autoloader->_include() /usr/share/php/Horde/Autoloader.php:65 >>>>>> 13. include() /usr/share/php/Horde/Autoloader.php:128 >>>>>> 14. require_once() /usr/share/php/Date/Holidays.php:39 >>>>>> 15. require_once() /usr/share/php/Date.php:55 >>>>>> 16. Horde_ErrorHandler::errorHandler() >>>>>> /usr/share/php/Date/TimeZone.php:4718 >>>>>> >>>>>> 2015-09-03T10:05:16+02:00 DEBUG: HORDE [kronolith] PHP ERROR: >>>>>> Non-static method Date_TimeZone::isValidID() should not be >>>>>> called statically, assuming $this from incompatible context >>>>>> [pid 1693 on line 192 of "/usr/share/php/Date/TimeZone.php"] >>>>>> 2015-09-03T10:05:16+02:00 DEBUG: HORDE 1. >>>>>> Horde_Core_Block_Layout_View->toHtml() >>>>>> /var/www/horde/services/portal/index.php:35 >>>>>> 2. Horde_Core_Block->getContent() >>>>>> /usr/share/php/Horde/Core/Block/Layout/View.php:98 >>>>>> 3. Horde_Core_Block->_call() /usr/share/php/Horde/Core/Block.php:175 >>>>>> 4. Kronolith_Block_Summary->_content() >>>>>> /usr/share/php/Horde/Core/Block.php:278 >>>>>> 5. Kronolith::listCalendars() >>>>>> /var/www/horde/kronolith/lib/Block/Summary.php:95 >>>>>> 6. Kronolith_CalendarsManager->get() >>>>>> /var/www/horde/kronolith/lib/Kronolith.php:1109 >>>>>> 7. Kronolith_CalendarsManager->_getAllHolidays() >>>>>> /var/www/horde/kronolith/lib/CalendarsManager.php:201 >>>>>> 8. class_exists() /var/www/horde/kronolith/lib/CalendarsManager.php:546 >>>>>> 9. spl_autoload_call() >>>>>> 10. Horde_Autoloader_Cache->loadClass() >>>>>> 11. Horde_Autoloader->loadClass() >>>>>> /usr/share/php/Horde/Autoloader/Cache.php:126 >>>>>> 12. Horde_Autoloader->_include() /usr/share/php/Horde/Autoloader.php:65 >>>>>> 13. include() /usr/share/php/Horde/Autoloader.php:128 >>>>>> 14. require_once() /usr/share/php/Date/Holidays.php:39 >>>>>> 15. require_once() /usr/share/php/Date.php:55 >>>>>> 16. Date_TimeZone->setDefault() /usr/share/php/Date/TimeZone.php:4718 >>>>>> 17. Horde_ErrorHandler::errorHandler() >>>>>> /usr/share/php/Date/TimeZone.php:192 >>>>>> >>>>>> >>>>>> It goes on with a some more lines like these. >>>>>> >>>>>> The browser displays only "500 - Internal Server Error". When I >>>>>> manually enter in the browser https://mydomain.de/horde/imp I >>>>>> can read and write mails as usual. >>>>>> >>>>>> Has anyone a hint for me what is going wrong in my setup? Or do >>>>>> you need further information? I'm running the latest pear >>>>>> packages of horde. PHP Version is: >>>>>> >>>>>> boromir /var/www/horde/config # php -v >>>>>> PHP 5.6.12-0+deb8u1 (cli) (built: Aug 26 2015 12:23:30) >>>>>> Copyright (c) 1997-2015 The PHP Group >>>>>> Zend Engine v2.6.0, Copyright (c) 1998-2015 Zend Technologies >>>>>> with XCache v3.2.0, Copyright (c) 2005-2014, by mOo >>>>>> with Zend OPcache v7.0.6-dev, Copyright (c) 1999-2015, by Zend >>>>>> Technologies >>>>>> with Xdebug v2.2.5, Copyright (c) 2002-2014, by Derick Rethans >>>>>> with XCache Optimizer v3.2.0, Copyright (c) 2005-2014, by mOo >>>>>> with XCache Cacher v3.2.0, Copyright (c) 2005-2014, by mOo >>>>>> with XCache Coverager v3.2.0, Copyright (c) 2005-2014, by mOo >>>>>> >>>>>> The webserver is lighttpd: >>>>>> boromir /var/www/horde/config # lighttpd -v >>>>>> lighttpd/1.4.35 (ssl) - a light and fast webserver >>>>>> Build-Date: Nov 2 2014 03:43:48 >>>>> >>>>> Try removing the PEAR Date_Holiday package. It has a dependency >>>>> on PEAR Date package, which is unmaintained, and is the source >>>>> of the errors you list. >>>> >>>> Thanks for the quick reply. I uninstalled the packages >>>> Date_Holidays and all related packages (Date_Holidays_German, >>>> ...). If I got yout point the actual reason for the errors ist >>>> the Date package which I also uninstalled. Then I receive the >>>> following error in the log (and similar in the browser window): >>>> >>>> 2015-09-03T18:09:33+02:00 EMERG: HORDE [kronolith] Class >>>> 'Date_Calc' not found [pid 1367 on line 115 of >>>> "/var/www/horde/kronolith/lib/Day.php"] >>>> 2015-09-03T18:09:33+02:00 DEBUG: HORDE 1. >>>> Horde_ErrorHandler::catchFatalError() >>>> >>>> Maybe I was wrong with uninstalling the Date package so I >>>> reinstalled it. Then I get the previously mentionend "500 - >>>> Internal Server Error". The log shows: >>>> >>>> 2015-09-03T18:19:02+02:00 DEBUG: HORDE [kronolith] PHP ERROR: >>>> Non-static method Date_Calc::dateDiff() should not be called >>>> statically, assuming $this from incompatible context [pid 1372 on >>>> line 115 of "/var/www/horde/kronolith/lib/Day.php"] >>>> 2015-09-03T18:19:02+02:00 DEBUG: HORDE 1. >>>> Horde_Core_Block_Layout_View->toHtml() >>>> /var/www/horde/services/portal/index.php:35 >>>> 2. Horde_Core_Block->getContent() >>>> /usr/share/php/Horde/Core/Block/Layout/View.php:98 >>>> 3. Horde_Core_Block->_call() /usr/share/php/Horde/Core/Block.php:175 >>>> 4. Kronolith_Block_Summary->_content() >>>> /usr/share/php/Horde/Core/Block.php:278 >>>> 5. Kronolith_Day->diff() >>>> /var/www/horde/kronolith/lib/Block/Summary.php:157 >>>> 6. Horde_ErrorHandler::errorHandler() >>>> /var/www/horde/kronolith/lib/Day.php:115 >>>> >>>> 2015-09-03T18:19:02+02:00 DEBUG: HORDE [kronolith] PHP ERROR: >>>> Non-static method Date_Calc::isValidDate() should not be called >>>> statically, assuming $this from incompatible context [pid 1372 on >>>> line 2061 of "/usr/share/php/Date/Calc.php"] >>>> 2015-09-03T18:19:02+02:00 DEBUG: HORDE 1. >>>> Horde_Core_Block_Layout_View->toHtml() >>>> /var/www/horde/services/portal/index.php:35 >>>> 2. Horde_Core_Block->getContent() >>>> /usr/share/php/Horde/Core/Block/Layout/View.php:98 >>>> 3. Horde_Core_Block->_call() /usr/share/php/Horde/Core/Block.php:175 >>>> 4. Kronolith_Block_Summary->_content() >>>> /usr/share/php/Horde/Core/Block.php:278 >>>> 5. Kronolith_Day->diff() >>>> /var/www/horde/kronolith/lib/Block/Summary.php:157 >>>> 6. Date_Calc->dateDiff() /var/www/horde/kronolith/lib/Day.php:116 >>>> 7. Horde_ErrorHandler::errorHandler() /usr/share/php/Date/Calc.php:2061 >>>> >>>> 2015-09-03T18:19:02+02:00 DEBUG: HORDE [kronolith] PHP ERROR: >>>> Non-static method Date_Calc::isValidDate() should not be called >>>> statically, assuming $this from incompatible context [pid 1372 on >>>> line 2064 of "/usr/share/php/Date/Calc.php"] >>>> 2015-09-03T18:19:02+02:00 DEBUG: HORDE 1. >>>> Horde_Core_Block_Layout_View->toHtml() >>>> /var/www/horde/services/portal/index.php:35 >>>> 2. Horde_Core_Block->getContent() >>>> /usr/share/php/Horde/Core/Block/Layout/View.php:98 >>>> 3. Horde_Core_Block->_call() /usr/share/php/Horde/Core/Block.php:175 >>>> 4. Kronolith_Block_Summary->_content() >>>> /usr/share/php/Horde/Core/Block.php:278 >>>> 5. Kronolith_Day->diff() >>>> /var/www/horde/kronolith/lib/Block/Summary.php:157 >>>> 6. Date_Calc->dateDiff() /var/www/horde/kronolith/lib/Day.php:116 >>>> 7. Horde_ErrorHandler::errorHandler() /usr/share/php/Date/Calc.php:2064 >>>> >>>> So it's a different error but the same result. Have you any more hints? >>>> >>>> Greetings >>>> Jens >>> >>> Instead fo fixing the error I could maybe change the >>> error_reporting level for PHP. Unfortunately I cannot see the >>> horde config page because it raises similar errors. Can I set it to >>> >>> error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT >>> >>> manually in one of horde's config files? >> >> horde/config/conf.php - 'debug_level' > > I just found the time to take care of that annoying bug in my > installation. I set the error_reporting to the values above in > conf.php but nothing changed regarding my bug. > > So I checked the value for "error_reporting" in the phpinfo()-screen > which I called from Horde's test.php. The "Local value" is 32767 > (which I think is E_ALL) and the "Master value" is 22527 (which I > think is E_ALL & ~E_DEPRECATED & ~E_STRICT). > > When I call phpinfo() from a php-file outside of Horde both the > Local and the Master value are at 22527. > > When I call phpinfo() in the Horde PHP Shell I get a Local value of > 30711 (which I think is E_ALL & ~E_STRICT & ~E_NOTICE). The Master > value is again 22527. > > Now I'm very confused where these different values come from or > where I probably defined them. In /etc/php5/cgi/php.ini I set > error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT. Are there other > places where I should have a look? > > > Any help is greatly appreciated. horde/config/conf.php - 'debug_level' -- mike The Horde Project http://www.horde.org https://www.facebook.com/hordeproject https://www.twitter.com/hordeproject -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5751 bytes Desc: S/MIME Signature URL: From hellermann at we-do.com Thu Oct 29 13:06:21 2015 From: hellermann at we-do.com (Jens Hellermann) Date: Thu, 29 Oct 2015 14:06:21 +0100 Subject: [horde] Update questions Horde Webmail In-Reply-To: <20151028145700.Horde.Gov4j_coX10u6mbnelmuxHV@h4.theupstairsroom.com> References: <20151028123712.Horde.c9s-zl54VvReP9F4ddV8ZKb@h4.theupstairsroom.com> <5630D911.30502@we-do.com> <20151028145700.Horde.Gov4j_coX10u6mbnelmuxHV@h4.theupstairsroom.com> Message-ID: <563219CD.1090805@we-do.com> Am 28.10.2015 um 15:57 schrieb Michael J Rubinsky: > > Quoting Jens Hellermann : > >> Am 28.10.2015 um 13:37 schrieb Michael J Rubinsky: >>> >>> Quoting Jens Hellermann : >>> >>>> Dear Horde List members, >>>> >>>> I have a question concerning updates of Horde Webmail. As I didn't >>>> know better at first (just googled update horde howto), I updated >>>> Horde Webmail following an article in a german debianforum: >>>> >>>> |pear upgrade -f -a -B -c horde >>>> >>>> and afterwards it was recommended to execute some scripts again: >>>> >>>> ||pear run-scripts horde/Horde_Role| >>>> >>>> But now I read in a mail from Michael Rubinsk that I should have used: >>>> >>>> pear upgrade -a -B horde/webmail >>>> >>>> I guess that is also why I lost some php extensions after upgrading. >>>> >>>> In my last update I did follow the method Michael suggested, but >>>> I'm still facing instability issues with the webinterface and >>>> connectivity issues to active sync (which dissapear, when I restart >>>> the whole server). >>>> >>>> My questions now are, how bad is it, I used the wrong update >>>> method? Can these problems result from that and can the process be >>>> reversed somehow, even by installating over the existing >>>> installation? >>> >>> >>> What does: >>> >>> pear list -c horde >>> >>> show? >>> >> Installed packages, channel pear.horde.org: >> =========================================== >> Package Version State >> Horde_ActiveSync 2.30.0 stable >> Horde_Alarm 2.2.5 stable >> Horde_Argv 2.0.11 stable >> Horde_Auth 2.1.10 stable >> Horde_Autoloader 2.1.1 stable >> Horde_Browser 2.0.10 stable >> Horde_Cache 2.5.0 stable >> Horde_Cli 2.0.6 stable >> Horde_Compress 2.1.3 stable >> Horde_Compress_Fast 1.1.0 stable >> Horde_Constraint 2.0.2 stable >> Horde_Controller 2.0.3 stable >> Horde_Core 2.22.1 stable >> Horde_Crypt 2.6.1 stable >> Horde_Crypt_Blowfish 1.1.0 stable >> Horde_CssMinify 1.0.2 stable >> Horde_Css_Parser 1.0.7 stable >> Horde_Data 2.1.3 stable >> Horde_Date 2.1.1 stable >> Horde_Date_Parser 2.0.4 stable >> Horde_Dav 1.1.2 stable >> Horde_Db 2.2.3 stable >> Horde_Editor 2.0.4 stable >> Horde_ElasticSearch 1.0.3 stable >> Horde_Exception 2.0.6 stable >> Horde_Feed 2.0.3 stable >> Horde_Form 2.0.11 stable >> Horde_Group 2.0.5 stable >> Horde_HashTable 1.2.3 stable >> Horde_History 2.3.5 stable >> Horde_Http 2.1.5 stable >> Horde_Icalendar 2.1.1 stable >> Horde_Idna 1.0.3 stable >> Horde_Image 2.3.3 stable >> Horde_Imap_Client 2.29.3 stable >> Horde_Imsp 2.0.8 stable >> Horde_Injector 2.0.4 stable >> Horde_Itip 2.1.0 stable >> Horde_JavascriptMinify 1.1.2 stable >> Horde_JavascriptMinify_Jsmin 1.0.1 stable >> Horde_Kolab_Format 2.0.7 stable >> Horde_Kolab_Server 2.0.4 stable >> Horde_Kolab_Session 2.0.2 stable >> Horde_Kolab_Storage 2.1.4 stable >> Horde_Ldap 2.3.1 stable >> Horde_ListHeaders 1.2.2 stable >> Horde_Lock 2.1.1 stable >> Horde_Log 2.1.2 stable >> Horde_LoginTasks 2.0.5 stable >> Horde_Mail 2.6.2 stable >> Horde_Mail_Autoconfig 1.0.2 stable >> Horde_Mapi 1.0.5 stable >> Horde_Memcache 2.0.7 stable >> Horde_Mime 2.9.2 stable >> Horde_Mime_Viewer 2.1.1 stable >> Horde_Mongo 1.0.3 stable >> Horde_Nls 2.1.0 stable >> Horde_Notification 2.0.3 stable >> Horde_Oauth 2.0.3 stable >> Horde_OpenXchange 1.0.0 stable >> Horde_Pack 1.0.5 stable >> Horde_Pdf 2.0.6 stable >> Horde_Perms 2.1.5 stable >> Horde_Prefs 2.7.4 stable >> Horde_Queue 1.1.3 stable >> Horde_Rdo 2.0.4 stable >> Horde_Role 1.0.1 stable >> Horde_Routes 2.0.4 stable >> Horde_Rpc 2.1.5 stable >> Horde_Scribe 2.0.2 stable >> Horde_Secret 2.0.5 stable >> Horde_Serialize 2.0.4 stable >> Horde_Service_Facebook 2.0.8 stable >> Horde_Service_Gravatar 1.0.0 stable >> Horde_Service_Twitter 2.1.5 stable >> Horde_Service_Weather 2.3.0 stable >> Horde_SessionHandler 2.2.5 stable >> Horde_Share 2.0.7 stable >> Horde_Smtp 1.9.1 stable >> Horde_Socket_Client 2.0.0 stable >> Horde_SpellChecker 2.1.2 stable >> Horde_Stream 1.6.2 stable >> Horde_Stream_Filter 2.0.3 stable >> Horde_Stream_Wrapper 2.1.2 stable >> Horde_Stringprep 1.0.2 stable >> Horde_Support 2.1.4 stable >> Horde_SyncMl 2.0.5 stable >> Horde_Template 2.0.2 stable >> Horde_Test 2.5.1 stable >> Horde_Text_Diff 2.1.1 stable >> Horde_Text_Filter 2.3.2 stable >> Horde_Text_Filter_Jsmin 1.0.1 stable >> Horde_Text_Flowed 2.0.2 stable >> Horde_Thrift 2.0.2 stable >> Horde_Timezone 1.0.9 stable >> Horde_Token 2.0.7 stable >> Horde_Translation 2.2.0 stable >> Horde_Tree 2.0.4 stable >> Horde_Url 2.2.4 stable >> Horde_Util 2.5.6 stable >> Horde_Vfs 2.3.0 stable >> Horde_View 2.0.5 stable >> Horde_Xml_Element 2.0.3 stable >> Horde_Xml_Wbxml 2.0.2 stable >> content 2.0.5 stable >> gollem 3.0.6 stable >> horde 5.2.8 stable >> horde_lz4 1.0.8 stable >> imp 6.2.11 stable >> ingo 3.2.7 stable >> kronolith 4.2.11 stable >> mnemo 4.2.8 stable >> nag 4.2.6 stable >> timeobjects 2.1.0 stable >> trean 1.1.3 stable >> turba 4.2.10 stable >> webmail 5.2.11 stable > > > This seems fine. Whatever is going on with your server doesn't seem to > be an issue with incorrect packages installed. Thank you, that excludes one more possible wrong going from my side. I discovered today, that if I clone the container that contains the horde (humor intended) and let it run on a different IP, the webinterface stays totally stable. Only when several clients connect via activesync the connection to the imap server (including openchange) becomes instable. I'll migrate the dovecot server to a single installation (without samba and openchange) and see if it stabelizes. Thanks a lot for your help though! > >>>> I any case I need to preserve the settings and the active-sync >>>> status of the clients, as I have a testing group involved there. >>>> >>>> Kind regards, Jens. >>>> -- >>>> Horde mailing list >>>> Frequently Asked Questions: http://horde.org/faq/ >>>> To unsubscribe, mail: horde-unsubscribe at lists.horde.org >>> >>> >>> >>> >>> >> >> -- >> Horde mailing list >> Frequently Asked Questions: http://horde.org/faq/ >> To unsubscribe, mail: horde-unsubscribe at lists.horde.org > > > > > From jens.gruentjes at ebira.de Thu Oct 29 13:06:39 2015 From: jens.gruentjes at ebira.de (Jens =?utf-8?b?R3LDvG50amVz?=) Date: Thu, 29 Oct 2015 13:06:39 +0000 Subject: [horde] PHP-related errors in Horde after upgrading to Debian Jessie In-Reply-To: <20151029125453.Horde.WqFSU50WmlmQEFiKPmlrypT@h4.theupstairsroom.com> References: <20150903102125.Horde.hmcwIM95EVZlUvKvB-MXkUG@mail.ebira.de> <20150903141115.Horde.GvlFfDUcFUlfZOeUtVgCRDg@h4.theupstairsroom.com> <20150903162138.Horde.WljtrmDg20gcemrNM5wVux4@mail.ebira.de> <20150908063241.Horde.EXf746s0jdo2ld4Aav9AF9Q@mail.ebira.de> <20150908074943.Horde.sruEdbu98U7xv44r94xVj3B@localhost> <20151028194833.Horde.82LlwNbciSu2ptVEkhY9EPD@mail.ebira.de> <20151029125453.Horde.WqFSU50WmlmQEFiKPmlrypT@h4.theupstairsroom.com> Message-ID: <20151029130639.Horde.7G8ouZmTsl7O_XzcEn6FPb9@mail.ebira.de> Zitat von Michael J Rubinsky : > Quoting Jens Gr?ntjes : > >> Zitat von Michael J Rubinsky : >> >>> Quoting Jens Gr?ntjes : >>> >>>> Zitat von Jens Gr?ntjes : >>>> >>>>> Zitat von Michael J Rubinsky : >>>>> >>>>>> Quoting Jens Gr?ntjes : >>>>>> >>>>>>> Hello list, >>>>>>> >>>>>>> after I upgraded my server to Debian Jessie I have problems >>>>>>> with horde. I'm quite sure this isn't a Horde bug but I'm >>>>>>> hoping that some of you experts have some hints for me. >>>>>>> >>>>>>> I'm having trouble when calling >>>>>>> https://mydomain.de/horde/services/portal >>>>>>> >>>>>>> The log show this stack trace >>>>>>> >>>>>>> >>>>>>> 2015-09-03T10:05:16+02:00 DEBUG: HORDE [kronolith] >>>>>>> Horde_Prefs: Storing preference value (display_external_cals) >>>>>>> [pid 1693 on line 532 of >>>>>>> "/var/www/horde/kronolith/lib/CalendarsManager.php"] >>>>>>> 2015-09-03T10:05:16+02:00 DEBUG: HORDE [kronolith] >>>>>>> Horde_Prefs: Storing preference value (display_remote_cals) >>>>>>> [pid 1693 on line 615 of >>>>>>> "/var/www/horde/kronolith/lib/CalendarsManager.php"] >>>>>>> 2015-09-03T10:05:16+02:00 DEBUG: HORDE [kronolith] PHP ERROR: >>>>>>> Non-static method Date_TimeZone::isValidID() should not be >>>>>>> called statically, assuming $this from incompatible context >>>>>>> [pid 1693 on line 4717 of "/usr/share/php/Date/TimeZone.php"] >>>>>>> 2015-09-03T10:05:16+02:00 DEBUG: HORDE 1. >>>>>>> Horde_Core_Block_Layout_View->toHtml() >>>>>>> /var/www/horde/services/portal/index.php:35 >>>>>>> 2. Horde_Core_Block->getContent() >>>>>>> /usr/share/php/Horde/Core/Block/Layout/View.php:98 >>>>>>> 3. Horde_Core_Block->_call() /usr/share/php/Horde/Core/Block.php:175 >>>>>>> 4. Kronolith_Block_Summary->_content() >>>>>>> /usr/share/php/Horde/Core/Block.php:278 >>>>>>> 5. Kronolith::listCalendars() >>>>>>> /var/www/horde/kronolith/lib/Block/Summary.php:95 >>>>>>> 6. Kronolith_CalendarsManager->get() >>>>>>> /var/www/horde/kronolith/lib/Kronolith.php:1109 >>>>>>> 7. Kronolith_CalendarsManager->_getAllHolidays() >>>>>>> /var/www/horde/kronolith/lib/CalendarsManager.php:201 >>>>>>> 8. class_exists() /var/www/horde/kronolith/lib/CalendarsManager.php:546 >>>>>>> 9. spl_autoload_call() >>>>>>> 10. Horde_Autoloader_Cache->loadClass() >>>>>>> 11. Horde_Autoloader->loadClass() >>>>>>> /usr/share/php/Horde/Autoloader/Cache.php:126 >>>>>>> 12. Horde_Autoloader->_include() /usr/share/php/Horde/Autoloader.php:65 >>>>>>> 13. include() /usr/share/php/Horde/Autoloader.php:128 >>>>>>> 14. require_once() /usr/share/php/Date/Holidays.php:39 >>>>>>> 15. require_once() /usr/share/php/Date.php:55 >>>>>>> 16. Horde_ErrorHandler::errorHandler() >>>>>>> /usr/share/php/Date/TimeZone.php:4717 >>>>>>> >>>>>>> 2015-09-03T10:05:16+02:00 DEBUG: HORDE [kronolith] PHP ERROR: >>>>>>> Non-static method Date_TimeZone::setDefault() should not be >>>>>>> called statically, assuming $this from incompatible context >>>>>>> [pid 1693 on line 4718 of "/usr/share/php/Date/TimeZone.php"] >>>>>>> 2015-09-03T10:05:16+02:00 DEBUG: HORDE 1. >>>>>>> Horde_Core_Block_Layout_View->toHtml() >>>>>>> /var/www/horde/services/portal/index.php:35 >>>>>>> 2. Horde_Core_Block->getContent() >>>>>>> /usr/share/php/Horde/Core/Block/Layout/View.php:98 >>>>>>> 3. Horde_Core_Block->_call() /usr/share/php/Horde/Core/Block.php:175 >>>>>>> 4. Kronolith_Block_Summary->_content() >>>>>>> /usr/share/php/Horde/Core/Block.php:278 >>>>>>> 5. Kronolith::listCalendars() >>>>>>> /var/www/horde/kronolith/lib/Block/Summary.php:95 >>>>>>> 6. Kronolith_CalendarsManager->get() >>>>>>> /var/www/horde/kronolith/lib/Kronolith.php:1109 >>>>>>> 7. Kronolith_CalendarsManager->_getAllHolidays() >>>>>>> /var/www/horde/kronolith/lib/CalendarsManager.php:201 >>>>>>> 8. class_exists() /var/www/horde/kronolith/lib/CalendarsManager.php:546 >>>>>>> 9. spl_autoload_call() >>>>>>> 10. Horde_Autoloader_Cache->loadClass() >>>>>>> 11. Horde_Autoloader->loadClass() >>>>>>> /usr/share/php/Horde/Autoloader/Cache.php:126 >>>>>>> 12. Horde_Autoloader->_include() /usr/share/php/Horde/Autoloader.php:65 >>>>>>> 13. include() /usr/share/php/Horde/Autoloader.php:128 >>>>>>> 14. require_once() /usr/share/php/Date/Holidays.php:39 >>>>>>> 15. require_once() /usr/share/php/Date.php:55 >>>>>>> 16. Horde_ErrorHandler::errorHandler() >>>>>>> /usr/share/php/Date/TimeZone.php:4718 >>>>>>> >>>>>>> 2015-09-03T10:05:16+02:00 DEBUG: HORDE [kronolith] PHP ERROR: >>>>>>> Non-static method Date_TimeZone::isValidID() should not be >>>>>>> called statically, assuming $this from incompatible context >>>>>>> [pid 1693 on line 192 of "/usr/share/php/Date/TimeZone.php"] >>>>>>> 2015-09-03T10:05:16+02:00 DEBUG: HORDE 1. >>>>>>> Horde_Core_Block_Layout_View->toHtml() >>>>>>> /var/www/horde/services/portal/index.php:35 >>>>>>> 2. Horde_Core_Block->getContent() >>>>>>> /usr/share/php/Horde/Core/Block/Layout/View.php:98 >>>>>>> 3. Horde_Core_Block->_call() /usr/share/php/Horde/Core/Block.php:175 >>>>>>> 4. Kronolith_Block_Summary->_content() >>>>>>> /usr/share/php/Horde/Core/Block.php:278 >>>>>>> 5. Kronolith::listCalendars() >>>>>>> /var/www/horde/kronolith/lib/Block/Summary.php:95 >>>>>>> 6. Kronolith_CalendarsManager->get() >>>>>>> /var/www/horde/kronolith/lib/Kronolith.php:1109 >>>>>>> 7. Kronolith_CalendarsManager->_getAllHolidays() >>>>>>> /var/www/horde/kronolith/lib/CalendarsManager.php:201 >>>>>>> 8. class_exists() /var/www/horde/kronolith/lib/CalendarsManager.php:546 >>>>>>> 9. spl_autoload_call() >>>>>>> 10. Horde_Autoloader_Cache->loadClass() >>>>>>> 11. Horde_Autoloader->loadClass() >>>>>>> /usr/share/php/Horde/Autoloader/Cache.php:126 >>>>>>> 12. Horde_Autoloader->_include() /usr/share/php/Horde/Autoloader.php:65 >>>>>>> 13. include() /usr/share/php/Horde/Autoloader.php:128 >>>>>>> 14. require_once() /usr/share/php/Date/Holidays.php:39 >>>>>>> 15. require_once() /usr/share/php/Date.php:55 >>>>>>> 16. Date_TimeZone->setDefault() /usr/share/php/Date/TimeZone.php:4718 >>>>>>> 17. Horde_ErrorHandler::errorHandler() >>>>>>> /usr/share/php/Date/TimeZone.php:192 >>>>>>> >>>>>>> >>>>>>> It goes on with a some more lines like these. >>>>>>> >>>>>>> The browser displays only "500 - Internal Server Error". When >>>>>>> I manually enter in the browser https://mydomain.de/horde/imp >>>>>>> I can read and write mails as usual. >>>>>>> >>>>>>> Has anyone a hint for me what is going wrong in my setup? Or >>>>>>> do you need further information? I'm running the latest pear >>>>>>> packages of horde. PHP Version is: >>>>>>> >>>>>>> boromir /var/www/horde/config # php -v >>>>>>> PHP 5.6.12-0+deb8u1 (cli) (built: Aug 26 2015 12:23:30) >>>>>>> Copyright (c) 1997-2015 The PHP Group >>>>>>> Zend Engine v2.6.0, Copyright (c) 1998-2015 Zend Technologies >>>>>>> with XCache v3.2.0, Copyright (c) 2005-2014, by mOo >>>>>>> with Zend OPcache v7.0.6-dev, Copyright (c) 1999-2015, by Zend >>>>>>> Technologies >>>>>>> with Xdebug v2.2.5, Copyright (c) 2002-2014, by Derick Rethans >>>>>>> with XCache Optimizer v3.2.0, Copyright (c) 2005-2014, by mOo >>>>>>> with XCache Cacher v3.2.0, Copyright (c) 2005-2014, by mOo >>>>>>> with XCache Coverager v3.2.0, Copyright (c) 2005-2014, by mOo >>>>>>> >>>>>>> The webserver is lighttpd: >>>>>>> boromir /var/www/horde/config # lighttpd -v >>>>>>> lighttpd/1.4.35 (ssl) - a light and fast webserver >>>>>>> Build-Date: Nov 2 2014 03:43:48 >>>>>> >>>>>> Try removing the PEAR Date_Holiday package. It has a dependency >>>>>> on PEAR Date package, which is unmaintained, and is the source >>>>>> of the errors you list. >>>>> >>>>> Thanks for the quick reply. I uninstalled the packages >>>>> Date_Holidays and all related packages (Date_Holidays_German, >>>>> ...). If I got yout point the actual reason for the errors ist >>>>> the Date package which I also uninstalled. Then I receive the >>>>> following error in the log (and similar in the browser window): >>>>> >>>>> 2015-09-03T18:09:33+02:00 EMERG: HORDE [kronolith] Class >>>>> 'Date_Calc' not found [pid 1367 on line 115 of >>>>> "/var/www/horde/kronolith/lib/Day.php"] >>>>> 2015-09-03T18:09:33+02:00 DEBUG: HORDE 1. >>>>> Horde_ErrorHandler::catchFatalError() >>>>> >>>>> Maybe I was wrong with uninstalling the Date package so I >>>>> reinstalled it. Then I get the previously mentionend "500 - >>>>> Internal Server Error". The log shows: >>>>> >>>>> 2015-09-03T18:19:02+02:00 DEBUG: HORDE [kronolith] PHP ERROR: >>>>> Non-static method Date_Calc::dateDiff() should not be called >>>>> statically, assuming $this from incompatible context [pid 1372 >>>>> on line 115 of "/var/www/horde/kronolith/lib/Day.php"] >>>>> 2015-09-03T18:19:02+02:00 DEBUG: HORDE 1. >>>>> Horde_Core_Block_Layout_View->toHtml() >>>>> /var/www/horde/services/portal/index.php:35 >>>>> 2. Horde_Core_Block->getContent() >>>>> /usr/share/php/Horde/Core/Block/Layout/View.php:98 >>>>> 3. Horde_Core_Block->_call() /usr/share/php/Horde/Core/Block.php:175 >>>>> 4. Kronolith_Block_Summary->_content() >>>>> /usr/share/php/Horde/Core/Block.php:278 >>>>> 5. Kronolith_Day->diff() >>>>> /var/www/horde/kronolith/lib/Block/Summary.php:157 >>>>> 6. Horde_ErrorHandler::errorHandler() >>>>> /var/www/horde/kronolith/lib/Day.php:115 >>>>> >>>>> 2015-09-03T18:19:02+02:00 DEBUG: HORDE [kronolith] PHP ERROR: >>>>> Non-static method Date_Calc::isValidDate() should not be called >>>>> statically, assuming $this from incompatible context [pid 1372 >>>>> on line 2061 of "/usr/share/php/Date/Calc.php"] >>>>> 2015-09-03T18:19:02+02:00 DEBUG: HORDE 1. >>>>> Horde_Core_Block_Layout_View->toHtml() >>>>> /var/www/horde/services/portal/index.php:35 >>>>> 2. Horde_Core_Block->getContent() >>>>> /usr/share/php/Horde/Core/Block/Layout/View.php:98 >>>>> 3. Horde_Core_Block->_call() /usr/share/php/Horde/Core/Block.php:175 >>>>> 4. Kronolith_Block_Summary->_content() >>>>> /usr/share/php/Horde/Core/Block.php:278 >>>>> 5. Kronolith_Day->diff() >>>>> /var/www/horde/kronolith/lib/Block/Summary.php:157 >>>>> 6. Date_Calc->dateDiff() /var/www/horde/kronolith/lib/Day.php:116 >>>>> 7. Horde_ErrorHandler::errorHandler() /usr/share/php/Date/Calc.php:2061 >>>>> >>>>> 2015-09-03T18:19:02+02:00 DEBUG: HORDE [kronolith] PHP ERROR: >>>>> Non-static method Date_Calc::isValidDate() should not be called >>>>> statically, assuming $this from incompatible context [pid 1372 >>>>> on line 2064 of "/usr/share/php/Date/Calc.php"] >>>>> 2015-09-03T18:19:02+02:00 DEBUG: HORDE 1. >>>>> Horde_Core_Block_Layout_View->toHtml() >>>>> /var/www/horde/services/portal/index.php:35 >>>>> 2. Horde_Core_Block->getContent() >>>>> /usr/share/php/Horde/Core/Block/Layout/View.php:98 >>>>> 3. Horde_Core_Block->_call() /usr/share/php/Horde/Core/Block.php:175 >>>>> 4. Kronolith_Block_Summary->_content() >>>>> /usr/share/php/Horde/Core/Block.php:278 >>>>> 5. Kronolith_Day->diff() >>>>> /var/www/horde/kronolith/lib/Block/Summary.php:157 >>>>> 6. Date_Calc->dateDiff() /var/www/horde/kronolith/lib/Day.php:116 >>>>> 7. Horde_ErrorHandler::errorHandler() /usr/share/php/Date/Calc.php:2064 >>>>> >>>>> So it's a different error but the same result. Have you any more hints? >>>>> >>>>> Greetings >>>>> Jens >>>> >>>> Instead fo fixing the error I could maybe change the >>>> error_reporting level for PHP. Unfortunately I cannot see the >>>> horde config page because it raises similar errors. Can I set it to >>>> >>>> error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT >>>> >>>> manually in one of horde's config files? >>> >>> horde/config/conf.php - 'debug_level' >> >> I just found the time to take care of that annoying bug in my >> installation. I set the error_reporting to the values above in >> conf.php but nothing changed regarding my bug. >> >> So I checked the value for "error_reporting" in the >> phpinfo()-screen which I called from Horde's test.php. The "Local >> value" is 32767 (which I think is E_ALL) and the "Master value" is >> 22527 (which I think is E_ALL & ~E_DEPRECATED & ~E_STRICT). >> >> When I call phpinfo() from a php-file outside of Horde both the >> Local and the Master value are at 22527. >> >> When I call phpinfo() in the Horde PHP Shell I get a Local value of >> 30711 (which I think is E_ALL & ~E_STRICT & ~E_NOTICE). The Master >> value is again 22527. >> >> Now I'm very confused where these different values come from or >> where I probably defined them. In /etc/php5/cgi/php.ini I set >> error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT. Are there >> other places where I should have a look? >> >> >> Any help is greatly appreciated. > > > horde/config/conf.php - 'debug_level' Mike, you told me that a while ago and I did make the entry in horde/config/conf.php. The line looks like this: $conf['debug_level'] = E_ALL & ~E_NOTICE & ~E_STRICT; I wonder why the Local value in both cases (phpinfo() from test.php and from Horde PHP shell) is different. -- Greetings Jens From mrubinsk at horde.org Thu Oct 29 13:14:17 2015 From: mrubinsk at horde.org (Michael J Rubinsky) Date: Thu, 29 Oct 2015 13:14:17 +0000 Subject: [horde] PHP-related errors in Horde after upgrading to Debian Jessie In-Reply-To: <20151029130639.Horde.7G8ouZmTsl7O_XzcEn6FPb9@mail.ebira.de> References: <20150903102125.Horde.hmcwIM95EVZlUvKvB-MXkUG@mail.ebira.de> <20150903141115.Horde.GvlFfDUcFUlfZOeUtVgCRDg@h4.theupstairsroom.com> <20150903162138.Horde.WljtrmDg20gcemrNM5wVux4@mail.ebira.de> <20150908063241.Horde.EXf746s0jdo2ld4Aav9AF9Q@mail.ebira.de> <20150908074943.Horde.sruEdbu98U7xv44r94xVj3B@localhost> <20151028194833.Horde.82LlwNbciSu2ptVEkhY9EPD@mail.ebira.de> <20151029125453.Horde.WqFSU50WmlmQEFiKPmlrypT@h4.theupstairsroom.com> <20151029130639.Horde.7G8ouZmTsl7O_XzcEn6FPb9@mail.ebira.de> Message-ID: <20151029131417.Horde.MdkJRm0ywgncWaHthhw58dC@h4.theupstairsroom.com> Quoting Jens Gr?ntjes : > Zitat von Michael J Rubinsky : > >> Quoting Jens Gr?ntjes : >> >>> Zitat von Michael J Rubinsky : >>> >>>> Quoting Jens Gr?ntjes : >>>> >>>>> Zitat von Jens Gr?ntjes : >>>>> >>>>>> Zitat von Michael J Rubinsky : >>>>>> >>>>>>> Quoting Jens Gr?ntjes : >>>>>>> >>>>>>>> Hello list, >>>>>>>> >>>>>>>> after I upgraded my server to Debian Jessie I have problems >>>>>>>> with horde. I'm quite sure this isn't a Horde bug but I'm >>>>>>>> hoping that some of you experts have some hints for me. >>>>>>>> >>>>>>>> I'm having trouble when calling >>>>>>>> https://mydomain.de/horde/services/portal >>>>>>>> >>>>>>>> The log show this stack trace >>>>>>>> >>>>>>>> >>>>>>>> 2015-09-03T10:05:16+02:00 DEBUG: HORDE [kronolith] >>>>>>>> Horde_Prefs: Storing preference value (display_external_cals) >>>>>>>> [pid 1693 on line 532 of >>>>>>>> "/var/www/horde/kronolith/lib/CalendarsManager.php"] >>>>>>>> 2015-09-03T10:05:16+02:00 DEBUG: HORDE [kronolith] >>>>>>>> Horde_Prefs: Storing preference value (display_remote_cals) >>>>>>>> [pid 1693 on line 615 of >>>>>>>> "/var/www/horde/kronolith/lib/CalendarsManager.php"] >>>>>>>> 2015-09-03T10:05:16+02:00 DEBUG: HORDE [kronolith] PHP ERROR: >>>>>>>> Non-static method Date_TimeZone::isValidID() should not be >>>>>>>> called statically, assuming $this from incompatible context >>>>>>>> [pid 1693 on line 4717 of "/usr/share/php/Date/TimeZone.php"] >>>>>>>> 2015-09-03T10:05:16+02:00 DEBUG: HORDE 1. >>>>>>>> Horde_Core_Block_Layout_View->toHtml() >>>>>>>> /var/www/horde/services/portal/index.php:35 >>>>>>>> 2. Horde_Core_Block->getContent() >>>>>>>> /usr/share/php/Horde/Core/Block/Layout/View.php:98 >>>>>>>> 3. Horde_Core_Block->_call() /usr/share/php/Horde/Core/Block.php:175 >>>>>>>> 4. Kronolith_Block_Summary->_content() >>>>>>>> /usr/share/php/Horde/Core/Block.php:278 >>>>>>>> 5. Kronolith::listCalendars() >>>>>>>> /var/www/horde/kronolith/lib/Block/Summary.php:95 >>>>>>>> 6. Kronolith_CalendarsManager->get() >>>>>>>> /var/www/horde/kronolith/lib/Kronolith.php:1109 >>>>>>>> 7. Kronolith_CalendarsManager->_getAllHolidays() >>>>>>>> /var/www/horde/kronolith/lib/CalendarsManager.php:201 >>>>>>>> 8. class_exists() >>>>>>>> /var/www/horde/kronolith/lib/CalendarsManager.php:546 >>>>>>>> 9. spl_autoload_call() >>>>>>>> 10. Horde_Autoloader_Cache->loadClass() >>>>>>>> 11. Horde_Autoloader->loadClass() >>>>>>>> /usr/share/php/Horde/Autoloader/Cache.php:126 >>>>>>>> 12. Horde_Autoloader->_include() >>>>>>>> /usr/share/php/Horde/Autoloader.php:65 >>>>>>>> 13. include() /usr/share/php/Horde/Autoloader.php:128 >>>>>>>> 14. require_once() /usr/share/php/Date/Holidays.php:39 >>>>>>>> 15. require_once() /usr/share/php/Date.php:55 >>>>>>>> 16. Horde_ErrorHandler::errorHandler() >>>>>>>> /usr/share/php/Date/TimeZone.php:4717 >>>>>>>> >>>>>>>> 2015-09-03T10:05:16+02:00 DEBUG: HORDE [kronolith] PHP ERROR: >>>>>>>> Non-static method Date_TimeZone::setDefault() should not be >>>>>>>> called statically, assuming $this from incompatible context >>>>>>>> [pid 1693 on line 4718 of "/usr/share/php/Date/TimeZone.php"] >>>>>>>> 2015-09-03T10:05:16+02:00 DEBUG: HORDE 1. >>>>>>>> Horde_Core_Block_Layout_View->toHtml() >>>>>>>> /var/www/horde/services/portal/index.php:35 >>>>>>>> 2. Horde_Core_Block->getContent() >>>>>>>> /usr/share/php/Horde/Core/Block/Layout/View.php:98 >>>>>>>> 3. Horde_Core_Block->_call() /usr/share/php/Horde/Core/Block.php:175 >>>>>>>> 4. Kronolith_Block_Summary->_content() >>>>>>>> /usr/share/php/Horde/Core/Block.php:278 >>>>>>>> 5. Kronolith::listCalendars() >>>>>>>> /var/www/horde/kronolith/lib/Block/Summary.php:95 >>>>>>>> 6. Kronolith_CalendarsManager->get() >>>>>>>> /var/www/horde/kronolith/lib/Kronolith.php:1109 >>>>>>>> 7. Kronolith_CalendarsManager->_getAllHolidays() >>>>>>>> /var/www/horde/kronolith/lib/CalendarsManager.php:201 >>>>>>>> 8. class_exists() >>>>>>>> /var/www/horde/kronolith/lib/CalendarsManager.php:546 >>>>>>>> 9. spl_autoload_call() >>>>>>>> 10. Horde_Autoloader_Cache->loadClass() >>>>>>>> 11. Horde_Autoloader->loadClass() >>>>>>>> /usr/share/php/Horde/Autoloader/Cache.php:126 >>>>>>>> 12. Horde_Autoloader->_include() >>>>>>>> /usr/share/php/Horde/Autoloader.php:65 >>>>>>>> 13. include() /usr/share/php/Horde/Autoloader.php:128 >>>>>>>> 14. require_once() /usr/share/php/Date/Holidays.php:39 >>>>>>>> 15. require_once() /usr/share/php/Date.php:55 >>>>>>>> 16. Horde_ErrorHandler::errorHandler() >>>>>>>> /usr/share/php/Date/TimeZone.php:4718 >>>>>>>> >>>>>>>> 2015-09-03T10:05:16+02:00 DEBUG: HORDE [kronolith] PHP ERROR: >>>>>>>> Non-static method Date_TimeZone::isValidID() should not be >>>>>>>> called statically, assuming $this from incompatible context >>>>>>>> [pid 1693 on line 192 of "/usr/share/php/Date/TimeZone.php"] >>>>>>>> 2015-09-03T10:05:16+02:00 DEBUG: HORDE 1. >>>>>>>> Horde_Core_Block_Layout_View->toHtml() >>>>>>>> /var/www/horde/services/portal/index.php:35 >>>>>>>> 2. Horde_Core_Block->getContent() >>>>>>>> /usr/share/php/Horde/Core/Block/Layout/View.php:98 >>>>>>>> 3. Horde_Core_Block->_call() /usr/share/php/Horde/Core/Block.php:175 >>>>>>>> 4. Kronolith_Block_Summary->_content() >>>>>>>> /usr/share/php/Horde/Core/Block.php:278 >>>>>>>> 5. Kronolith::listCalendars() >>>>>>>> /var/www/horde/kronolith/lib/Block/Summary.php:95 >>>>>>>> 6. Kronolith_CalendarsManager->get() >>>>>>>> /var/www/horde/kronolith/lib/Kronolith.php:1109 >>>>>>>> 7. Kronolith_CalendarsManager->_getAllHolidays() >>>>>>>> /var/www/horde/kronolith/lib/CalendarsManager.php:201 >>>>>>>> 8. class_exists() >>>>>>>> /var/www/horde/kronolith/lib/CalendarsManager.php:546 >>>>>>>> 9. spl_autoload_call() >>>>>>>> 10. Horde_Autoloader_Cache->loadClass() >>>>>>>> 11. Horde_Autoloader->loadClass() >>>>>>>> /usr/share/php/Horde/Autoloader/Cache.php:126 >>>>>>>> 12. Horde_Autoloader->_include() >>>>>>>> /usr/share/php/Horde/Autoloader.php:65 >>>>>>>> 13. include() /usr/share/php/Horde/Autoloader.php:128 >>>>>>>> 14. require_once() /usr/share/php/Date/Holidays.php:39 >>>>>>>> 15. require_once() /usr/share/php/Date.php:55 >>>>>>>> 16. Date_TimeZone->setDefault() /usr/share/php/Date/TimeZone.php:4718 >>>>>>>> 17. Horde_ErrorHandler::errorHandler() >>>>>>>> /usr/share/php/Date/TimeZone.php:192 >>>>>>>> >>>>>>>> >>>>>>>> It goes on with a some more lines like these. >>>>>>>> >>>>>>>> The browser displays only "500 - Internal Server Error". When >>>>>>>> I manually enter in the browser https://mydomain.de/horde/imp >>>>>>>> I can read and write mails as usual. >>>>>>>> >>>>>>>> Has anyone a hint for me what is going wrong in my setup? Or >>>>>>>> do you need further information? I'm running the latest pear >>>>>>>> packages of horde. PHP Version is: >>>>>>>> >>>>>>>> boromir /var/www/horde/config # php -v >>>>>>>> PHP 5.6.12-0+deb8u1 (cli) (built: Aug 26 2015 12:23:30) >>>>>>>> Copyright (c) 1997-2015 The PHP Group >>>>>>>> Zend Engine v2.6.0, Copyright (c) 1998-2015 Zend Technologies >>>>>>>> with XCache v3.2.0, Copyright (c) 2005-2014, by mOo >>>>>>>> with Zend OPcache v7.0.6-dev, Copyright (c) 1999-2015, by >>>>>>>> Zend Technologies >>>>>>>> with Xdebug v2.2.5, Copyright (c) 2002-2014, by Derick Rethans >>>>>>>> with XCache Optimizer v3.2.0, Copyright (c) 2005-2014, by mOo >>>>>>>> with XCache Cacher v3.2.0, Copyright (c) 2005-2014, by mOo >>>>>>>> with XCache Coverager v3.2.0, Copyright (c) 2005-2014, by mOo >>>>>>>> >>>>>>>> The webserver is lighttpd: >>>>>>>> boromir /var/www/horde/config # lighttpd -v >>>>>>>> lighttpd/1.4.35 (ssl) - a light and fast webserver >>>>>>>> Build-Date: Nov 2 2014 03:43:48 >>>>>>> >>>>>>> Try removing the PEAR Date_Holiday package. It has a >>>>>>> dependency on PEAR Date package, which is unmaintained, and is >>>>>>> the source of the errors you list. >>>>>> >>>>>> Thanks for the quick reply. I uninstalled the packages >>>>>> Date_Holidays and all related packages (Date_Holidays_German, >>>>>> ...). If I got yout point the actual reason for the errors ist >>>>>> the Date package which I also uninstalled. Then I receive the >>>>>> following error in the log (and similar in the browser window): >>>>>> >>>>>> 2015-09-03T18:09:33+02:00 EMERG: HORDE [kronolith] Class >>>>>> 'Date_Calc' not found [pid 1367 on line 115 of >>>>>> "/var/www/horde/kronolith/lib/Day.php"] >>>>>> 2015-09-03T18:09:33+02:00 DEBUG: HORDE 1. >>>>>> Horde_ErrorHandler::catchFatalError() >>>>>> >>>>>> Maybe I was wrong with uninstalling the Date package so I >>>>>> reinstalled it. Then I get the previously mentionend "500 - >>>>>> Internal Server Error". The log shows: >>>>>> >>>>>> 2015-09-03T18:19:02+02:00 DEBUG: HORDE [kronolith] PHP ERROR: >>>>>> Non-static method Date_Calc::dateDiff() should not be called >>>>>> statically, assuming $this from incompatible context [pid 1372 >>>>>> on line 115 of "/var/www/horde/kronolith/lib/Day.php"] >>>>>> 2015-09-03T18:19:02+02:00 DEBUG: HORDE 1. >>>>>> Horde_Core_Block_Layout_View->toHtml() >>>>>> /var/www/horde/services/portal/index.php:35 >>>>>> 2. Horde_Core_Block->getContent() >>>>>> /usr/share/php/Horde/Core/Block/Layout/View.php:98 >>>>>> 3. Horde_Core_Block->_call() /usr/share/php/Horde/Core/Block.php:175 >>>>>> 4. Kronolith_Block_Summary->_content() >>>>>> /usr/share/php/Horde/Core/Block.php:278 >>>>>> 5. Kronolith_Day->diff() >>>>>> /var/www/horde/kronolith/lib/Block/Summary.php:157 >>>>>> 6. Horde_ErrorHandler::errorHandler() >>>>>> /var/www/horde/kronolith/lib/Day.php:115 >>>>>> >>>>>> 2015-09-03T18:19:02+02:00 DEBUG: HORDE [kronolith] PHP ERROR: >>>>>> Non-static method Date_Calc::isValidDate() should not be called >>>>>> statically, assuming $this from incompatible context [pid 1372 >>>>>> on line 2061 of "/usr/share/php/Date/Calc.php"] >>>>>> 2015-09-03T18:19:02+02:00 DEBUG: HORDE 1. >>>>>> Horde_Core_Block_Layout_View->toHtml() >>>>>> /var/www/horde/services/portal/index.php:35 >>>>>> 2. Horde_Core_Block->getContent() >>>>>> /usr/share/php/Horde/Core/Block/Layout/View.php:98 >>>>>> 3. Horde_Core_Block->_call() /usr/share/php/Horde/Core/Block.php:175 >>>>>> 4. Kronolith_Block_Summary->_content() >>>>>> /usr/share/php/Horde/Core/Block.php:278 >>>>>> 5. Kronolith_Day->diff() >>>>>> /var/www/horde/kronolith/lib/Block/Summary.php:157 >>>>>> 6. Date_Calc->dateDiff() /var/www/horde/kronolith/lib/Day.php:116 >>>>>> 7. Horde_ErrorHandler::errorHandler() /usr/share/php/Date/Calc.php:2061 >>>>>> >>>>>> 2015-09-03T18:19:02+02:00 DEBUG: HORDE [kronolith] PHP ERROR: >>>>>> Non-static method Date_Calc::isValidDate() should not be called >>>>>> statically, assuming $this from incompatible context [pid 1372 >>>>>> on line 2064 of "/usr/share/php/Date/Calc.php"] >>>>>> 2015-09-03T18:19:02+02:00 DEBUG: HORDE 1. >>>>>> Horde_Core_Block_Layout_View->toHtml() >>>>>> /var/www/horde/services/portal/index.php:35 >>>>>> 2. Horde_Core_Block->getContent() >>>>>> /usr/share/php/Horde/Core/Block/Layout/View.php:98 >>>>>> 3. Horde_Core_Block->_call() /usr/share/php/Horde/Core/Block.php:175 >>>>>> 4. Kronolith_Block_Summary->_content() >>>>>> /usr/share/php/Horde/Core/Block.php:278 >>>>>> 5. Kronolith_Day->diff() >>>>>> /var/www/horde/kronolith/lib/Block/Summary.php:157 >>>>>> 6. Date_Calc->dateDiff() /var/www/horde/kronolith/lib/Day.php:116 >>>>>> 7. Horde_ErrorHandler::errorHandler() /usr/share/php/Date/Calc.php:2064 >>>>>> >>>>>> So it's a different error but the same result. Have you any more hints? >>>>>> >>>>>> Greetings >>>>>> Jens >>>>> >>>>> Instead fo fixing the error I could maybe change the >>>>> error_reporting level for PHP. Unfortunately I cannot see the >>>>> horde config page because it raises similar errors. Can I set it >>>>> to >>>>> >>>>> error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT >>>>> >>>>> manually in one of horde's config files? >>>> >>>> horde/config/conf.php - 'debug_level' >>> >>> I just found the time to take care of that annoying bug in my >>> installation. I set the error_reporting to the values above in >>> conf.php but nothing changed regarding my bug. >>> >>> So I checked the value for "error_reporting" in the >>> phpinfo()-screen which I called from Horde's test.php. The "Local >>> value" is 32767 (which I think is E_ALL) and the "Master value" is >>> 22527 (which I think is E_ALL & ~E_DEPRECATED & ~E_STRICT). >>> >>> When I call phpinfo() from a php-file outside of Horde both the >>> Local and the Master value are at 22527. Then this is what the php.ini file in use is set to. >>> When I call phpinfo() in the Horde PHP Shell I get a Local value >>> of 30711 (which I think is E_ALL & ~E_STRICT & ~E_NOTICE). The >>> Master value is again 22527. Yes, the value in conf.php is used to set this when Horde is initialized. Hence, this is the "local" value. This matches what you say you set 'debug_level' to. >>> Now I'm very confused where these different values come from or >>> where I probably defined them. In /etc/php5/cgi/php.ini I set >>> error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT. Are there >>> other places where I should have a look? What ever you want the value to be inside Horde, you need to set in conf.php. >>> Any help is greatly appreciated. >> >> >> horde/config/conf.php - 'debug_level' > > Mike, you told me that a while ago and I did make the entry in > horde/config/conf.php. The line looks like this: > > $conf['debug_level'] = E_ALL & ~E_NOTICE & ~E_STRICT; > > I wonder why the Local value in both cases (phpinfo() from test.php > and from Horde PHP shell) is different. > > -- > Greetings > Jens > > -- > Horde mailing list > Frequently Asked Questions: http://horde.org/faq/ > To unsubscribe, mail: horde-unsubscribe at lists.horde.org -- mike The Horde Project http://www.horde.org https://www.facebook.com/hordeproject https://www.twitter.com/hordeproject -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5751 bytes Desc: S/MIME Signature URL: From jens.gruentjes at ebira.de Thu Oct 29 13:23:57 2015 From: jens.gruentjes at ebira.de (Jens =?utf-8?b?R3LDvG50amVz?=) Date: Thu, 29 Oct 2015 13:23:57 +0000 Subject: [horde] PHP-related errors in Horde after upgrading to Debian Jessie In-Reply-To: <20151029131417.Horde.MdkJRm0ywgncWaHthhw58dC@h4.theupstairsroom.com> References: <20150903102125.Horde.hmcwIM95EVZlUvKvB-MXkUG@mail.ebira.de> <20150903141115.Horde.GvlFfDUcFUlfZOeUtVgCRDg@h4.theupstairsroom.com> <20150903162138.Horde.WljtrmDg20gcemrNM5wVux4@mail.ebira.de> <20150908063241.Horde.EXf746s0jdo2ld4Aav9AF9Q@mail.ebira.de> <20150908074943.Horde.sruEdbu98U7xv44r94xVj3B@localhost> <20151028194833.Horde.82LlwNbciSu2ptVEkhY9EPD@mail.ebira.de> <20151029125453.Horde.WqFSU50WmlmQEFiKPmlrypT@h4.theupstairsroom.com> <20151029130639.Horde.7G8ouZmTsl7O_XzcEn6FPb9@mail.ebira.de> <20151029131417.Horde.MdkJRm0ywgncWaHthhw58dC@h4.theupstairsroom.com> Message-ID: <20151029132357.Horde.Cwp-y8AuBNT5Zv_Z9QCJku-@mail.ebira.de> Zitat von Michael J Rubinsky : > Quoting Jens Gr?ntjes : > >> Zitat von Michael J Rubinsky : >> >>> Quoting Jens Gr?ntjes : >>> >>>> Zitat von Michael J Rubinsky : >>>> >>>>> Quoting Jens Gr?ntjes : >>>>> >>>>>> Zitat von Jens Gr?ntjes : >>>>>> >>>>>>> Zitat von Michael J Rubinsky : >>>>>>> >>>>>>>> Quoting Jens Gr?ntjes : >>>>>>>> >>>>>>>>> Hello list, >>>>>>>>> >>>>>>>>> after I upgraded my server to Debian Jessie I have problems >>>>>>>>> with horde. I'm quite sure this isn't a Horde bug but I'm >>>>>>>>> hoping that some of you experts have some hints for me. >>>>>>>>> >>>>>>>>> I'm having trouble when calling >>>>>>>>> https://mydomain.de/horde/services/portal >>>>>>>>> >>>>>>>>> The log show this stack trace >>>>>>>>> >>>>>>>>> >>>>>>>>> 2015-09-03T10:05:16+02:00 DEBUG: HORDE [kronolith] >>>>>>>>> Horde_Prefs: Storing preference value >>>>>>>>> (display_external_cals) [pid 1693 on line 532 of >>>>>>>>> "/var/www/horde/kronolith/lib/CalendarsManager.php"] >>>>>>>>> 2015-09-03T10:05:16+02:00 DEBUG: HORDE [kronolith] >>>>>>>>> Horde_Prefs: Storing preference value (display_remote_cals) >>>>>>>>> [pid 1693 on line 615 of >>>>>>>>> "/var/www/horde/kronolith/lib/CalendarsManager.php"] >>>>>>>>> 2015-09-03T10:05:16+02:00 DEBUG: HORDE [kronolith] PHP >>>>>>>>> ERROR: Non-static method Date_TimeZone::isValidID() should >>>>>>>>> not be called statically, assuming $this from incompatible >>>>>>>>> context [pid 1693 on line 4717 of >>>>>>>>> "/usr/share/php/Date/TimeZone.php"] >>>>>>>>> 2015-09-03T10:05:16+02:00 DEBUG: HORDE 1. >>>>>>>>> Horde_Core_Block_Layout_View->toHtml() >>>>>>>>> /var/www/horde/services/portal/index.php:35 >>>>>>>>> 2. Horde_Core_Block->getContent() >>>>>>>>> /usr/share/php/Horde/Core/Block/Layout/View.php:98 >>>>>>>>> 3. Horde_Core_Block->_call() /usr/share/php/Horde/Core/Block.php:175 >>>>>>>>> 4. Kronolith_Block_Summary->_content() >>>>>>>>> /usr/share/php/Horde/Core/Block.php:278 >>>>>>>>> 5. Kronolith::listCalendars() >>>>>>>>> /var/www/horde/kronolith/lib/Block/Summary.php:95 >>>>>>>>> 6. Kronolith_CalendarsManager->get() >>>>>>>>> /var/www/horde/kronolith/lib/Kronolith.php:1109 >>>>>>>>> 7. Kronolith_CalendarsManager->_getAllHolidays() >>>>>>>>> /var/www/horde/kronolith/lib/CalendarsManager.php:201 >>>>>>>>> 8. class_exists() >>>>>>>>> /var/www/horde/kronolith/lib/CalendarsManager.php:546 >>>>>>>>> 9. spl_autoload_call() >>>>>>>>> 10. Horde_Autoloader_Cache->loadClass() >>>>>>>>> 11. Horde_Autoloader->loadClass() >>>>>>>>> /usr/share/php/Horde/Autoloader/Cache.php:126 >>>>>>>>> 12. Horde_Autoloader->_include() >>>>>>>>> /usr/share/php/Horde/Autoloader.php:65 >>>>>>>>> 13. include() /usr/share/php/Horde/Autoloader.php:128 >>>>>>>>> 14. require_once() /usr/share/php/Date/Holidays.php:39 >>>>>>>>> 15. require_once() /usr/share/php/Date.php:55 >>>>>>>>> 16. Horde_ErrorHandler::errorHandler() >>>>>>>>> /usr/share/php/Date/TimeZone.php:4717 >>>>>>>>> >>>>>>>>> 2015-09-03T10:05:16+02:00 DEBUG: HORDE [kronolith] PHP >>>>>>>>> ERROR: Non-static method Date_TimeZone::setDefault() should >>>>>>>>> not be called statically, assuming $this from incompatible >>>>>>>>> context [pid 1693 on line 4718 of >>>>>>>>> "/usr/share/php/Date/TimeZone.php"] >>>>>>>>> 2015-09-03T10:05:16+02:00 DEBUG: HORDE 1. >>>>>>>>> Horde_Core_Block_Layout_View->toHtml() >>>>>>>>> /var/www/horde/services/portal/index.php:35 >>>>>>>>> 2. Horde_Core_Block->getContent() >>>>>>>>> /usr/share/php/Horde/Core/Block/Layout/View.php:98 >>>>>>>>> 3. Horde_Core_Block->_call() /usr/share/php/Horde/Core/Block.php:175 >>>>>>>>> 4. Kronolith_Block_Summary->_content() >>>>>>>>> /usr/share/php/Horde/Core/Block.php:278 >>>>>>>>> 5. Kronolith::listCalendars() >>>>>>>>> /var/www/horde/kronolith/lib/Block/Summary.php:95 >>>>>>>>> 6. Kronolith_CalendarsManager->get() >>>>>>>>> /var/www/horde/kronolith/lib/Kronolith.php:1109 >>>>>>>>> 7. Kronolith_CalendarsManager->_getAllHolidays() >>>>>>>>> /var/www/horde/kronolith/lib/CalendarsManager.php:201 >>>>>>>>> 8. class_exists() >>>>>>>>> /var/www/horde/kronolith/lib/CalendarsManager.php:546 >>>>>>>>> 9. spl_autoload_call() >>>>>>>>> 10. Horde_Autoloader_Cache->loadClass() >>>>>>>>> 11. Horde_Autoloader->loadClass() >>>>>>>>> /usr/share/php/Horde/Autoloader/Cache.php:126 >>>>>>>>> 12. Horde_Autoloader->_include() >>>>>>>>> /usr/share/php/Horde/Autoloader.php:65 >>>>>>>>> 13. include() /usr/share/php/Horde/Autoloader.php:128 >>>>>>>>> 14. require_once() /usr/share/php/Date/Holidays.php:39 >>>>>>>>> 15. require_once() /usr/share/php/Date.php:55 >>>>>>>>> 16. Horde_ErrorHandler::errorHandler() >>>>>>>>> /usr/share/php/Date/TimeZone.php:4718 >>>>>>>>> >>>>>>>>> 2015-09-03T10:05:16+02:00 DEBUG: HORDE [kronolith] PHP >>>>>>>>> ERROR: Non-static method Date_TimeZone::isValidID() should >>>>>>>>> not be called statically, assuming $this from incompatible >>>>>>>>> context [pid 1693 on line 192 of >>>>>>>>> "/usr/share/php/Date/TimeZone.php"] >>>>>>>>> 2015-09-03T10:05:16+02:00 DEBUG: HORDE 1. >>>>>>>>> Horde_Core_Block_Layout_View->toHtml() >>>>>>>>> /var/www/horde/services/portal/index.php:35 >>>>>>>>> 2. Horde_Core_Block->getContent() >>>>>>>>> /usr/share/php/Horde/Core/Block/Layout/View.php:98 >>>>>>>>> 3. Horde_Core_Block->_call() /usr/share/php/Horde/Core/Block.php:175 >>>>>>>>> 4. Kronolith_Block_Summary->_content() >>>>>>>>> /usr/share/php/Horde/Core/Block.php:278 >>>>>>>>> 5. Kronolith::listCalendars() >>>>>>>>> /var/www/horde/kronolith/lib/Block/Summary.php:95 >>>>>>>>> 6. Kronolith_CalendarsManager->get() >>>>>>>>> /var/www/horde/kronolith/lib/Kronolith.php:1109 >>>>>>>>> 7. Kronolith_CalendarsManager->_getAllHolidays() >>>>>>>>> /var/www/horde/kronolith/lib/CalendarsManager.php:201 >>>>>>>>> 8. class_exists() >>>>>>>>> /var/www/horde/kronolith/lib/CalendarsManager.php:546 >>>>>>>>> 9. spl_autoload_call() >>>>>>>>> 10. Horde_Autoloader_Cache->loadClass() >>>>>>>>> 11. Horde_Autoloader->loadClass() >>>>>>>>> /usr/share/php/Horde/Autoloader/Cache.php:126 >>>>>>>>> 12. Horde_Autoloader->_include() >>>>>>>>> /usr/share/php/Horde/Autoloader.php:65 >>>>>>>>> 13. include() /usr/share/php/Horde/Autoloader.php:128 >>>>>>>>> 14. require_once() /usr/share/php/Date/Holidays.php:39 >>>>>>>>> 15. require_once() /usr/share/php/Date.php:55 >>>>>>>>> 16. Date_TimeZone->setDefault() /usr/share/php/Date/TimeZone.php:4718 >>>>>>>>> 17. Horde_ErrorHandler::errorHandler() >>>>>>>>> /usr/share/php/Date/TimeZone.php:192 >>>>>>>>> >>>>>>>>> >>>>>>>>> It goes on with a some more lines like these. >>>>>>>>> >>>>>>>>> The browser displays only "500 - Internal Server Error". >>>>>>>>> When I manually enter in the browser >>>>>>>>> https://mydomain.de/horde/imp I can read and write mails as >>>>>>>>> usual. >>>>>>>>> >>>>>>>>> Has anyone a hint for me what is going wrong in my setup? Or >>>>>>>>> do you need further information? I'm running the latest pear >>>>>>>>> packages of horde. PHP Version is: >>>>>>>>> >>>>>>>>> boromir /var/www/horde/config # php -v >>>>>>>>> PHP 5.6.12-0+deb8u1 (cli) (built: Aug 26 2015 12:23:30) >>>>>>>>> Copyright (c) 1997-2015 The PHP Group >>>>>>>>> Zend Engine v2.6.0, Copyright (c) 1998-2015 Zend Technologies >>>>>>>>> with XCache v3.2.0, Copyright (c) 2005-2014, by mOo >>>>>>>>> with Zend OPcache v7.0.6-dev, Copyright (c) 1999-2015, by >>>>>>>>> Zend Technologies >>>>>>>>> with Xdebug v2.2.5, Copyright (c) 2002-2014, by Derick Rethans >>>>>>>>> with XCache Optimizer v3.2.0, Copyright (c) 2005-2014, by mOo >>>>>>>>> with XCache Cacher v3.2.0, Copyright (c) 2005-2014, by mOo >>>>>>>>> with XCache Coverager v3.2.0, Copyright (c) 2005-2014, by mOo >>>>>>>>> >>>>>>>>> The webserver is lighttpd: >>>>>>>>> boromir /var/www/horde/config # lighttpd -v >>>>>>>>> lighttpd/1.4.35 (ssl) - a light and fast webserver >>>>>>>>> Build-Date: Nov 2 2014 03:43:48 >>>>>>>> >>>>>>>> Try removing the PEAR Date_Holiday package. It has a >>>>>>>> dependency on PEAR Date package, which is unmaintained, and >>>>>>>> is the source of the errors you list. >>>>>>> >>>>>>> Thanks for the quick reply. I uninstalled the packages >>>>>>> Date_Holidays and all related packages (Date_Holidays_German, >>>>>>> ...). If I got yout point the actual reason for the errors ist >>>>>>> the Date package which I also uninstalled. Then I receive the >>>>>>> following error in the log (and similar in the browser window): >>>>>>> >>>>>>> 2015-09-03T18:09:33+02:00 EMERG: HORDE [kronolith] Class >>>>>>> 'Date_Calc' not found [pid 1367 on line 115 of >>>>>>> "/var/www/horde/kronolith/lib/Day.php"] >>>>>>> 2015-09-03T18:09:33+02:00 DEBUG: HORDE 1. >>>>>>> Horde_ErrorHandler::catchFatalError() >>>>>>> >>>>>>> Maybe I was wrong with uninstalling the Date package so I >>>>>>> reinstalled it. Then I get the previously mentionend "500 - >>>>>>> Internal Server Error". The log shows: >>>>>>> >>>>>>> 2015-09-03T18:19:02+02:00 DEBUG: HORDE [kronolith] PHP ERROR: >>>>>>> Non-static method Date_Calc::dateDiff() should not be called >>>>>>> statically, assuming $this from incompatible context [pid 1372 >>>>>>> on line 115 of "/var/www/horde/kronolith/lib/Day.php"] >>>>>>> 2015-09-03T18:19:02+02:00 DEBUG: HORDE 1. >>>>>>> Horde_Core_Block_Layout_View->toHtml() >>>>>>> /var/www/horde/services/portal/index.php:35 >>>>>>> 2. Horde_Core_Block->getContent() >>>>>>> /usr/share/php/Horde/Core/Block/Layout/View.php:98 >>>>>>> 3. Horde_Core_Block->_call() /usr/share/php/Horde/Core/Block.php:175 >>>>>>> 4. Kronolith_Block_Summary->_content() >>>>>>> /usr/share/php/Horde/Core/Block.php:278 >>>>>>> 5. Kronolith_Day->diff() >>>>>>> /var/www/horde/kronolith/lib/Block/Summary.php:157 >>>>>>> 6. Horde_ErrorHandler::errorHandler() >>>>>>> /var/www/horde/kronolith/lib/Day.php:115 >>>>>>> >>>>>>> 2015-09-03T18:19:02+02:00 DEBUG: HORDE [kronolith] PHP ERROR: >>>>>>> Non-static method Date_Calc::isValidDate() should not be >>>>>>> called statically, assuming $this from incompatible context >>>>>>> [pid 1372 on line 2061 of "/usr/share/php/Date/Calc.php"] >>>>>>> 2015-09-03T18:19:02+02:00 DEBUG: HORDE 1. >>>>>>> Horde_Core_Block_Layout_View->toHtml() >>>>>>> /var/www/horde/services/portal/index.php:35 >>>>>>> 2. Horde_Core_Block->getContent() >>>>>>> /usr/share/php/Horde/Core/Block/Layout/View.php:98 >>>>>>> 3. Horde_Core_Block->_call() /usr/share/php/Horde/Core/Block.php:175 >>>>>>> 4. Kronolith_Block_Summary->_content() >>>>>>> /usr/share/php/Horde/Core/Block.php:278 >>>>>>> 5. Kronolith_Day->diff() >>>>>>> /var/www/horde/kronolith/lib/Block/Summary.php:157 >>>>>>> 6. Date_Calc->dateDiff() /var/www/horde/kronolith/lib/Day.php:116 >>>>>>> 7. Horde_ErrorHandler::errorHandler() /usr/share/php/Date/Calc.php:2061 >>>>>>> >>>>>>> 2015-09-03T18:19:02+02:00 DEBUG: HORDE [kronolith] PHP ERROR: >>>>>>> Non-static method Date_Calc::isValidDate() should not be >>>>>>> called statically, assuming $this from incompatible context >>>>>>> [pid 1372 on line 2064 of "/usr/share/php/Date/Calc.php"] >>>>>>> 2015-09-03T18:19:02+02:00 DEBUG: HORDE 1. >>>>>>> Horde_Core_Block_Layout_View->toHtml() >>>>>>> /var/www/horde/services/portal/index.php:35 >>>>>>> 2. Horde_Core_Block->getContent() >>>>>>> /usr/share/php/Horde/Core/Block/Layout/View.php:98 >>>>>>> 3. Horde_Core_Block->_call() /usr/share/php/Horde/Core/Block.php:175 >>>>>>> 4. Kronolith_Block_Summary->_content() >>>>>>> /usr/share/php/Horde/Core/Block.php:278 >>>>>>> 5. Kronolith_Day->diff() >>>>>>> /var/www/horde/kronolith/lib/Block/Summary.php:157 >>>>>>> 6. Date_Calc->dateDiff() /var/www/horde/kronolith/lib/Day.php:116 >>>>>>> 7. Horde_ErrorHandler::errorHandler() /usr/share/php/Date/Calc.php:2064 >>>>>>> >>>>>>> So it's a different error but the same result. Have you any more hints? >>>>>>> >>>>>>> Greetings >>>>>>> Jens >>>>>> >>>>>> Instead fo fixing the error I could maybe change the >>>>>> error_reporting level for PHP. Unfortunately I cannot see the >>>>>> horde config page because it raises similar errors. Can I set >>>>>> it to >>>>>> >>>>>> error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT >>>>>> >>>>>> manually in one of horde's config files? >>>>> >>>>> horde/config/conf.php - 'debug_level' >>>> >>>> I just found the time to take care of that annoying bug in my >>>> installation. I set the error_reporting to the values above in >>>> conf.php but nothing changed regarding my bug. >>>> >>>> So I checked the value for "error_reporting" in the >>>> phpinfo()-screen which I called from Horde's test.php. The "Local >>>> value" is 32767 (which I think is E_ALL) and the "Master value" >>>> is 22527 (which I think is E_ALL & ~E_DEPRECATED & ~E_STRICT). >>>> >>>> When I call phpinfo() from a php-file outside of Horde both the >>>> Local and the Master value are at 22527. > > Then this is what the php.ini file in use is set to. > That is what I expected. >>>> When I call phpinfo() in the Horde PHP Shell I get a Local value >>>> of 30711 (which I think is E_ALL & ~E_STRICT & ~E_NOTICE). The >>>> Master value is again 22527. > > Yes, the value in conf.php is used to set this when Horde is > initialized. Hence, this is the "local" value. This matches what you > say you set 'debug_level' to. Okay, that matches my config. > >>>> Now I'm very confused where these different values come from or >>>> where I probably defined them. In /etc/php5/cgi/php.ini I set >>>> error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT. Are there >>>> other places where I should have a look? > > What ever you want the value to be inside Horde, you need to set in conf.php. > Okay, I understand. But I don't understand why the Local value according to phpinfo() from the test.php is 32767. With my settings I wonder if the errors like the one below can make Horde crash? 2015-10-28T20:49:19+01:00 DEBUG: HORDE [kronolith] PHP ERROR: Non-static method Date_Calc::dateToDays() should not be c alled statically, assuming $this from incompatible context [pid 12311 on line 4045 of "/usr/share/php/Date/Calc.php"] 2015-10-28T20:49:19+01:00 DEBUG: HORDE 1. Horde_Core_Ajax_Application->send() /var/www/horde/services/ajax.php:70 I'm getting frequent php-cgi-segfaults whenever this happens. >>>> Any help is greatly appreciated. >>> >>> >>> horde/config/conf.php - 'debug_level' >> >> Mike, you told me that a while ago and I did make the entry in >> horde/config/conf.php. The line looks like this: >> >> $conf['debug_level'] = E_ALL & ~E_NOTICE & ~E_STRICT; >> >> I wonder why the Local value in both cases (phpinfo() from test.php >> and from Horde PHP shell) is different. >> >> -- >> Greetings >> Jens >> >> -- >> Horde mailing list >> Frequently Asked Questions: http://horde.org/faq/ >> To unsubscribe, mail: horde-unsubscribe at lists.horde.org From mrubinsk at horde.org Thu Oct 29 13:29:24 2015 From: mrubinsk at horde.org (Michael J Rubinsky) Date: Thu, 29 Oct 2015 13:29:24 +0000 Subject: [horde] PHP-related errors in Horde after upgrading to Debian Jessie In-Reply-To: <20151029132357.Horde.Cwp-y8AuBNT5Zv_Z9QCJku-@mail.ebira.de> References: <20150903102125.Horde.hmcwIM95EVZlUvKvB-MXkUG@mail.ebira.de> <20150903141115.Horde.GvlFfDUcFUlfZOeUtVgCRDg@h4.theupstairsroom.com> <20150903162138.Horde.WljtrmDg20gcemrNM5wVux4@mail.ebira.de> <20150908063241.Horde.EXf746s0jdo2ld4Aav9AF9Q@mail.ebira.de> <20150908074943.Horde.sruEdbu98U7xv44r94xVj3B@localhost> <20151028194833.Horde.82LlwNbciSu2ptVEkhY9EPD@mail.ebira.de> <20151029125453.Horde.WqFSU50WmlmQEFiKPmlrypT@h4.theupstairsroom.com> <20151029130639.Horde.7G8ouZmTsl7O_XzcEn6FPb9@mail.ebira.de> <20151029131417.Horde.MdkJRm0ywgncWaHthhw58dC@h4.theupstairsroom.com> <20151029132357.Horde.Cwp-y8AuBNT5Zv_Z9QCJku-@mail.ebira.de> Message-ID: <20151029132924.Horde.l4yOaN6JzT1xsRKELDmzZ7A@h4.theupstairsroom.com> Quoting Jens Gr?ntjes : > Zitat von Michael J Rubinsky : > >> Quoting Jens Gr?ntjes : >> >>> Zitat von Michael J Rubinsky : >>> >>>> Quoting Jens Gr?ntjes : >>>> >>>>> Zitat von Michael J Rubinsky : >>>>> >>>>>> Quoting Jens Gr?ntjes : >>>>>> >>>>>>> Zitat von Jens Gr?ntjes : >>>>>>> >>>>>>>> Zitat von Michael J Rubinsky : >>>>>>>> >>>>>>>>> Quoting Jens Gr?ntjes : >>>>>>>>> >>>>>>>>>> Hello list, >>>>>>>>>> >>>>>>>>>> after I upgraded my server to Debian Jessie I have problems >>>>>>>>>> with horde. I'm quite sure this isn't a Horde bug but I'm >>>>>>>>>> hoping that some of you experts have some hints for me. >>>>>>>>>> >>>>>>>>>> I'm having trouble when calling >>>>>>>>>> https://mydomain.de/horde/services/portal >>>>>>>>>> >>>>>>>>>> The log show this stack trace >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> 2015-09-03T10:05:16+02:00 DEBUG: HORDE [kronolith] >>>>>>>>>> Horde_Prefs: Storing preference value >>>>>>>>>> (display_external_cals) [pid 1693 on line 532 of >>>>>>>>>> "/var/www/horde/kronolith/lib/CalendarsManager.php"] >>>>>>>>>> 2015-09-03T10:05:16+02:00 DEBUG: HORDE [kronolith] >>>>>>>>>> Horde_Prefs: Storing preference value (display_remote_cals) >>>>>>>>>> [pid 1693 on line 615 of >>>>>>>>>> "/var/www/horde/kronolith/lib/CalendarsManager.php"] >>>>>>>>>> 2015-09-03T10:05:16+02:00 DEBUG: HORDE [kronolith] PHP >>>>>>>>>> ERROR: Non-static method Date_TimeZone::isValidID() should >>>>>>>>>> not be called statically, assuming $this from incompatible >>>>>>>>>> context [pid 1693 on line 4717 of >>>>>>>>>> "/usr/share/php/Date/TimeZone.php"] >>>>>>>>>> 2015-09-03T10:05:16+02:00 DEBUG: HORDE 1. >>>>>>>>>> Horde_Core_Block_Layout_View->toHtml() >>>>>>>>>> /var/www/horde/services/portal/index.php:35 >>>>>>>>>> 2. Horde_Core_Block->getContent() >>>>>>>>>> /usr/share/php/Horde/Core/Block/Layout/View.php:98 >>>>>>>>>> 3. Horde_Core_Block->_call() /usr/share/php/Horde/Core/Block.php:175 >>>>>>>>>> 4. Kronolith_Block_Summary->_content() >>>>>>>>>> /usr/share/php/Horde/Core/Block.php:278 >>>>>>>>>> 5. Kronolith::listCalendars() >>>>>>>>>> /var/www/horde/kronolith/lib/Block/Summary.php:95 >>>>>>>>>> 6. Kronolith_CalendarsManager->get() >>>>>>>>>> /var/www/horde/kronolith/lib/Kronolith.php:1109 >>>>>>>>>> 7. Kronolith_CalendarsManager->_getAllHolidays() >>>>>>>>>> /var/www/horde/kronolith/lib/CalendarsManager.php:201 >>>>>>>>>> 8. class_exists() >>>>>>>>>> /var/www/horde/kronolith/lib/CalendarsManager.php:546 >>>>>>>>>> 9. spl_autoload_call() >>>>>>>>>> 10. Horde_Autoloader_Cache->loadClass() >>>>>>>>>> 11. Horde_Autoloader->loadClass() >>>>>>>>>> /usr/share/php/Horde/Autoloader/Cache.php:126 >>>>>>>>>> 12. Horde_Autoloader->_include() >>>>>>>>>> /usr/share/php/Horde/Autoloader.php:65 >>>>>>>>>> 13. include() /usr/share/php/Horde/Autoloader.php:128 >>>>>>>>>> 14. require_once() /usr/share/php/Date/Holidays.php:39 >>>>>>>>>> 15. require_once() /usr/share/php/Date.php:55 >>>>>>>>>> 16. Horde_ErrorHandler::errorHandler() >>>>>>>>>> /usr/share/php/Date/TimeZone.php:4717 >>>>>>>>>> >>>>>>>>>> 2015-09-03T10:05:16+02:00 DEBUG: HORDE [kronolith] PHP >>>>>>>>>> ERROR: Non-static method Date_TimeZone::setDefault() should >>>>>>>>>> not be called statically, assuming $this from incompatible >>>>>>>>>> context [pid 1693 on line 4718 of >>>>>>>>>> "/usr/share/php/Date/TimeZone.php"] >>>>>>>>>> 2015-09-03T10:05:16+02:00 DEBUG: HORDE 1. >>>>>>>>>> Horde_Core_Block_Layout_View->toHtml() >>>>>>>>>> /var/www/horde/services/portal/index.php:35 >>>>>>>>>> 2. Horde_Core_Block->getContent() >>>>>>>>>> /usr/share/php/Horde/Core/Block/Layout/View.php:98 >>>>>>>>>> 3. Horde_Core_Block->_call() /usr/share/php/Horde/Core/Block.php:175 >>>>>>>>>> 4. Kronolith_Block_Summary->_content() >>>>>>>>>> /usr/share/php/Horde/Core/Block.php:278 >>>>>>>>>> 5. Kronolith::listCalendars() >>>>>>>>>> /var/www/horde/kronolith/lib/Block/Summary.php:95 >>>>>>>>>> 6. Kronolith_CalendarsManager->get() >>>>>>>>>> /var/www/horde/kronolith/lib/Kronolith.php:1109 >>>>>>>>>> 7. Kronolith_CalendarsManager->_getAllHolidays() >>>>>>>>>> /var/www/horde/kronolith/lib/CalendarsManager.php:201 >>>>>>>>>> 8. class_exists() >>>>>>>>>> /var/www/horde/kronolith/lib/CalendarsManager.php:546 >>>>>>>>>> 9. spl_autoload_call() >>>>>>>>>> 10. Horde_Autoloader_Cache->loadClass() >>>>>>>>>> 11. Horde_Autoloader->loadClass() >>>>>>>>>> /usr/share/php/Horde/Autoloader/Cache.php:126 >>>>>>>>>> 12. Horde_Autoloader->_include() >>>>>>>>>> /usr/share/php/Horde/Autoloader.php:65 >>>>>>>>>> 13. include() /usr/share/php/Horde/Autoloader.php:128 >>>>>>>>>> 14. require_once() /usr/share/php/Date/Holidays.php:39 >>>>>>>>>> 15. require_once() /usr/share/php/Date.php:55 >>>>>>>>>> 16. Horde_ErrorHandler::errorHandler() >>>>>>>>>> /usr/share/php/Date/TimeZone.php:4718 >>>>>>>>>> >>>>>>>>>> 2015-09-03T10:05:16+02:00 DEBUG: HORDE [kronolith] PHP >>>>>>>>>> ERROR: Non-static method Date_TimeZone::isValidID() should >>>>>>>>>> not be called statically, assuming $this from incompatible >>>>>>>>>> context [pid 1693 on line 192 of >>>>>>>>>> "/usr/share/php/Date/TimeZone.php"] >>>>>>>>>> 2015-09-03T10:05:16+02:00 DEBUG: HORDE 1. >>>>>>>>>> Horde_Core_Block_Layout_View->toHtml() >>>>>>>>>> /var/www/horde/services/portal/index.php:35 >>>>>>>>>> 2. Horde_Core_Block->getContent() >>>>>>>>>> /usr/share/php/Horde/Core/Block/Layout/View.php:98 >>>>>>>>>> 3. Horde_Core_Block->_call() /usr/share/php/Horde/Core/Block.php:175 >>>>>>>>>> 4. Kronolith_Block_Summary->_content() >>>>>>>>>> /usr/share/php/Horde/Core/Block.php:278 >>>>>>>>>> 5. Kronolith::listCalendars() >>>>>>>>>> /var/www/horde/kronolith/lib/Block/Summary.php:95 >>>>>>>>>> 6. Kronolith_CalendarsManager->get() >>>>>>>>>> /var/www/horde/kronolith/lib/Kronolith.php:1109 >>>>>>>>>> 7. Kronolith_CalendarsManager->_getAllHolidays() >>>>>>>>>> /var/www/horde/kronolith/lib/CalendarsManager.php:201 >>>>>>>>>> 8. class_exists() >>>>>>>>>> /var/www/horde/kronolith/lib/CalendarsManager.php:546 >>>>>>>>>> 9. spl_autoload_call() >>>>>>>>>> 10. Horde_Autoloader_Cache->loadClass() >>>>>>>>>> 11. Horde_Autoloader->loadClass() >>>>>>>>>> /usr/share/php/Horde/Autoloader/Cache.php:126 >>>>>>>>>> 12. Horde_Autoloader->_include() >>>>>>>>>> /usr/share/php/Horde/Autoloader.php:65 >>>>>>>>>> 13. include() /usr/share/php/Horde/Autoloader.php:128 >>>>>>>>>> 14. require_once() /usr/share/php/Date/Holidays.php:39 >>>>>>>>>> 15. require_once() /usr/share/php/Date.php:55 >>>>>>>>>> 16. Date_TimeZone->setDefault() >>>>>>>>>> /usr/share/php/Date/TimeZone.php:4718 >>>>>>>>>> 17. Horde_ErrorHandler::errorHandler() >>>>>>>>>> /usr/share/php/Date/TimeZone.php:192 >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> It goes on with a some more lines like these. >>>>>>>>>> >>>>>>>>>> The browser displays only "500 - Internal Server Error". >>>>>>>>>> When I manually enter in the browser >>>>>>>>>> https://mydomain.de/horde/imp I can read and write mails as >>>>>>>>>> usual. >>>>>>>>>> >>>>>>>>>> Has anyone a hint for me what is going wrong in my setup? >>>>>>>>>> Or do you need further information? I'm running the latest >>>>>>>>>> pear packages of horde. PHP Version is: >>>>>>>>>> >>>>>>>>>> boromir /var/www/horde/config # php -v >>>>>>>>>> PHP 5.6.12-0+deb8u1 (cli) (built: Aug 26 2015 12:23:30) >>>>>>>>>> Copyright (c) 1997-2015 The PHP Group >>>>>>>>>> Zend Engine v2.6.0, Copyright (c) 1998-2015 Zend Technologies >>>>>>>>>> with XCache v3.2.0, Copyright (c) 2005-2014, by mOo >>>>>>>>>> with Zend OPcache v7.0.6-dev, Copyright (c) 1999-2015, by >>>>>>>>>> Zend Technologies >>>>>>>>>> with Xdebug v2.2.5, Copyright (c) 2002-2014, by Derick Rethans >>>>>>>>>> with XCache Optimizer v3.2.0, Copyright (c) 2005-2014, by mOo >>>>>>>>>> with XCache Cacher v3.2.0, Copyright (c) 2005-2014, by mOo >>>>>>>>>> with XCache Coverager v3.2.0, Copyright (c) 2005-2014, by mOo >>>>>>>>>> >>>>>>>>>> The webserver is lighttpd: >>>>>>>>>> boromir /var/www/horde/config # lighttpd -v >>>>>>>>>> lighttpd/1.4.35 (ssl) - a light and fast webserver >>>>>>>>>> Build-Date: Nov 2 2014 03:43:48 >>>>>>>>> >>>>>>>>> Try removing the PEAR Date_Holiday package. It has a >>>>>>>>> dependency on PEAR Date package, which is unmaintained, and >>>>>>>>> is the source of the errors you list. >>>>>>>> >>>>>>>> Thanks for the quick reply. I uninstalled the packages >>>>>>>> Date_Holidays and all related packages (Date_Holidays_German, >>>>>>>> ...). If I got yout point the actual reason for the errors >>>>>>>> ist the Date package which I also uninstalled. Then I receive >>>>>>>> the following error in the log (and similar in the browser >>>>>>>> window): >>>>>>>> >>>>>>>> 2015-09-03T18:09:33+02:00 EMERG: HORDE [kronolith] Class >>>>>>>> 'Date_Calc' not found [pid 1367 on line 115 of >>>>>>>> "/var/www/horde/kronolith/lib/Day.php"] >>>>>>>> 2015-09-03T18:09:33+02:00 DEBUG: HORDE 1. >>>>>>>> Horde_ErrorHandler::catchFatalError() >>>>>>>> >>>>>>>> Maybe I was wrong with uninstalling the Date package so I >>>>>>>> reinstalled it. Then I get the previously mentionend "500 - >>>>>>>> Internal Server Error". The log shows: >>>>>>>> >>>>>>>> 2015-09-03T18:19:02+02:00 DEBUG: HORDE [kronolith] PHP ERROR: >>>>>>>> Non-static method Date_Calc::dateDiff() should not be called >>>>>>>> statically, assuming $this from incompatible context [pid >>>>>>>> 1372 on line 115 of "/var/www/horde/kronolith/lib/Day.php"] >>>>>>>> 2015-09-03T18:19:02+02:00 DEBUG: HORDE 1. >>>>>>>> Horde_Core_Block_Layout_View->toHtml() >>>>>>>> /var/www/horde/services/portal/index.php:35 >>>>>>>> 2. Horde_Core_Block->getContent() >>>>>>>> /usr/share/php/Horde/Core/Block/Layout/View.php:98 >>>>>>>> 3. Horde_Core_Block->_call() /usr/share/php/Horde/Core/Block.php:175 >>>>>>>> 4. Kronolith_Block_Summary->_content() >>>>>>>> /usr/share/php/Horde/Core/Block.php:278 >>>>>>>> 5. Kronolith_Day->diff() >>>>>>>> /var/www/horde/kronolith/lib/Block/Summary.php:157 >>>>>>>> 6. Horde_ErrorHandler::errorHandler() >>>>>>>> /var/www/horde/kronolith/lib/Day.php:115 >>>>>>>> >>>>>>>> 2015-09-03T18:19:02+02:00 DEBUG: HORDE [kronolith] PHP ERROR: >>>>>>>> Non-static method Date_Calc::isValidDate() should not be >>>>>>>> called statically, assuming $this from incompatible context >>>>>>>> [pid 1372 on line 2061 of "/usr/share/php/Date/Calc.php"] >>>>>>>> 2015-09-03T18:19:02+02:00 DEBUG: HORDE 1. >>>>>>>> Horde_Core_Block_Layout_View->toHtml() >>>>>>>> /var/www/horde/services/portal/index.php:35 >>>>>>>> 2. Horde_Core_Block->getContent() >>>>>>>> /usr/share/php/Horde/Core/Block/Layout/View.php:98 >>>>>>>> 3. Horde_Core_Block->_call() /usr/share/php/Horde/Core/Block.php:175 >>>>>>>> 4. Kronolith_Block_Summary->_content() >>>>>>>> /usr/share/php/Horde/Core/Block.php:278 >>>>>>>> 5. Kronolith_Day->diff() >>>>>>>> /var/www/horde/kronolith/lib/Block/Summary.php:157 >>>>>>>> 6. Date_Calc->dateDiff() /var/www/horde/kronolith/lib/Day.php:116 >>>>>>>> 7. Horde_ErrorHandler::errorHandler() >>>>>>>> /usr/share/php/Date/Calc.php:2061 >>>>>>>> >>>>>>>> 2015-09-03T18:19:02+02:00 DEBUG: HORDE [kronolith] PHP ERROR: >>>>>>>> Non-static method Date_Calc::isValidDate() should not be >>>>>>>> called statically, assuming $this from incompatible context >>>>>>>> [pid 1372 on line 2064 of "/usr/share/php/Date/Calc.php"] >>>>>>>> 2015-09-03T18:19:02+02:00 DEBUG: HORDE 1. >>>>>>>> Horde_Core_Block_Layout_View->toHtml() >>>>>>>> /var/www/horde/services/portal/index.php:35 >>>>>>>> 2. Horde_Core_Block->getContent() >>>>>>>> /usr/share/php/Horde/Core/Block/Layout/View.php:98 >>>>>>>> 3. Horde_Core_Block->_call() /usr/share/php/Horde/Core/Block.php:175 >>>>>>>> 4. Kronolith_Block_Summary->_content() >>>>>>>> /usr/share/php/Horde/Core/Block.php:278 >>>>>>>> 5. Kronolith_Day->diff() >>>>>>>> /var/www/horde/kronolith/lib/Block/Summary.php:157 >>>>>>>> 6. Date_Calc->dateDiff() /var/www/horde/kronolith/lib/Day.php:116 >>>>>>>> 7. Horde_ErrorHandler::errorHandler() >>>>>>>> /usr/share/php/Date/Calc.php:2064 >>>>>>>> >>>>>>>> So it's a different error but the same result. Have you any >>>>>>>> more hints? >>>>>>>> >>>>>>>> Greetings >>>>>>>> Jens >>>>>>> >>>>>>> Instead fo fixing the error I could maybe change the >>>>>>> error_reporting level for PHP. Unfortunately I cannot see the >>>>>>> horde config page because it raises similar errors. Can I set >>>>>>> it to >>>>>>> >>>>>>> error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT >>>>>>> >>>>>>> manually in one of horde's config files? >>>>>> >>>>>> horde/config/conf.php - 'debug_level' >>>>> >>>>> I just found the time to take care of that annoying bug in my >>>>> installation. I set the error_reporting to the values above in >>>>> conf.php but nothing changed regarding my bug. >>>>> >>>>> So I checked the value for "error_reporting" in the >>>>> phpinfo()-screen which I called from Horde's test.php. The >>>>> "Local value" is 32767 (which I think is E_ALL) and the "Master >>>>> value" is 22527 (which I think is E_ALL & ~E_DEPRECATED & >>>>> ~E_STRICT). >>>>> >>>>> When I call phpinfo() from a php-file outside of Horde both the >>>>> Local and the Master value are at 22527. >> >> Then this is what the php.ini file in use is set to. >> > That is what I expected. >>>>> When I call phpinfo() in the Horde PHP Shell I get a Local value >>>>> of 30711 (which I think is E_ALL & ~E_STRICT & ~E_NOTICE). The >>>>> Master value is again 22527. >> >> Yes, the value in conf.php is used to set this when Horde is >> initialized. Hence, this is the "local" value. This matches what >> you say you set 'debug_level' to. > Okay, that matches my config. >> >>>>> Now I'm very confused where these different values come from or >>>>> where I probably defined them. In /etc/php5/cgi/php.ini I set >>>>> error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT. Are there >>>>> other places where I should have a look? >> >> What ever you want the value to be inside Horde, you need to set in >> conf.php. >> > Okay, I understand. But I don't understand why the Local value > according to phpinfo() from the test.php is 32767. Probably because test.php doesn't initialize the full Horde environment, just enough to test the dependencies whereas the phpshell is running in the scope of a fully initialized Horde environment. > With my settings I wonder if the errors like the one below can make > Horde crash? Why don't you put the ~E_DEPRECATED in conf.php as well? > > 2015-10-28T20:49:19+01:00 DEBUG: HORDE [kronolith] PHP ERROR: > Non-static method Date_Calc::dateToDays() should not be c > alled statically, assuming $this from incompatible context [pid > 12311 on line 4045 of "/usr/share/php/Date/Calc.php"] > 2015-10-28T20:49:19+01:00 DEBUG: HORDE 1. > Horde_Core_Ajax_Application->send() > /var/www/horde/services/ajax.php:70 > > I'm getting frequent php-cgi-segfaults whenever this happens. > >>>>> Any help is greatly appreciated. >>>> >>>> >>>> horde/config/conf.php - 'debug_level' >>> >>> Mike, you told me that a while ago and I did make the entry in >>> horde/config/conf.php. The line looks like this: >>> >>> $conf['debug_level'] = E_ALL & ~E_NOTICE & ~E_STRICT; >>> >>> I wonder why the Local value in both cases (phpinfo() from >>> test.php and from Horde PHP shell) is different. >>> >>> -- >>> Greetings >>> Jens >>> >>> -- >>> Horde mailing list >>> Frequently Asked Questions: http://horde.org/faq/ >>> To unsubscribe, mail: horde-unsubscribe at lists.horde.org > > > > -- > Horde mailing list > Frequently Asked Questions: http://horde.org/faq/ > To unsubscribe, mail: horde-unsubscribe at lists.horde.org -- mike The Horde Project http://www.horde.org https://www.facebook.com/hordeproject https://www.twitter.com/hordeproject -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5751 bytes Desc: S/MIME Signature URL: From jens.gruentjes at ebira.de Thu Oct 29 14:12:13 2015 From: jens.gruentjes at ebira.de (Jens =?utf-8?b?R3LDvG50amVz?=) Date: Thu, 29 Oct 2015 14:12:13 +0000 Subject: [horde] PHP-related errors in Horde after upgrading to Debian Jessie In-Reply-To: <20151029132924.Horde.l4yOaN6JzT1xsRKELDmzZ7A@h4.theupstairsroom.com> References: <20150903102125.Horde.hmcwIM95EVZlUvKvB-MXkUG@mail.ebira.de> <20150903141115.Horde.GvlFfDUcFUlfZOeUtVgCRDg@h4.theupstairsroom.com> <20150903162138.Horde.WljtrmDg20gcemrNM5wVux4@mail.ebira.de> <20150908063241.Horde.EXf746s0jdo2ld4Aav9AF9Q@mail.ebira.de> <20150908074943.Horde.sruEdbu98U7xv44r94xVj3B@localhost> <20151028194833.Horde.82LlwNbciSu2ptVEkhY9EPD@mail.ebira.de> <20151029125453.Horde.WqFSU50WmlmQEFiKPmlrypT@h4.theupstairsroom.com> <20151029130639.Horde.7G8ouZmTsl7O_XzcEn6FPb9@mail.ebira.de> <20151029131417.Horde.MdkJRm0ywgncWaHthhw58dC@h4.theupstairsroom.com> <20151029132357.Horde.Cwp-y8AuBNT5Zv_Z9QCJku-@mail.ebira.de> <20151029132924.Horde.l4yOaN6JzT1xsRKELDmzZ7A@h4.theupstairsroom.com> Message-ID: <20151029141213.Horde.g3TlpMh7NSKuMcE_3kkVK_K@mail.ebira.de> Zitat von Michael J Rubinsky : > Quoting Jens Gr?ntjes : > >> Zitat von Michael J Rubinsky : >> >>> Quoting Jens Gr?ntjes : >>> >>>> Zitat von Michael J Rubinsky : >>>> >>>>> Quoting Jens Gr?ntjes : >>>>> >>>>>> Zitat von Michael J Rubinsky : >>>>>> >>>>>>> Quoting Jens Gr?ntjes : >>>>>>> >>>>>>>> Zitat von Jens Gr?ntjes : >>>>>>>> >>>>>>>>> Zitat von Michael J Rubinsky : >>>>>>>>> >>>>>>>>>> Quoting Jens Gr?ntjes : >>>>>>>>>> >>>>>>>>>>> Hello list, >>>>>>>>>>> >>>>>>>>>>> after I upgraded my server to Debian Jessie I have >>>>>>>>>>> problems with horde. I'm quite sure this isn't a Horde bug >>>>>>>>>>> but I'm hoping that some of you experts have some hints >>>>>>>>>>> for me. >>>>>>>>>>> >>>>>>>>>>> I'm having trouble when calling >>>>>>>>>>> https://mydomain.de/horde/services/portal >>>>>>>>>>> >>>>>>>>>>> The log show this stack trace >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> 2015-09-03T10:05:16+02:00 DEBUG: HORDE [kronolith] >>>>>>>>>>> Horde_Prefs: Storing preference value >>>>>>>>>>> (display_external_cals) [pid 1693 on line 532 of >>>>>>>>>>> "/var/www/horde/kronolith/lib/CalendarsManager.php"] >>>>>>>>>>> 2015-09-03T10:05:16+02:00 DEBUG: HORDE [kronolith] >>>>>>>>>>> Horde_Prefs: Storing preference value >>>>>>>>>>> (display_remote_cals) [pid 1693 on line 615 of >>>>>>>>>>> "/var/www/horde/kronolith/lib/CalendarsManager.php"] >>>>>>>>>>> 2015-09-03T10:05:16+02:00 DEBUG: HORDE [kronolith] PHP >>>>>>>>>>> ERROR: Non-static method Date_TimeZone::isValidID() should >>>>>>>>>>> not be called statically, assuming $this from incompatible >>>>>>>>>>> context [pid 1693 on line 4717 of >>>>>>>>>>> "/usr/share/php/Date/TimeZone.php"] >>>>>>>>>>> 2015-09-03T10:05:16+02:00 DEBUG: HORDE 1. >>>>>>>>>>> Horde_Core_Block_Layout_View->toHtml() >>>>>>>>>>> /var/www/horde/services/portal/index.php:35 >>>>>>>>>>> 2. Horde_Core_Block->getContent() >>>>>>>>>>> /usr/share/php/Horde/Core/Block/Layout/View.php:98 >>>>>>>>>>> 3. Horde_Core_Block->_call() >>>>>>>>>>> /usr/share/php/Horde/Core/Block.php:175 >>>>>>>>>>> 4. Kronolith_Block_Summary->_content() >>>>>>>>>>> /usr/share/php/Horde/Core/Block.php:278 >>>>>>>>>>> 5. Kronolith::listCalendars() >>>>>>>>>>> /var/www/horde/kronolith/lib/Block/Summary.php:95 >>>>>>>>>>> 6. Kronolith_CalendarsManager->get() >>>>>>>>>>> /var/www/horde/kronolith/lib/Kronolith.php:1109 >>>>>>>>>>> 7. Kronolith_CalendarsManager->_getAllHolidays() >>>>>>>>>>> /var/www/horde/kronolith/lib/CalendarsManager.php:201 >>>>>>>>>>> 8. class_exists() >>>>>>>>>>> /var/www/horde/kronolith/lib/CalendarsManager.php:546 >>>>>>>>>>> 9. spl_autoload_call() >>>>>>>>>>> 10. Horde_Autoloader_Cache->loadClass() >>>>>>>>>>> 11. Horde_Autoloader->loadClass() >>>>>>>>>>> /usr/share/php/Horde/Autoloader/Cache.php:126 >>>>>>>>>>> 12. Horde_Autoloader->_include() >>>>>>>>>>> /usr/share/php/Horde/Autoloader.php:65 >>>>>>>>>>> 13. include() /usr/share/php/Horde/Autoloader.php:128 >>>>>>>>>>> 14. require_once() /usr/share/php/Date/Holidays.php:39 >>>>>>>>>>> 15. require_once() /usr/share/php/Date.php:55 >>>>>>>>>>> 16. Horde_ErrorHandler::errorHandler() >>>>>>>>>>> /usr/share/php/Date/TimeZone.php:4717 >>>>>>>>>>> >>>>>>>>>>> 2015-09-03T10:05:16+02:00 DEBUG: HORDE [kronolith] PHP >>>>>>>>>>> ERROR: Non-static method Date_TimeZone::setDefault() >>>>>>>>>>> should not be called statically, assuming $this from >>>>>>>>>>> incompatible context [pid 1693 on line 4718 of >>>>>>>>>>> "/usr/share/php/Date/TimeZone.php"] >>>>>>>>>>> 2015-09-03T10:05:16+02:00 DEBUG: HORDE 1. >>>>>>>>>>> Horde_Core_Block_Layout_View->toHtml() >>>>>>>>>>> /var/www/horde/services/portal/index.php:35 >>>>>>>>>>> 2. Horde_Core_Block->getContent() >>>>>>>>>>> /usr/share/php/Horde/Core/Block/Layout/View.php:98 >>>>>>>>>>> 3. Horde_Core_Block->_call() >>>>>>>>>>> /usr/share/php/Horde/Core/Block.php:175 >>>>>>>>>>> 4. Kronolith_Block_Summary->_content() >>>>>>>>>>> /usr/share/php/Horde/Core/Block.php:278 >>>>>>>>>>> 5. Kronolith::listCalendars() >>>>>>>>>>> /var/www/horde/kronolith/lib/Block/Summary.php:95 >>>>>>>>>>> 6. Kronolith_CalendarsManager->get() >>>>>>>>>>> /var/www/horde/kronolith/lib/Kronolith.php:1109 >>>>>>>>>>> 7. Kronolith_CalendarsManager->_getAllHolidays() >>>>>>>>>>> /var/www/horde/kronolith/lib/CalendarsManager.php:201 >>>>>>>>>>> 8. class_exists() >>>>>>>>>>> /var/www/horde/kronolith/lib/CalendarsManager.php:546 >>>>>>>>>>> 9. spl_autoload_call() >>>>>>>>>>> 10. Horde_Autoloader_Cache->loadClass() >>>>>>>>>>> 11. Horde_Autoloader->loadClass() >>>>>>>>>>> /usr/share/php/Horde/Autoloader/Cache.php:126 >>>>>>>>>>> 12. Horde_Autoloader->_include() >>>>>>>>>>> /usr/share/php/Horde/Autoloader.php:65 >>>>>>>>>>> 13. include() /usr/share/php/Horde/Autoloader.php:128 >>>>>>>>>>> 14. require_once() /usr/share/php/Date/Holidays.php:39 >>>>>>>>>>> 15. require_once() /usr/share/php/Date.php:55 >>>>>>>>>>> 16. Horde_ErrorHandler::errorHandler() >>>>>>>>>>> /usr/share/php/Date/TimeZone.php:4718 >>>>>>>>>>> >>>>>>>>>>> 2015-09-03T10:05:16+02:00 DEBUG: HORDE [kronolith] PHP >>>>>>>>>>> ERROR: Non-static method Date_TimeZone::isValidID() should >>>>>>>>>>> not be called statically, assuming $this from incompatible >>>>>>>>>>> context [pid 1693 on line 192 of >>>>>>>>>>> "/usr/share/php/Date/TimeZone.php"] >>>>>>>>>>> 2015-09-03T10:05:16+02:00 DEBUG: HORDE 1. >>>>>>>>>>> Horde_Core_Block_Layout_View->toHtml() >>>>>>>>>>> /var/www/horde/services/portal/index.php:35 >>>>>>>>>>> 2. Horde_Core_Block->getContent() >>>>>>>>>>> /usr/share/php/Horde/Core/Block/Layout/View.php:98 >>>>>>>>>>> 3. Horde_Core_Block->_call() >>>>>>>>>>> /usr/share/php/Horde/Core/Block.php:175 >>>>>>>>>>> 4. Kronolith_Block_Summary->_content() >>>>>>>>>>> /usr/share/php/Horde/Core/Block.php:278 >>>>>>>>>>> 5. Kronolith::listCalendars() >>>>>>>>>>> /var/www/horde/kronolith/lib/Block/Summary.php:95 >>>>>>>>>>> 6. Kronolith_CalendarsManager->get() >>>>>>>>>>> /var/www/horde/kronolith/lib/Kronolith.php:1109 >>>>>>>>>>> 7. Kronolith_CalendarsManager->_getAllHolidays() >>>>>>>>>>> /var/www/horde/kronolith/lib/CalendarsManager.php:201 >>>>>>>>>>> 8. class_exists() >>>>>>>>>>> /var/www/horde/kronolith/lib/CalendarsManager.php:546 >>>>>>>>>>> 9. spl_autoload_call() >>>>>>>>>>> 10. Horde_Autoloader_Cache->loadClass() >>>>>>>>>>> 11. Horde_Autoloader->loadClass() >>>>>>>>>>> /usr/share/php/Horde/Autoloader/Cache.php:126 >>>>>>>>>>> 12. Horde_Autoloader->_include() >>>>>>>>>>> /usr/share/php/Horde/Autoloader.php:65 >>>>>>>>>>> 13. include() /usr/share/php/Horde/Autoloader.php:128 >>>>>>>>>>> 14. require_once() /usr/share/php/Date/Holidays.php:39 >>>>>>>>>>> 15. require_once() /usr/share/php/Date.php:55 >>>>>>>>>>> 16. Date_TimeZone->setDefault() >>>>>>>>>>> /usr/share/php/Date/TimeZone.php:4718 >>>>>>>>>>> 17. Horde_ErrorHandler::errorHandler() >>>>>>>>>>> /usr/share/php/Date/TimeZone.php:192 >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> It goes on with a some more lines like these. >>>>>>>>>>> >>>>>>>>>>> The browser displays only "500 - Internal Server Error". >>>>>>>>>>> When I manually enter in the browser >>>>>>>>>>> https://mydomain.de/horde/imp I can read and write mails >>>>>>>>>>> as usual. >>>>>>>>>>> >>>>>>>>>>> Has anyone a hint for me what is going wrong in my setup? >>>>>>>>>>> Or do you need further information? I'm running the latest >>>>>>>>>>> pear packages of horde. PHP Version is: >>>>>>>>>>> >>>>>>>>>>> boromir /var/www/horde/config # php -v >>>>>>>>>>> PHP 5.6.12-0+deb8u1 (cli) (built: Aug 26 2015 12:23:30) >>>>>>>>>>> Copyright (c) 1997-2015 The PHP Group >>>>>>>>>>> Zend Engine v2.6.0, Copyright (c) 1998-2015 Zend Technologies >>>>>>>>>>> with XCache v3.2.0, Copyright (c) 2005-2014, by mOo >>>>>>>>>>> with Zend OPcache v7.0.6-dev, Copyright (c) 1999-2015, by >>>>>>>>>>> Zend Technologies >>>>>>>>>>> with Xdebug v2.2.5, Copyright (c) 2002-2014, by Derick Rethans >>>>>>>>>>> with XCache Optimizer v3.2.0, Copyright (c) 2005-2014, by mOo >>>>>>>>>>> with XCache Cacher v3.2.0, Copyright (c) 2005-2014, by mOo >>>>>>>>>>> with XCache Coverager v3.2.0, Copyright (c) 2005-2014, by mOo >>>>>>>>>>> >>>>>>>>>>> The webserver is lighttpd: >>>>>>>>>>> boromir /var/www/horde/config # lighttpd -v >>>>>>>>>>> lighttpd/1.4.35 (ssl) - a light and fast webserver >>>>>>>>>>> Build-Date: Nov 2 2014 03:43:48 >>>>>>>>>> >>>>>>>>>> Try removing the PEAR Date_Holiday package. It has a >>>>>>>>>> dependency on PEAR Date package, which is unmaintained, and >>>>>>>>>> is the source of the errors you list. >>>>>>>>> >>>>>>>>> Thanks for the quick reply. I uninstalled the packages >>>>>>>>> Date_Holidays and all related packages >>>>>>>>> (Date_Holidays_German, ...). If I got yout point the actual >>>>>>>>> reason for the errors ist the Date package which I also >>>>>>>>> uninstalled. Then I receive the following error in the log >>>>>>>>> (and similar in the browser window): >>>>>>>>> >>>>>>>>> 2015-09-03T18:09:33+02:00 EMERG: HORDE [kronolith] Class >>>>>>>>> 'Date_Calc' not found [pid 1367 on line 115 of >>>>>>>>> "/var/www/horde/kronolith/lib/Day.php"] >>>>>>>>> 2015-09-03T18:09:33+02:00 DEBUG: HORDE 1. >>>>>>>>> Horde_ErrorHandler::catchFatalError() >>>>>>>>> >>>>>>>>> Maybe I was wrong with uninstalling the Date package so I >>>>>>>>> reinstalled it. Then I get the previously mentionend "500 - >>>>>>>>> Internal Server Error". The log shows: >>>>>>>>> >>>>>>>>> 2015-09-03T18:19:02+02:00 DEBUG: HORDE [kronolith] PHP >>>>>>>>> ERROR: Non-static method Date_Calc::dateDiff() should not be >>>>>>>>> called statically, assuming $this from incompatible context >>>>>>>>> [pid 1372 on line 115 of >>>>>>>>> "/var/www/horde/kronolith/lib/Day.php"] >>>>>>>>> 2015-09-03T18:19:02+02:00 DEBUG: HORDE 1. >>>>>>>>> Horde_Core_Block_Layout_View->toHtml() >>>>>>>>> /var/www/horde/services/portal/index.php:35 >>>>>>>>> 2. Horde_Core_Block->getContent() >>>>>>>>> /usr/share/php/Horde/Core/Block/Layout/View.php:98 >>>>>>>>> 3. Horde_Core_Block->_call() /usr/share/php/Horde/Core/Block.php:175 >>>>>>>>> 4. Kronolith_Block_Summary->_content() >>>>>>>>> /usr/share/php/Horde/Core/Block.php:278 >>>>>>>>> 5. Kronolith_Day->diff() >>>>>>>>> /var/www/horde/kronolith/lib/Block/Summary.php:157 >>>>>>>>> 6. Horde_ErrorHandler::errorHandler() >>>>>>>>> /var/www/horde/kronolith/lib/Day.php:115 >>>>>>>>> >>>>>>>>> 2015-09-03T18:19:02+02:00 DEBUG: HORDE [kronolith] PHP >>>>>>>>> ERROR: Non-static method Date_Calc::isValidDate() should not >>>>>>>>> be called statically, assuming $this from incompatible >>>>>>>>> context [pid 1372 on line 2061 of >>>>>>>>> "/usr/share/php/Date/Calc.php"] >>>>>>>>> 2015-09-03T18:19:02+02:00 DEBUG: HORDE 1. >>>>>>>>> Horde_Core_Block_Layout_View->toHtml() >>>>>>>>> /var/www/horde/services/portal/index.php:35 >>>>>>>>> 2. Horde_Core_Block->getContent() >>>>>>>>> /usr/share/php/Horde/Core/Block/Layout/View.php:98 >>>>>>>>> 3. Horde_Core_Block->_call() /usr/share/php/Horde/Core/Block.php:175 >>>>>>>>> 4. Kronolith_Block_Summary->_content() >>>>>>>>> /usr/share/php/Horde/Core/Block.php:278 >>>>>>>>> 5. Kronolith_Day->diff() >>>>>>>>> /var/www/horde/kronolith/lib/Block/Summary.php:157 >>>>>>>>> 6. Date_Calc->dateDiff() /var/www/horde/kronolith/lib/Day.php:116 >>>>>>>>> 7. Horde_ErrorHandler::errorHandler() >>>>>>>>> /usr/share/php/Date/Calc.php:2061 >>>>>>>>> >>>>>>>>> 2015-09-03T18:19:02+02:00 DEBUG: HORDE [kronolith] PHP >>>>>>>>> ERROR: Non-static method Date_Calc::isValidDate() should not >>>>>>>>> be called statically, assuming $this from incompatible >>>>>>>>> context [pid 1372 on line 2064 of >>>>>>>>> "/usr/share/php/Date/Calc.php"] >>>>>>>>> 2015-09-03T18:19:02+02:00 DEBUG: HORDE 1. >>>>>>>>> Horde_Core_Block_Layout_View->toHtml() >>>>>>>>> /var/www/horde/services/portal/index.php:35 >>>>>>>>> 2. Horde_Core_Block->getContent() >>>>>>>>> /usr/share/php/Horde/Core/Block/Layout/View.php:98 >>>>>>>>> 3. Horde_Core_Block->_call() /usr/share/php/Horde/Core/Block.php:175 >>>>>>>>> 4. Kronolith_Block_Summary->_content() >>>>>>>>> /usr/share/php/Horde/Core/Block.php:278 >>>>>>>>> 5. Kronolith_Day->diff() >>>>>>>>> /var/www/horde/kronolith/lib/Block/Summary.php:157 >>>>>>>>> 6. Date_Calc->dateDiff() /var/www/horde/kronolith/lib/Day.php:116 >>>>>>>>> 7. Horde_ErrorHandler::errorHandler() >>>>>>>>> /usr/share/php/Date/Calc.php:2064 >>>>>>>>> >>>>>>>>> So it's a different error but the same result. Have you any >>>>>>>>> more hints? >>>>>>>>> >>>>>>>>> Greetings >>>>>>>>> Jens >>>>>>>> >>>>>>>> Instead fo fixing the error I could maybe change the >>>>>>>> error_reporting level for PHP. Unfortunately I cannot see the >>>>>>>> horde config page because it raises similar errors. Can I set >>>>>>>> it to >>>>>>>> >>>>>>>> error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT >>>>>>>> >>>>>>>> manually in one of horde's config files? >>>>>>> >>>>>>> horde/config/conf.php - 'debug_level' >>>>>> >>>>>> I just found the time to take care of that annoying bug in my >>>>>> installation. I set the error_reporting to the values above in >>>>>> conf.php but nothing changed regarding my bug. >>>>>> >>>>>> So I checked the value for "error_reporting" in the >>>>>> phpinfo()-screen which I called from Horde's test.php. The >>>>>> "Local value" is 32767 (which I think is E_ALL) and the "Master >>>>>> value" is 22527 (which I think is E_ALL & ~E_DEPRECATED & >>>>>> ~E_STRICT). >>>>>> >>>>>> When I call phpinfo() from a php-file outside of Horde both the >>>>>> Local and the Master value are at 22527. >>> >>> Then this is what the php.ini file in use is set to. >>> >> That is what I expected. >>>>>> When I call phpinfo() in the Horde PHP Shell I get a Local >>>>>> value of 30711 (which I think is E_ALL & ~E_STRICT & >>>>>> ~E_NOTICE). The Master value is again 22527. >>> >>> Yes, the value in conf.php is used to set this when Horde is >>> initialized. Hence, this is the "local" value. This matches what >>> you say you set 'debug_level' to. >> Okay, that matches my config. >>> >>>>>> Now I'm very confused where these different values come from or >>>>>> where I probably defined them. In /etc/php5/cgi/php.ini I set >>>>>> error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT. Are there >>>>>> other places where I should have a look? >>> >>> What ever you want the value to be inside Horde, you need to set >>> in conf.php. >>> >> Okay, I understand. But I don't understand why the Local value >> according to phpinfo() from the test.php is 32767. > > Probably because test.php doesn't initialize the full Horde > environment, just enough to test the dependencies whereas the > phpshell is running in the scope of a fully initialized Horde > environment. > > >> With my settings I wonder if the errors like the one below can make >> Horde crash? > > Why don't you put the ~E_DEPRECATED in conf.php as well? Thanks for the hint, now the errors are gone from Horde's log. But nevertheless I get an error "500 - Internal Server Error" in my browser like before. Is this error likely to be triggered by the webserver? Then I would have to look at lighty's error logs instead (Hope I find any). > >> >> 2015-10-28T20:49:19+01:00 DEBUG: HORDE [kronolith] PHP ERROR: >> Non-static method Date_Calc::dateToDays() should not be c >> alled statically, assuming $this from incompatible context [pid >> 12311 on line 4045 of "/usr/share/php/Date/Calc.php"] >> 2015-10-28T20:49:19+01:00 DEBUG: HORDE 1. >> Horde_Core_Ajax_Application->send() >> /var/www/horde/services/ajax.php:70 >> >> I'm getting frequent php-cgi-segfaults whenever this happens. >> >>>>>> Any help is greatly appreciated. >>>>> >>>>> >>>>> horde/config/conf.php - 'debug_level' >>>> >>>> Mike, you told me that a while ago and I did make the entry in >>>> horde/config/conf.php. The line looks like this: >>>> >>>> $conf['debug_level'] = E_ALL & ~E_NOTICE & ~E_STRICT; >>>> >>>> I wonder why the Local value in both cases (phpinfo() from >>>> test.php and from Horde PHP shell) is different. >>>> >>>> -- >>>> Greetings >>>> Jens >>>> >>>> -- >>>> Horde mailing list >>>> Frequently Asked Questions: http://horde.org/faq/ >>>> To unsubscribe, mail: horde-unsubscribe at lists.horde.org >> >> >> >> -- >> Horde mailing list >> Frequently Asked Questions: http://horde.org/faq/ >> To unsubscribe, mail: horde-unsubscribe at lists.horde.org From wahnes at uni-koeln.de Thu Oct 29 16:37:30 2015 From: wahnes at uni-koeln.de (Jens Wahnes) Date: Thu, 29 Oct 2015 17:37:30 +0100 Subject: [horde] Sharing user information between hooks In-Reply-To: <20151026150138.Horde.gi9GCSJfF6wSlkrjP8m4_l2@h4.theupstairsroom.com> References: <20151002095841.GD31122@coredump.rrz.uni-koeln.de> <20151002191428.Horde.9wk_cyFiBx0MkiODsqQ0Xcl@h4.theupstairsroom.com> <20151026144347.GB12631@coredump.rrz.uni-koeln.de> <20151026150138.Horde.gi9GCSJfF6wSlkrjP8m4_l2@h4.theupstairsroom.com> Message-ID: <20151029163730.GA20070@coredump.rrz.uni-koeln.de> On Mon, Oct 26 2015, at 15:01:38 +0000, Michael J Rubinsky wrote: > Quoting Jens Wahnes : >> The reason to introduce code to write things into the session was to >> save unnecessary LDAP requests that would otherwise have to be executed >> in both Horde's hooks and IMP's hooks. The bulk of LDAP requests we >> see, however, seems to stem from the fact that a complete session is >> set up (including hooks being run) whenever there is a request through >> CalDAV or such. And not only is a session created for the user >> performing the CalDAV request, but also for all users that have granted >> this user access to their calendars, plus all users that this user is >> granting access to his or her calendars. All in all, that's a lot of >> sessions with lots of LDAP requests. (Consider, for example, a group >> of just 5 people granting calendar access to each other's personal >> calendar. Then you've got 5 LDAP requests per every CalDAV request. >> If everyone within the group is accessing all 5 calendars via CalDAV, >> that's 5*5*5 = 125 LDAP requests for just 5 people.) >> >> So I came to the idea to use memcache to cache the LDAP data, since we >> make heavy use of memcache anyways. I dug around the Horde API docs a >> bit and came up with some code that looks like this (not exactly, but >> close enough): >> >> >> $memcache = >> $GLOBALS['injector']->getInstance('Horde_Core_Factory_HashTable')->create($GLOBALS['injector']); > > This should be: $GLOBALS['injector']->getInstance('Horde_HashTable'); Thank you for pointing this out. It feels much better to have code that interfaces with the rest of the system the way it is intended to work. :) However, even when using the "getInstance('Horde_HashTable')" code, the old problem remains that the prefix for memcache keys ($conf['hashtable']['params']['prefix'] from conf.php) is not used. Not such a big problem since I can work around that, after all, but still leaves me with a feeling I'm not calling the Horde code correctly. Can you shed some light on that? > The Horde_Core_Factory_HashTable class is registered with the injector > as the factory to use to create the hash table driver. If interested, > this is done in Horde_Registry::__construct(). Unfortunately, I don't quite unterstand what you're trying to tell me. Should this give me a clue as to where to look for code that does the prefix handling? Or is it totally unrelated to that question? Jens -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: Digital signature URL: From mrubinsk at horde.org Thu Oct 29 16:47:46 2015 From: mrubinsk at horde.org (Michael J Rubinsky) Date: Thu, 29 Oct 2015 16:47:46 +0000 Subject: [horde] Sharing user information between hooks In-Reply-To: <20151029163730.GA20070@coredump.rrz.uni-koeln.de> References: <20151002095841.GD31122@coredump.rrz.uni-koeln.de> <20151002191428.Horde.9wk_cyFiBx0MkiODsqQ0Xcl@h4.theupstairsroom.com> <20151026144347.GB12631@coredump.rrz.uni-koeln.de> <20151026150138.Horde.gi9GCSJfF6wSlkrjP8m4_l2@h4.theupstairsroom.com> <20151029163730.GA20070@coredump.rrz.uni-koeln.de> Message-ID: <20151029164746.Horde.SytueaE8IFccnX_FMrShfky@h4.theupstairsroom.com> Quoting Jens Wahnes : > On Mon, Oct 26 2015, at 15:01:38 +0000, Michael J Rubinsky wrote: > >> Quoting Jens Wahnes : >>> The reason to introduce code to write things into the session was to >>> save unnecessary LDAP requests that would otherwise have to be executed >>> in both Horde's hooks and IMP's hooks. The bulk of LDAP requests we >>> see, however, seems to stem from the fact that a complete session is >>> set up (including hooks being run) whenever there is a request through >>> CalDAV or such. And not only is a session created for the user >>> performing the CalDAV request, but also for all users that have granted >>> this user access to their calendars, plus all users that this user is >>> granting access to his or her calendars. All in all, that's a lot of >>> sessions with lots of LDAP requests. (Consider, for example, a group >>> of just 5 people granting calendar access to each other's personal >>> calendar. Then you've got 5 LDAP requests per every CalDAV request. >>> If everyone within the group is accessing all 5 calendars via CalDAV, >>> that's 5*5*5 = 125 LDAP requests for just 5 people.) >>> >>> So I came to the idea to use memcache to cache the LDAP data, since we >>> make heavy use of memcache anyways. I dug around the Horde API docs a >>> bit and came up with some code that looks like this (not exactly, but >>> close enough): >>> >>> >>> $memcache = >>> $GLOBALS['injector']->getInstance('Horde_Core_Factory_HashTable')->create($GLOBALS['injector']); >> >> This should be: $GLOBALS['injector']->getInstance('Horde_HashTable'); > > Thank you for pointing this out. It feels much better to have code > that interfaces with the rest of the system the way it is intended to > work. :) > > However, even when using the "getInstance('Horde_HashTable')" code, the > old problem remains that the prefix for memcache keys > ($conf['hashtable']['params']['prefix'] from conf.php) is not used. > Not such a big problem since I can work around that, after all, but > still leaves me with a feeling I'm not calling the Horde code > correctly. Can you shed some light on that? I'll take a look. I'm not *that* familiar with the memcache code. I see some places where we *might* be missing prepending the keys, but I'm not sure. >> The Horde_Core_Factory_HashTable class is registered with the injector >> as the factory to use to create the hash table driver. If interested, >> this is done in Horde_Registry::__construct(). > > Unfortunately, I don't quite unterstand what you're trying to tell me. > Should this give me a clue as to where to look for code that does the > prefix handling? Or is it totally unrelated to that question? Sorry, I was just explaining why the getInstance('Horde_HashTable') works the way it does, and where the code is that registers the injector/factory names in case you were interested. :) -- mike The Horde Project http://www.horde.org https://www.facebook.com/hordeproject https://www.twitter.com/hordeproject -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5751 bytes Desc: S/MIME Signature URL: From mrubinsk at horde.org Thu Oct 29 16:53:10 2015 From: mrubinsk at horde.org (Michael J Rubinsky) Date: Thu, 29 Oct 2015 16:53:10 +0000 Subject: [horde] Sharing user information between hooks In-Reply-To: <20151029164746.Horde.SytueaE8IFccnX_FMrShfky@h4.theupstairsroom.com> References: <20151002095841.GD31122@coredump.rrz.uni-koeln.de> <20151002191428.Horde.9wk_cyFiBx0MkiODsqQ0Xcl@h4.theupstairsroom.com> <20151026144347.GB12631@coredump.rrz.uni-koeln.de> <20151026150138.Horde.gi9GCSJfF6wSlkrjP8m4_l2@h4.theupstairsroom.com> <20151029163730.GA20070@coredump.rrz.uni-koeln.de> <20151029164746.Horde.SytueaE8IFccnX_FMrShfky@h4.theupstairsroom.com> Message-ID: <20151029165310.Horde.TBNGQJsQqz2Q7Dh_TilZmxI@h4.theupstairsroom.com> Quoting Michael J Rubinsky : > Quoting Jens Wahnes : > >> On Mon, Oct 26 2015, at 15:01:38 +0000, Michael J Rubinsky wrote: >> >>> Quoting Jens Wahnes : >>>> The reason to introduce code to write things into the session was to >>>> save unnecessary LDAP requests that would otherwise have to be executed >>>> in both Horde's hooks and IMP's hooks. The bulk of LDAP requests we >>>> see, however, seems to stem from the fact that a complete session is >>>> set up (including hooks being run) whenever there is a request through >>>> CalDAV or such. And not only is a session created for the user >>>> performing the CalDAV request, but also for all users that have granted >>>> this user access to their calendars, plus all users that this user is >>>> granting access to his or her calendars. All in all, that's a lot of >>>> sessions with lots of LDAP requests. (Consider, for example, a group >>>> of just 5 people granting calendar access to each other's personal >>>> calendar. Then you've got 5 LDAP requests per every CalDAV request. >>>> If everyone within the group is accessing all 5 calendars via CalDAV, >>>> that's 5*5*5 = 125 LDAP requests for just 5 people.) >>>> >>>> So I came to the idea to use memcache to cache the LDAP data, since we >>>> make heavy use of memcache anyways. I dug around the Horde API docs a >>>> bit and came up with some code that looks like this (not exactly, but >>>> close enough): >>>> >>>> >>>> $memcache = >>>> $GLOBALS['injector']->getInstance('Horde_Core_Factory_HashTable')->create($GLOBALS['injector']); >>> >>> This should be: $GLOBALS['injector']->getInstance('Horde_HashTable'); >> >> Thank you for pointing this out. It feels much better to have code >> that interfaces with the rest of the system the way it is intended to >> work. :) >> >> However, even when using the "getInstance('Horde_HashTable')" code, the >> old problem remains that the prefix for memcache keys >> ($conf['hashtable']['params']['prefix'] from conf.php) is not used. >> Not such a big problem since I can work around that, after all, but >> still leaves me with a feeling I'm not calling the Horde code >> correctly. Can you shed some light on that? > > I'll take a look. I'm not *that* familiar with the memcache code. I > see some places where we *might* be missing prepending the keys, but > I'm not sure. Actually, the only place that this might be wrong is in the lock/unlock methods. Setting/deleting should work as expected. Horde_HashTable_Base:: has set/delete/get etc... methods that call a hkey() method which adds the prefix. After the prefix is added, the concrete _set/_delete etc... methods are called using the already prefixed keys. You'll have to check there to see why it's not working. Alternatively, check that the expected config values are being grabbed in Horde_Core_Factory_Hashtable. -- mike The Horde Project http://www.horde.org https://www.facebook.com/hordeproject https://www.twitter.com/hordeproject -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5751 bytes Desc: S/MIME Signature URL: From ballier at mail.schule.de Fri Oct 30 07:39:50 2015 From: ballier at mail.schule.de (Ralph Ballier) Date: Fri, 30 Oct 2015 08:39:50 +0100 Subject: [horde] Issue with VFS In-Reply-To: <20151027083141.Horde.eirCC0DxEbwUuTGucXkU9Ca@horde.osz-lise-meitner.eu> Message-ID: <20151030083950.Horde._ELBLVAcRyCFm1cchfv8Wxr@horde.osz-lise-meitner.eu> Zitat von Ralph Ballier : > Hello, > > if I try to move a file in VFS to an other folder, then I get the > following > error message. But it is possible to delete the same file. > > Ralph > > A FATAL ERROR HAS OCCURRED > > UNABLE TO DELETE VFS FILE. > > 1. Gollem::moveFile() /www/htdocs/horde2/gollem/manager.php:169 2. > Gollem::_copyFile() /www/htdocs/horde2/gollem/lib/Gollem.php:480 3. > Gollem::moveFile() /www/htdocs/horde2/gollem/manager.php:169 4. > Gollem::_copyFile() /www/htdocs/horde2/gollem/lib/Gollem.php:480 5. > Horde_Vfs_Sql->deleteFile() /www/htdocs/horde2/gollem/lib/Gollem.php:557 > > DETAILS > > The Full Error Message Is Logged In Horde's Log File, And Is Shown Below > Only To Administrators. Non-administrative Users Will Not See Error > Details. > > Gollem_Exception Object (? ? ?[details] =>? ? ? [logged] => 1 > [_logLevel:protected] => 0? ? ?[message:protected] => Unable to delete VFS > file.? ? ?[string:Exception:private] =>? ? ? [code:protected] => 0 > [file:protected] => /www/htdocs/horde2/gollem/lib/Gollem.php > [line:protected] => 560? ? ?[trace:Exception:private] => Array? ? ? ? ?( > ? ? ? ? [0] => Array? ? ? ? ? ? ? ? ?(? ? ? ? ? ? ? ? ? ? ?[file] => > /www/htdocs/horde2/gollem/lib/Gollem.php? ? ? ? ? ? ? ? ? ? ?[line] => 480 > ? ? ? ? ? ? ? ? ? [function] => _copyFile? ? ? ? ? ? ? ? ? ? ?[class] => > Gollem? ? ? ? ? ? ? ? ? ? ?[type] => ::? ? ? ? ? ? ? ? ? ? ?[args] => > Array > ? ? ? ? ? ? ? ? ? ? ? ?(? ? ? ? ? ? ? ? ? ? ? ? ? ? ?[0] => move > ? ? ? ? ? ? ? ? ?[1] => sqlhome? ? ? ? ? ? ? ? ? ? ? ? ? ? ?[2] => > /home/admin? ? ? ? ? ? ? ? ? ? ? ? ? ? ?[3] => Dok1.pdf > ? ? ? ?[4] => sqlhome? ? ? ? ? ? ? ? ? ? ? ? ? ? ?[5] => > /home/admin/Folder_1? ? ? ? ? ? ? ? ? ? ? ? ?)? ? ? ? ? ? ? ? ? ) > ? [1] => Array? ? ? ? ? ? ? ? ?(? ? ? ? ? ? ? ? ? ? ?[file] => > /www/htdocs/horde2/gollem/manager.php? ? ? ? ? ? ? ? ? ? ?[line] => 169 > ? ? ? ? ? ? ? ?[function] => moveFile? ? ? ? ? ? ? ? ? ? ?[class] => > Gollem? ? ? ? ? ? ? ? ? ? ?[type] => ::? ? ? ? ? ? ? ? ? ? ?[args] => > Array > ? ? ? ? ? ? ? ? ? ? ? ?(? ? ? ? ? ? ? ? ? ? ? ? ? ? ?[0] => sqlhome > ? ? ? ? ? ? ? ? ? ? [1] => /home/admin? ? ? ? ? ? ? ? ? ? ? ? ? ? ?[2] => > Dok1.pdf? ? ? ? ? ? ? ? ? ? ? ? ? ? ?[3] => sqlhome > ? ?[4] => /home/admin/Folder_1? ? ? ? ? ? ? ? ? ? ? ? ?) > )? ? ? ? ? )? ? ? [previous:Exception:private] => Horde_Vfs_Exception > Object? ? ? ? ?(? ? ? ? ? ? ?[details] =>? ? ? ? ? ? ? [logged] => > ? ?[_logLevel:protected] => 0? ? ? ? ? ? ?[message:protected] => Unable to > delete VFS file.? ? ? ? ? ? ?[string:Exception:private] => > [code:protected] => 0? ? ? ? ? ? ?[file:protected] => > /usr/lib/php/Horde/Vfs/Sql.php? ? ? ? ? ? ?[line:protected] => 303 > ? [trace:Exception:private] => Array? ? ? ? ? ? ? ? ?( > [0] => Array? ? ? ? ? ? ? ? ? ? ? ? ?(? ? ? ? ? ? ? ? ? ? ? ? ? ? ?[file] > => /www/htdocs/horde2/gollem/lib/Gollem.php > [line] => 557? ? ? ? ? ? ? ? ? ? ? ? ? ? ?[function] => deleteFile > ? ? ? ? ? ? ? ? ? [class] => Horde_Vfs_Sql > [type] => ->? ? ? ? ? ? ? ? ? ? ? ? ? ? ?[args] => Array > ? ? ? ? ? ? (? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?[0] => /home/admin > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?[1] => Dok1.pdf > )? ? ? ? ? ? ? ? ? ? ? ? ? )? ? ? ? ? ? ? ? ? ? ? [1] => Array > ? ? ? ? ? ? (? ? ? ? ? ? ? ? ? ? ? ? ? ? ?[file] => > /www/htdocs/horde2/gollem/lib/Gollem.php? ? ? ? ? ? ? ? ? ? ? ? ? ? > ?[line] > => 480? ? ? ? ? ? ? ? ? ? ? ? ? ? ?[function] => _copyFile > ? ? ? ? ? [class] => Gollem? ? ? ? ? ? ? ? ? ? ? ? ? ? ?[type] => :: > ? ? ? ? ? ? ? ? ? ? ?[args] => Array? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?( > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?[0] => move > ? ?[1] => sqlhome? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?[2] => /home/admin > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?[3] => Dok1.pdf > ? ? ? ? ?[4] => sqlhome? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?[5] => > /home/admin/Folder_1? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?) > ? ?)? ? ? ? ? ? ? ? ? ? ? [2] => Array? ? ? ? ? ? ? ? ? ? ? ? ?( > ? ? ? ? ? ? ? ? ?[file] => /www/htdocs/horde2/gollem/manager.php > ? ? ? ? ? ? ? ? ?[line] => 169? ? ? ? ? ? ? ? ? ? ? ? ? ? ?[function] => > moveFile? ? ? ? ? ? ? ? ? ? ? ? ? ? ?[class] => Gollem > ? ? ? [type] => ::? ? ? ? ? ? ? ? ? ? ? ? ? ? ?[args] => Array > ? ? ? ? ? ? ? ? ? ?(? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?[0] => sqlhome > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? [1] => /home/admin > ? ? ? ? ? ?[2] => Dok1.pdf? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?[3] => > sqlhome? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?[4] => /home/admin/Folder_1 > ? ? ? ? ? ? ? ? ? ? ? ? ? ?)? ? ? ? ? ? ? ? ? ? ? ? ? )? ? ? ? ? ? ? ? ? ) > ? ? ? ? ? ? [previous:Exception:private] =>? ? ? ? ? )? ) > -- > Horde mailing list > Frequently Asked Questions: http://horde.org/faq/To unsubscribe, mail: > horde-unsubscribe at lists.horde.org Has nobody this problem? But I concede this is not a true problem. I can copy and then delete the old file. But I mean, it's not good for a normal user to see such a drastic error message. Ralph From ballier at mail.schule.de Fri Oct 30 09:08:36 2015 From: ballier at mail.schule.de (Ralph Ballier) Date: Fri, 30 Oct 2015 10:08:36 +0100 Subject: [horde] Flags, categories and labels Message-ID: <20151030100836.Horde.fuINHyu5X4daAdR_L7lwU89@horde.osz-lise-meitner.eu> Hello, I hope the subject has not to much elements, but I mean this is a similar theme. In "Preferences for Mail" I can define new flags. In "Global preferences" I can define new categories and labels". But I can nowhere see where I can use it. Ralph From ballier at mail.schule.de Fri Oct 30 09:22:29 2015 From: ballier at mail.schule.de (Ralph Ballier) Date: Fri, 30 Oct 2015 10:22:29 +0100 Subject: [horde] Tags Message-ID: <20151030102229.Horde.rp7ymxP-Pe18f6zv6oxljRT@horde.osz-lise-meitner.eu> Hello, is it possible to search for more the one tag in the calendar? Such as: to find appointments with the tags "holidays" and "department_2"? Ralph From mrubinsk at horde.org Fri Oct 30 14:40:12 2015 From: mrubinsk at horde.org (Michael J Rubinsky) Date: Fri, 30 Oct 2015 14:40:12 +0000 Subject: [horde] Flags, categories and labels In-Reply-To: <20151030100836.Horde.fuINHyu5X4daAdR_L7lwU89@horde.osz-lise-meitner.eu> Message-ID: <20151030144012.Horde.MQk3x6W2W05hPmBi9tDcEk_@h4.theupstairsroom.com> Quoting Ralph Ballier : > Hello, > > I hope the subject has not to much elements, but I mean this is a similar > theme. > > In "Preferences for Mail" I can define new flags. In "Global preferences" I > can define new categories and labels". But I can nowhere see where I can > use it. Flags in IMP are usable within IMP - where you can right click a message in the message list and "Mark As" a flag. Categories and labels in the Global preferences are a legacy feature that has been slowly being phased out. Off hand, I'm not sure if any of the current versions of the released applications utilize these categories or not, but they are completely gone in the development branch. Categories have been replaced by "Tags". -- mike The Horde Project http://www.horde.org https://www.facebook.com/hordeproject https://www.twitter.com/hordeproject -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5751 bytes Desc: S/MIME Signature URL: From mrubinsk at horde.org Fri Oct 30 14:48:39 2015 From: mrubinsk at horde.org (Michael J Rubinsky) Date: Fri, 30 Oct 2015 14:48:39 +0000 Subject: [horde] Tags In-Reply-To: <20151030102229.Horde.rp7ymxP-Pe18f6zv6oxljRT@horde.osz-lise-meitner.eu> Message-ID: <20151030144839.Horde.QBe5uOPJAtdEAYES3XcMmLg@h4.theupstairsroom.com> Quoting Ralph Ballier : > Hello, > > is it possible to search for more the one tag in the calendar? > > Such as: to find appointments with the tags "holidays" and "department_2"? Not currently. -- mike The Horde Project http://www.horde.org https://www.facebook.com/hordeproject https://www.twitter.com/hordeproject -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5751 bytes Desc: S/MIME Signature URL: From ballier at mail.schule.de Fri Oct 30 15:12:23 2015 From: ballier at mail.schule.de (Ralph Ballier) Date: Fri, 30 Oct 2015 16:12:23 +0100 Subject: [horde] Tags Message-ID: <20151030161223.Horde.62S2V7jeidyG_5zIn4U-iVX@horde.osz-lise-meitner.eu> Zitat von Michael J Rubinsky : > Quoting Ralph Ballier : > >> Hello, >> >> is it possible to search for more the one tag in the calendar? >> >> Such as: to find appointments with the tags "holidays" and >> "department_2"? > > Not currently. > > -- > mike > The Horde Project > http://www.horde.org > https://www.facebook.com/hordeprojecthttps://www.twitter.com/hordeproject So I will make a workaround: tag "holidays", tag "department_2" and tag "holidays and department_2", but better where a "AND" or "OR" search. Ralph Ralph Ballier Abteilungsleiter an der Lise-Meitner-Schule Rudower Stra?e 184 12351 Berlin Tel.: +49 30 660689-25/-24/-0 From wahnes at uni-koeln.de Fri Oct 30 17:13:38 2015 From: wahnes at uni-koeln.de (Jens Wahnes) Date: Fri, 30 Oct 2015 18:13:38 +0100 Subject: [horde] Sharing user information between hooks In-Reply-To: <20151029165310.Horde.TBNGQJsQqz2Q7Dh_TilZmxI@h4.theupstairsroom.com> References: <20151002095841.GD31122@coredump.rrz.uni-koeln.de> <20151002191428.Horde.9wk_cyFiBx0MkiODsqQ0Xcl@h4.theupstairsroom.com> <20151026144347.GB12631@coredump.rrz.uni-koeln.de> <20151026150138.Horde.gi9GCSJfF6wSlkrjP8m4_l2@h4.theupstairsroom.com> <20151029163730.GA20070@coredump.rrz.uni-koeln.de> <20151029164746.Horde.SytueaE8IFccnX_FMrShfky@h4.theupstairsroom.com> <20151029165310.Horde.TBNGQJsQqz2Q7Dh_TilZmxI@h4.theupstairsroom.com> Message-ID: <20151030171338.GB20070@coredump.rrz.uni-koeln.de> On Thu, Oct 29 2015, at 16:53:10 +0000, Michael J Rubinsky wrote: > Quoting Michael J Rubinsky : >> Quoting Jens Wahnes : >>> On Mon, Oct 26 2015, at 15:01:38 +0000, Michael J Rubinsky wrote: >>>> This should be: $GLOBALS['injector']->getInstance('Horde_HashTable'); >>> Thank you for pointing this out. It feels much better to have code >>> that interfaces with the rest of the system the way it is intended to >>> work. :) >>> >>> However, even when using the "getInstance('Horde_HashTable')" code, the >>> old problem remains that the prefix for memcache keys >>> ($conf['hashtable']['params']['prefix'] from conf.php) is not used. >>> Not such a big problem since I can work around that, after all, but >>> still leaves me with a feeling I'm not calling the Horde code >>> correctly. Can you shed some light on that? >> I'll take a look. I'm not *that* familiar with the memcache code. I >> see some places where we *might* be missing prepending the keys, but >> I'm not sure. > Actually, the only place that this might be wrong is in the lock/unlock > methods. Setting/deleting should work as expected. > Horde_HashTable_Base:: has set/delete/get etc... methods that call a > hkey() method which adds the prefix. After the prefix is added, the > concrete _set/_delete etc... methods are called using the already > prefixed keys. You'll have to check there to see why it's not working. Thanks for looking this up, but I don't know how would I go about that. Should I add some code to these classes to write additional info to the log file? Or can this be done through some external PHP debugging methods? I've heard of xdebug, but I've never really used it so far. > Alternatively, check that the expected config values are being grabbed > in Horde_Core_Factory_Hashtable. To me, that seems to be the case. In the debug info I get (I added a statement "Horde::debug($memcache)"), the prefix info is present. Here's an excerpt from that: object(Horde_HashTable_Memcache)#125 (4) { ["_memcache":protected]=> object(Horde_Memcache)#121 (6) { ["_locks":protected]=> array(0) { } ["_logger":protected]=> object(Horde_Core_Log_Wrapper)#95 (0) { } ["_memcache":protected]=> object(Memcache)#124 (2) { ["connection"]=> resource(11) of type (memcache connection) ["_failureCallback"]=> array(2) { [0]=> *RECURSION* [1]=> string(8) "failover" } } ["_noexist":protected]=> array(0) { } ["_params":protected]=> array(10) { ["compression"]=> bool(true) ["hostspec"]=> array(2) { [0]=> string(9) "localhost" [1]=> string(26) "foo.bar.example.com" } ["large_items"]=> bool(true) ["persistent"]=> bool(true) ["port"]=> array(2) { [0]=> string(5) "11211" [1]=> string(5) "11211" } ["prefix"]=> string(8) "HordeSam" ["weight"]=> array(2) { [0]=> string(2) "90" [1]=> string(2) "10" } ["c_threshold"]=> int(1200) ["umask"]=> int(63) ["logger"]=> object(Horde_Core_Log_Wrapper)#95 (0) { } } When I grepped through the log file, I could see that there is only one other type of memcache keys which do not seem to include the set prefix. They are related to IMAP access and look like this: 2015-10-30T15:00:26+01:00 DEBUG: HORDE [imp] Horde_HashTable_Memcache: Retrieved keys (horde_imap_client|user1|INBOX|localhost|143|10289) [pid 16337 on line 233 of "/usr/share/pear/Horde/HashTable/Base.php"] Does this give anyone a clue, maybe? What's so special about Horde_Imap_Client? All other entries do have the prefix. They all look just like this one: 2015-10-30T15:00:26+01:00 DEBUG: HORDE [imp] Horde_HashTable_Memcache: Retrieved keys (HordeSamperm_sql_exists_2kronolith,HordeSamperm_sql_exists_2kronolith_t) [pid 16337 on line 233 of "/usr/share/pear/Horde/HashTable/Base.php"] Jens -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: Digital signature URL: From ballier at mail.schule.de Sat Oct 31 12:38:26 2015 From: ballier at mail.schule.de (Ralph Ballier) Date: Sat, 31 Oct 2015 13:38:26 +0100 Subject: [horde] Problems with whups In-Reply-To: <20151019153632.Horde.vJGTme0ZseIPKViBICimu_c@horde.osz-lise-meitner.eu> References: <20151011122537.Horde.xfgmsif9Jz_iAi_dI6Iz5ln@horde.osz-lise-meitner.eu> <20151011151306.Horde.eGbmnpoyBwAjNHpOINlyd2H@h4.theupstairsroom.com> <20151019153632.Horde.vJGTme0ZseIPKViBICimu_c@horde.osz-lise-meitner.eu> Message-ID: <20151031133826.Horde.abw71PHPkeHrAVnCreS2G3Y@horde.osz-lise-meitner.eu> Zitat von Ralph Ballier : > Zitat von Michael J Rubinsky : > >> Quoting Ralph Ballier : >> >>> Hello, >>> ? >>> I installed "whups" over PEAR. >>> >>> Unfortunately when I call it, the error message "Missing >>> Horde_Db_Adapter_Base" appears. >>> ? >>> Where is the mistake? >> >> Hard to say with the information you provided. Was this a complete new >> install of Horde? Any errors in the PEAR install output? Did you use a >> separate, or the system, PEAR install? >> >> -- >> mike >> The Horde Project >> http://www.horde.org >> https://www.facebook.com/hordeprojecthttps://www.twitter.com/hordeproject >> ? > > This is a new install of Horde. I have always use "pear install ...".? > > I can only remember one error message: "The configuration file is not > writable". Then I have "chown -R www.www[1]" and after this it was > writable. > > After all I have made "pear uninstall whups" and Horde was working well > again. > -- > Horde mailing list > Frequently Asked Questions: http://horde.org/faq/To unsubscribe, mail: > horde-unsubscribe at lists.horde.org I have tried again to install whups. Again the error message "Missing Horde_Db_Adapter_Base". I attach the detailed error message. Again I must deinstall whups with "pear uninstall horde/whups", otherwise it was not possible to work with horde. What means "Horde_Db_Adapter_Base"? Ralph A FATAL ERROR HAS OCCURRED MISSING HORDE_DB_ADAPTER_BASE ?1. Horde_Injector->getInstance() /www/htdocs/horde2/kronolith/index.php:144 ?2. Horde_Injector->createInstance() /usr/lib/php/Horde/Injector.php:272 ?3. Horde_Injector_Binder_AnnotatedSetters->create() /usr/lib/php/Horde/Injector.php:238 ?4. Horde_Injector_Binder_Implementation->create() /usr/lib/php/Horde/Injector/Binder/AnnotatedSetters.php:78 ?5. Horde_Injector_Binder_Implementation->_getInstance() /usr/lib/php/Horde/Injector/Binder/Implementation.php:70 ?6. ReflectionClass->newInstanceArgs() /usr/lib/php/Horde/Injector/Binder/Implementation.php:88 ?7. Horde_View_Topbar->__construct() ?8. Horde_Core_Topbar->getTree() /www/htdocs/horde2/lib/View/Topbar.php:54 ?9. Horde_Registry->hasPermission() /usr/lib/php/Horde/Core/Topbar.php:78 10. Horde_Registry->isAuthenticated() /usr/lib/php/Horde/Registry.php:1729 11. Horde_Registry->checkExistingAuth() /usr/lib/php/Horde/Registry.php:2180 12. Horde_Core_Auth_Application->validateAuth() /usr/lib/php/Horde/Registry.php:2642 13. Horde_Registry->callAppMethod() /usr/lib/php/Horde/Core/Auth/Application.php:187 14. Horde_Registry->pushApp() /usr/lib/php/Horde/Registry.php:1189 15. Horde_Registry->setLanguageEnvironment() /usr/lib/php/Horde/Registry.php:1590 16. Horde_Registry->setLanguage() /usr/lib/php/Horde/Registry.php:2927 17. Horde_Registry->callAppMethod() /usr/lib/php/Horde/Registry.php:2902 18. Horde_Registry->pushApp() /usr/lib/php/Horde/Registry.php:1189 19. Horde_Registry->_pushAppError() /usr/lib/php/Horde/Registry.php:1630 20. Horde_Injector->getInstance() /www/htdocs/horde2/kronolith/index.php:144 21. Horde_Injector->createInstance() /usr/lib/php/Horde/Injector.php:272 22. Horde_Injector_Binder_AnnotatedSetters->create() /usr/lib/php/Horde/Injector.php:238 23. Horde_Injector_Binder_Implementation->create() /usr/lib/php/Horde/Injector/Binder/AnnotatedSetters.php:78 24. Horde_Injector_Binder_Implementation->_getInstance() /usr/lib/php/Horde/Injector/Binder/Implementation.php:70 25. ReflectionClass->newInstanceArgs() /usr/lib/php/Horde/Injector/Binder/Implementation.php:88 26. Horde_View_Topbar->__construct() 27. Horde_Core_Topbar->getTree() /www/htdocs/horde2/lib/View/Topbar.php:54 28. Horde_Registry->hasPermission() /usr/lib/php/Horde/Core/Topbar.php:78 29. Horde_Registry->isAuthenticated() /usr/lib/php/Horde/Registry.php:1729 30. Horde_Registry->checkExistingAuth() /usr/lib/php/Horde/Registry.php:2180 31. Horde_Core_Auth_Application->validateAuth() /usr/lib/php/Horde/Registry.php:2642 32. Horde_Registry->callAppMethod() /usr/lib/php/Horde/Core/Auth/Application.php:187 33. Horde_Registry->pushApp() /usr/lib/php/Horde/Registry.php:1189 34. Horde_Registry->setLanguageEnvironment() /usr/lib/php/Horde/Registry.php:1590 35. Horde_Registry->setLanguage() /usr/lib/php/Horde/Registry.php:2927 36. Horde_Registry->callAppMethod() /usr/lib/php/Horde/Registry.php:2902 37. Horde_Registry->pushApp() /usr/lib/php/Horde/Registry.php:1189 38. Horde_Registry->callAppMethod() /usr/lib/php/Horde/Registry.php:1625 39. call_user_func_array() /usr/lib/php/Horde/Registry.php:1192 40. Horde_Registry_Application->init() 41. Whups_Application->_init() /usr/lib/php/Horde/Registry/Application.php:105 42. Whups_Factory_Driver->create() /www/htdocs/horde2/whups/lib/Application.php:49 43. Whups_Driver_Sql->setStorage() /www/htdocs/horde2/whups/lib/Factory/Driver.php:41 ? Links: ------ [1] http://www.www From ballier at mail.schule.de Sat Oct 31 07:48:43 2015 From: ballier at mail.schule.de (Ralph Ballier) Date: Sat, 31 Oct 2015 08:48:43 +0100 Subject: [horde] What is meant with 'value' => 'a:0:{}' ? Message-ID: <20151031084843.Horde.IMjlga93ruviXkmuNQsOu3s@horde.osz-lise-meitner.eu> Hello, I try to understand the configuration of Horde. Sometimes there is a detailed information in the files, but sometime I don't find anything. An example is:?'value' => 'a:0:{}' I don't understand it. Where I can refer about this?? Thanks Ralph From ballier at mail.schule.de Sat Oct 31 09:42:29 2015 From: ballier at mail.schule.de (Ralph Ballier) Date: Sat, 31 Oct 2015 10:42:29 +0100 Subject: [horde] Public calendars Message-ID: <20151031104229.Horde.J4OTUXiLj-5JPXIoMeTmyFP@horde.osz-lise-meitner.eu> Hello, I have integrated a public calendar in a website. Now I can see the days of the months, but when I click at a day, ?I have to login. I think, this is not a public calender. You can see it, if you click at ?http://ods3.schule.de/kalender.html I had use the URL from inside of my horde installation:
Ralph From ballier at mail.schule.de Sat Oct 31 08:29:19 2015 From: ballier at mail.schule.de (Ralph Ballier) Date: Sat, 31 Oct 2015 09:29:19 +0100 Subject: [horde] What is meant with value => ... ? Message-ID: <20151031092919.Horde.LzTLQOjw09d9Q0F1nkVTIMs@horde.osz-lise-meitner.eu> Hello, I try to understand the configuration of Horde. Sometimes there is a detailed information in the files, but sometime I don't find anything. An example is:?'value' => 'a:0:{}' I don't understand it. Where I can refer about this?? Thanks Ralph ? From mrubinsk at horde.org Sat Oct 31 21:41:09 2015 From: mrubinsk at horde.org (Michael J Rubinsky) Date: Sat, 31 Oct 2015 21:41:09 +0000 Subject: [horde] What is meant with 'value' => 'a:0:{}' ? In-Reply-To: <20151031084843.Horde.IMjlga93ruviXkmuNQsOu3s@horde.osz-lise-meitner.eu> Message-ID: <20151031214109.Horde.9bTXZVg-xK2JyGzp1EGbe_M@h4.theupstairsroom.com> Quoting Ralph Ballier : > Hello, > > I try to understand the configuration of Horde. Sometimes there is a > detailed information in the files, but sometime I don't find anything. > > An example is:?'value' => 'a:0:{}' I don't understand it. Where I can > refer about this?? This is a php serialized array. The value of this particular one is: [] - an empty array. If you are trying to configure default pref values, for these types of values the best way to do it is to use a test user account to set the prefs the way you want them, then look up the values in the pref storage backend. -- mike The Horde Project http://www.horde.org https://www.facebook.com/hordeproject https://www.twitter.com/hordeproject -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5751 bytes Desc: S/MIME Signature URL: From mrubinsk at horde.org Sat Oct 31 21:44:25 2015 From: mrubinsk at horde.org (Michael J Rubinsky) Date: Sat, 31 Oct 2015 21:44:25 +0000 Subject: [horde] Public calendars In-Reply-To: <20151031104229.Horde.J4OTUXiLj-5JPXIoMeTmyFP@horde.osz-lise-meitner.eu> Message-ID: <20151031214425.Horde.bkxkK2btDOxZZzLUvejctew@h4.theupstairsroom.com> Quoting Ralph Ballier : > Hello, > > I have integrated a public calendar in a website. Now I can see the days of > the months, but when I click at a day, ?I have to login. I think, this is > not a public calender. Does the kronolith application have public permissions? (Admin->Permissions) > You can see it, if you click at ?http://ods3.schule.de/kalender.html > > I had use the URL from inside of my horde installation: > >
> > Ralph > -- > Horde mailing list > Frequently Asked Questions: http://horde.org/faq/ > To unsubscribe, mail: horde-unsubscribe at lists.horde.org -- mike The Horde Project http://www.horde.org https://www.facebook.com/hordeproject https://www.twitter.com/hordeproject -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5751 bytes Desc: S/MIME Signature URL: From mrubinsk at horde.org Sat Oct 31 21:48:21 2015 From: mrubinsk at horde.org (Michael J Rubinsky) Date: Sat, 31 Oct 2015 21:48:21 +0000 Subject: [horde] Problems with whups In-Reply-To: <20151031133826.Horde.abw71PHPkeHrAVnCreS2G3Y@horde.osz-lise-meitner.eu> References: <20151011122537.Horde.xfgmsif9Jz_iAi_dI6Iz5ln@horde.osz-lise-meitner.eu> <20151011151306.Horde.eGbmnpoyBwAjNHpOINlyd2H@h4.theupstairsroom.com> <20151019153632.Horde.vJGTme0ZseIPKViBICimu_c@horde.osz-lise-meitner.eu> <20151031133826.Horde.abw71PHPkeHrAVnCreS2G3Y@horde.osz-lise-meitner.eu> Message-ID: <20151031214821.Horde.M8KSP2tZyGGa9k_di4FI_FT@h4.theupstairsroom.com> Quoting Ralph Ballier : > Zitat von Ralph Ballier : > >> Zitat von Michael J Rubinsky : >> >>> Quoting Ralph Ballier : >>> >>>> Hello, >>>> ? >>>> I installed "whups" over PEAR. >>>> >>>> Unfortunately when I call it, the error message "Missing >>>> Horde_Db_Adapter_Base" appears. >>>> ? >>>> Where is the mistake? >>> >>> Hard to say with the information you provided. Was this a complete new >>> install of Horde? Any errors in the PEAR install output? Did you use a >>> separate, or the system, PEAR install? >>> >>> -- >>> mike >>> The Horde Project >>> http://www.horde.org >>> > https://www.facebook.com/hordeprojecthttps://www.twitter.com/hordeproject >>> ? >> >> This is a new install of Horde. I have always use "pear install ...".? >> >> I can only remember one error message: "The configuration file is not >> writable". Then I have "chown -R www.www[1]" and after this it was >> writable. >> >> After all I have made "pear uninstall whups" and Horde was working well >> again. >> -- >> Horde mailing list >> Frequently Asked Questions: http://horde.org/faq/To unsubscribe, mail: >> horde-unsubscribe at lists.horde.org > > I have tried again to install whups. Again the error message "Missing > Horde_Db_Adapter_Base". I attach the detailed error message. Again I must > deinstall whups with "pear uninstall horde/whups", otherwise it was not > possible to work with horde. > > What means "Horde_Db_Adapter_Base"? It's a class contained in the Horde_Db package. If it was *really* missing, just about everything that uses a database in your Horde install would be broken. Are you using the same PEAR executable to install Whups that you used to install your base install? > > Ralph > > A FATAL ERROR HAS OCCURRED > MISSING HORDE_DB_ADAPTER_BASE > ?1. Horde_Injector->getInstance() > /www/htdocs/horde2/kronolith/index.php:144 > ?2. Horde_Injector->createInstance() /usr/lib/php/Horde/Injector.php:272 > ?3. Horde_Injector_Binder_AnnotatedSetters->create() > /usr/lib/php/Horde/Injector.php:238 > ?4. Horde_Injector_Binder_Implementation->create() > /usr/lib/php/Horde/Injector/Binder/AnnotatedSetters.php:78 > ?5. Horde_Injector_Binder_Implementation->_getInstance() > /usr/lib/php/Horde/Injector/Binder/Implementation.php:70 > ?6. ReflectionClass->newInstanceArgs() > /usr/lib/php/Horde/Injector/Binder/Implementation.php:88 > ?7. Horde_View_Topbar->__construct() > ?8. Horde_Core_Topbar->getTree() /www/htdocs/horde2/lib/View/Topbar.php:54 > ?9. Horde_Registry->hasPermission() /usr/lib/php/Horde/Core/Topbar.php:78 > 10. Horde_Registry->isAuthenticated() /usr/lib/php/Horde/Registry.php:1729 > 11. Horde_Registry->checkExistingAuth() > /usr/lib/php/Horde/Registry.php:2180 > 12. Horde_Core_Auth_Application->validateAuth() > /usr/lib/php/Horde/Registry.php:2642 > 13. Horde_Registry->callAppMethod() > /usr/lib/php/Horde/Core/Auth/Application.php:187 > 14. Horde_Registry->pushApp() /usr/lib/php/Horde/Registry.php:1189 > 15. Horde_Registry->setLanguageEnvironment() > /usr/lib/php/Horde/Registry.php:1590 > 16. Horde_Registry->setLanguage() /usr/lib/php/Horde/Registry.php:2927 > 17. Horde_Registry->callAppMethod() /usr/lib/php/Horde/Registry.php:2902 > 18. Horde_Registry->pushApp() /usr/lib/php/Horde/Registry.php:1189 > 19. Horde_Registry->_pushAppError() /usr/lib/php/Horde/Registry.php:1630 > 20. Horde_Injector->getInstance() > /www/htdocs/horde2/kronolith/index.php:144 > 21. Horde_Injector->createInstance() /usr/lib/php/Horde/Injector.php:272 > 22. Horde_Injector_Binder_AnnotatedSetters->create() > /usr/lib/php/Horde/Injector.php:238 > 23. Horde_Injector_Binder_Implementation->create() > /usr/lib/php/Horde/Injector/Binder/AnnotatedSetters.php:78 > 24. Horde_Injector_Binder_Implementation->_getInstance() > /usr/lib/php/Horde/Injector/Binder/Implementation.php:70 > 25. ReflectionClass->newInstanceArgs() > /usr/lib/php/Horde/Injector/Binder/Implementation.php:88 > 26. Horde_View_Topbar->__construct() > 27. Horde_Core_Topbar->getTree() /www/htdocs/horde2/lib/View/Topbar.php:54 > 28. Horde_Registry->hasPermission() /usr/lib/php/Horde/Core/Topbar.php:78 > 29. Horde_Registry->isAuthenticated() /usr/lib/php/Horde/Registry.php:1729 > 30. Horde_Registry->checkExistingAuth() > /usr/lib/php/Horde/Registry.php:2180 > 31. Horde_Core_Auth_Application->validateAuth() > /usr/lib/php/Horde/Registry.php:2642 > 32. Horde_Registry->callAppMethod() > /usr/lib/php/Horde/Core/Auth/Application.php:187 > 33. Horde_Registry->pushApp() /usr/lib/php/Horde/Registry.php:1189 > 34. Horde_Registry->setLanguageEnvironment() > /usr/lib/php/Horde/Registry.php:1590 > 35. Horde_Registry->setLanguage() /usr/lib/php/Horde/Registry.php:2927 > 36. Horde_Registry->callAppMethod() /usr/lib/php/Horde/Registry.php:2902 > 37. Horde_Registry->pushApp() /usr/lib/php/Horde/Registry.php:1189 > 38. Horde_Registry->callAppMethod() /usr/lib/php/Horde/Registry.php:1625 > 39. call_user_func_array() /usr/lib/php/Horde/Registry.php:1192 > 40. Horde_Registry_Application->init() > 41. Whups_Application->_init() > /usr/lib/php/Horde/Registry/Application.php:105 > 42. Whups_Factory_Driver->create() > /www/htdocs/horde2/whups/lib/Application.php:49 > 43. Whups_Driver_Sql->setStorage() > /www/htdocs/horde2/whups/lib/Factory/Driver.php:41 > ? > > > > Links: > ------ > [1] http://www.www > -- > Horde mailing list > Frequently Asked Questions: http://horde.org/faq/ > To unsubscribe, mail: horde-unsubscribe at lists.horde.org -- mike The Horde Project http://www.horde.org https://www.facebook.com/hordeproject https://www.twitter.com/hordeproject -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5751 bytes Desc: S/MIME Signature URL: