Bugs item #877082, was opened at 2004-01-14 20:52
Message generated for change (Comment added) made by ralfbecker
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=554338&aid=877082&group_id=78745
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: addressbook
Group: 1.0 release (closed / no more reports please)
Status: Closed
Resolution: None
Priority: 5
Submitted By: Thomas Weber (xorsf)
Assigned to: Raphael Derosso Pereira (raphaelpereira)
Summary: wrong field in ldap for mobile phone number
Initial Comment:
with ldap as backend for the addressbook, it uses
phpgwCellTelephoneNumber as Attribute to store a mobile
phone Number. This is fine if you only use eGW to
access the addressbook but it breaks other ldap aware
clients (like mozilla). Actually ldap and ldap access
via mozilla and other products is one of the main
reasons for me to use eGW.
The objectClass inetOrgPerson which is used by eGW
anyway, defines the Attribute mobile to store cell
phone numbers. Could this please be changed to behave
more standards conform?
you might wanna check http://ldap.akbkhome.com/ for an
nice ldap Schema Viewer.
Comment By: Ralf Becker (ralfbecker)
Message:
Logged In: YES
user_id=208526
Hi,
the eGroupWare development team has finished a new release: 1.2
We believe many of the reported bugs are fixed.
As we dont have the time to check all the open bugs, we close
them now and kindly ask you to re-check your bug-report with the
new release.
If you find your reported bug still exists in the new release
(1.2RC7), please reopen the bug-report.
Thanks for your understanding and we hope you enjoy using the new
release.
eGroupWare development team
Comment By: Thomas Weber (xorsf)
Message:
Logged In: YES
user_id=897642
well, the inetOrgPerson objectClass is probably older than 2
years (no offense intended).
I understand the upgrade path problem, but once 1.0 is
finally released, this will get even worse. A script to
convert from phpgwCellTelephoneNumber to mobile seems rather
trivial for me - except it will run quite some time for big
adressbooks. Maybe such a script and an interim fix (until
the next stable release) to use mobile and fall back to
phpgwCell* if mobile isn’t defined could be a doable way. So
users who don’t care about other clients wouldn’t even
notice and those who care could convert their database. For
the update to the next major release such a convert run
could be mandatory (i guess there’ll be other things to fix
as well). If I’d had the slightest clue about php I’d come
up with such a script myself - unfortunately I guess it has
to be php for the eGW project.
Once you’ve tried to use eGW for lookups in an ldap based
adressbook with more than say 500 entries, you’d understand
the need to make it standard conform so you can access the
data with other clients. Though it’s very nice to maintain
the data and as an access method if you have nothing but a
browser.
Comment By: Miles Lott (milosch)
Message:
Logged In: YES
user_id=228
Keep in mind that the ldap schema were written over 2 years
ago. A search was done at the time - it wasn’t created
without research. Hopefully, this can be updated soon. But
we do have to keep in mind those using *groupware with ldap
contacts, and provide an upgrade path for them. It had been
discussed also to maintain duplicate fields in ldap where
needed to work with multiple clients.
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=554338&aid=877082&group_id=78745
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
eGroupWare-tracker mailing list
eGroupWare-tracker@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/egroupware-tracker