6.0.0-beta1
▾
Tasks
New Task
Search
Photos
Wiki
▾
Tickets
New Ticket
Search
dev.horde.org
Toggle Alerts Log
Help
8/2/25
H
istory
A
ttachments
C
omment
W
atch
Download
Comment on [#6517] Export to ldif - data has no cn attribute
*
Your Email Address
*
Spam protection
Enter the letters below:
.__ \ / .. ,.__ [ __ >< | \./ [ __ [_.// \\__| | [_./
Comment
>> What about when sources.php has a more complex definition of 'name'? > > > > I saw this definition, but why there is no attribute key 'name' > available in the parameter $data of Horde_Data_ldif::exportFile? I > used also the lib/tests/ldif_exportFile.phpt testscript. The testdata > always containing a 'name' key - my real data not. > > > > In my unterstanding the config/source.php definitions are currently > not used in lib/Data/ldif.php and i think, the 'name' attribute > should be available before calling > > > > $ldif->exportFile(_("contacts.ldif"), $data, true); > > > > in data.php. My patch is only a workaround. With this patch, I can > see the correct names in Thunderbird with the import Turba > addressbook data. I created some screenshots from the imported Horde > data in Thunderbird, see > > > > http://www.linuxhacker.at/bugs/all/horde-turba-export-in-ldif > > > > I write the data array to the logfile before i calling exportFile in > data.php: > > > > [15] => Array > > ( > > [firstname] => Straub > > [lastname] => Herbert > > [middlenames] => > > [namePrefix] => > > [nameSuffix] => > > [alias] => > > [birthday] => > > [homeStreet] => > > [homePOBox] => > > [homeCity] => > > [homeProvince] => > > [homePostalCode] => > > [homeCountry] => > > [workStreet] => > > [workPOBox] => > > [workCity] => > > [workProvince] => > > [workPostalCode] => > > [workCountry] => > > [timezone] => > > [email] => herbert@linuxhacker.at > > [homePhone] => > > [workPhone] => > > [cellPhone] => > > [fax] => > > [pager] => > > [title] => > > [role] => > > [company] => , > > [category] => > > [notes] => undefined > > [website] => > > [freebusyUrl] => > > [pgpPublicKey] => > > [smimePublicKey] => > > ) > > > > Should the fix be implemented in the export routine or in another place?
Attachment
Watch this ticket
N
ew Ticket
M
y Tickets
S
earch
Q
uery Builder
R
eports
Saved Queries
Open Bugs
Bugs waiting for Feedback
Open Bugs in Releases
Open Enhancements
Enhancements waiting for Feedback
Bugs with Patches
Enhancements with Patches
Release Showstoppers
Stalled Tickets
New Tickets
Horde 5 Showstoppers