[Kolab-devel] php failure undefined method Horde_Kolab_Server_ldap::uidForIdOrMail (openSUSE native)

Gunnar Wrobel wrobel at pardus.de
Sun Mar 1 22:16:36 CET 2009


Quoting Richard Bos <ml at radoeka.nl>:

> Hi Gunnar,
>
> Op woensdag 25 februari 2009 12:13:16 schreef Gunnar Wrobel:
>> > which is not so bad ;)
>>
>> In my eyes this is very, very bad ;)
>>
>> You don't link stuff from an installed web application into the  
>> system  libraries. This is not okay.
>
> I have changed the rpm now, so the horde/lib is added to the include_path in
> php.ini during rpm installation.  This works but....  
> /srv/www/htdocs/horde/lib
> must come before: /usr/share/php5/PEAR.  If the latter is placed before the
> /srv/www/htdocs/horde/lib some the tests fail with:
>
> = /usr/share/php5/PEAR/test/Kolab_Filter/Horde/Kolab/Filter/AllTests.php =
>
> 1) testRecurrenceInvitation(Horde_Kolab_Filter_ResourceTest)
> Only variable references should be returned by reference
> /usr/share/php5/PEAR/Horde/iCalendar.php:376
> /usr/share/php5/PEAR/Horde/Kolab/Resource.php:290
> /usr/share/php5/PEAR/Horde/Kolab/Resource.php:451
> /usr/share/php5/PEAR/Horde/Kolab/Filter/Incoming.php:141
> /usr/share/php5/PEAR/Horde/Kolab/Filter/Base.php:132
> /usr/share/php5/PEAR/Horde/Kolab/Test/Filter.php:259
> /usr/share/php5/PEAR/test/Kolab_Filter/Horde/Kolab/Filter/ResourceTest.php:78
> /usr/share/php5/PEAR/test/Kolab_Filter/Horde/Kolab/Filter/AllTests.php:36
> /usr/share/php5/PEAR/test/Kolab_Filter/Horde/Kolab/Filter/AllTests.php:63
>
> 2) testLongStringInvitation(Horde_Kolab_Filter_ResourceTest)
> Only variable references should be returned by reference
> /usr/share/php5/PEAR/Horde/iCalendar.php:376
> /usr/share/php5/PEAR/Horde/Kolab/Resource.php:290
> /usr/share/php5/PEAR/Horde/Kolab/Resource.php:451
> /usr/share/php5/PEAR/Horde/Kolab/Filter/Incoming.php:141
> /usr/share/php5/PEAR/Horde/Kolab/Filter/Base.php:132
> /usr/share/php5/PEAR/Horde/Kolab/Test/Filter.php:259
> /usr/share/php5/PEAR/test/Kolab_Filter/Horde/Kolab/Filter/ResourceTest.php:108
> /usr/share/php5/PEAR/test/Kolab_Filter/Horde/Kolab/Filter/AllTests.php:36
> /usr/share/php5/PEAR/test/Kolab_Filter/Horde/Kolab/Filter/AllTests.php:63
>
> The method that is called at line 78 and 108 in ReSourceTest.php is
> sendFixture.  I assume that this method uses a method that is available in
> both  /srv/www/htdocs/horde/lib and /usr/share/php5/PEAR (e.g. Horde/Util),
> but that one of them is different....  Which is a pity.  Is there an easy way
> to determine which methods are used (function trace)?  More about my horde
> installation below.
>
> I would assume that the preferred include_path is (as all kolab-* packages
> store their files in /usr/share/php5/PEAR):
>  ".:/usr/share/php5:/usr/share/php5/PEAR:/srv/www/htdocs/horde/lib"
> while I now must specify:
>  ".:/usr/share/php5:/srv/www/htdocs/horde/lib:/usr/share/php5/PEAR"
> to make sure that the above mentioned tests do not fail....

The correct path for Kolab_FreeBusy and Kolab_Filter should only be

/usr/share/php5

That is all.

For the Kolab web client it should be sufficient to use:

/srv/www/htdocs/horde/lib:/srv/www/htdocs/horde/pear

The web client brings all the require dependencies it needs within  
"lib" and "pear".

>
>
>> > What I would like to know is the following: are the following files
>> > that are provided by the big horde package:
>> > Horde/Kolab.php
>> > Horde/Kolab/Storage/IMAP/cclient.php
>> > Horde/Kolab/Storage/IMAP/pear.php
>> > Horde/Kolab/Storage/IMAP.php
>> > Horde/Kolab/Storage/IMAP/test.php
>> > Horde/Kolab/Storage/Session.php
>> > used at the moment?  They are not available via http://pear.horde.org
>> > AFAIC determine.  IOW is it okay to drop them from the big horde
>> > package?
>>
>> The IMAP library was moved from Kolab_Storage to Kolab_Server. So  
>> the  paths need to be Horde/Kolab/Server/IMAP/... This is provided  
>> within  the Kolab_Server package from pear.horde.org.
>
> okay.  I removed Horde/Kolab completely from my horde rpm.
>
>> Looks like you are using the unpatched horde-webmail-1.2.0 release.  
>>  This is plain Horde though and not the Kolab web client. It will  
>> not  be compatible with the Kolab server.
>
> I use the kolab-packages that you distribute via pear.horde.org.   
> Further do I
> only use horde for the kolab-server.  I have not started yet to work on the
> horde-webclient.  Is a patched horde-webclient also needed for the kolab-
> server (that is not using horde-webclient)?

No. The patched horde is not needed for the Kolab server to work.

But an unpatched horde will not work with the Kolab server.

Cheers,

Gunnar

>
> --
> Richard
>
> _______________________________________________
> Kolab-devel mailing list
> Kolab-devel at kolab.org
> https://kolab.org/mailman/listinfo/kolab-devel
>



-- 
______ http://kdab.com _______________ http://kolab-konsortium.com _

p at rdus Kolab work is funded in part by KDAB and the Kolab Konsortium

____ http://www.pardus.de _________________ http://gunnarwrobel.de _
E-mail : p at rdus.de                                 Dr. Gunnar Wrobel
Tel.   : +49 700 6245 0000                          Bundesstrasse 29
Fax    : +49 721 1513 52322                          D-20146 Hamburg
--------------------------------------------------------------------
    >> Mail at ease - Rent a kolab groupware server at p at rdus <<
--------------------------------------------------------------------


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digitale PGP-Unterschrift
URL: <http://lists.kolab.org/pipermail/devel/attachments/20090301/b9158ec1/attachment.sig>


More information about the devel mailing list