I hate to bump on the list, but I haven't even heard back a "this isn't
implemented/possible" response yet.
I've spent the last month trying to find any way to hack up
htdocs/add_value.php or something, seeing if I could figure out some way
to force the "Modify Entry" window to display all template described
attributes in the same way as they're displayed in "Create Object"
window. I know jack about PHP and can only make generalized guesses
about what codes running where and when and what it's doing.
So out of desperation I tried redesigning my Create template so that
each attribute definition has a "<value>---</value>" line in it. Sorta
like this:
<attribute id="mail">
<display>Email</display>
<value>---</value>
<icon>images/mail.png</icon>
<order>5</order>
</attribute>
The hope is that, horrible as it is, a contact entry could have all it's
possible attributes pre-loaded with "default" values. Essentially
non-data that would force the ldap object to present editable text
fields in the "Modify Entry" window for all attributes.
This just ended up revealing what seems to be a bug in 1.1.0.5. At ldap
object creation time, for attributes that are inherited down into the
mozillaAbPersonAlpha schema from above, the <value></value> template
parameter seems to cause DOUBLE fields for the attribute to appear, one
pre-populated with "---" and another empty. For example: givenname, cn,
sn, mail, telephoneNumber, fax and so on all had two text fields.
For attributes defined explicitly inside the mozillaAbPersonAlpha
schema, things worked as expected, with a single text field for the
attribute, pre-populated with "---". For example: nsAIMid,
mozillaHomeStreet, mozillaHomeStreet2 and so on all had one text field
like it should.
In short, even my desperate attempt to work *for* phpldapadmin, rather
than it working for me, blows up in my face.
If there's any one out there that understands what I'm trying to do,
thinks they know what might work, or at the very very least knows I'm
hosed, please let me know. Heck, I'm itching to post my schema,
templates, configs the whole shebang here. But that's a huge mess of
text to flood the list with if it's all for naught.
Honestly, even a "No. You cant do this, so shut up" would alleviate a
modicum of my frustration at this point.
Yennix S. Gantriean wrote:
> Greetings,
>
> I've been setting up a local LDAP server to function as my centralized
> address book. One of the features I've put in place is address book
> entry via phpldapadmin.
>
> I'm currently using phpldapadmin 1.1.0.5 on PHP Version 5.2.8-pl1-gentoo
> with openldap Version 2.3.43 and apache version 2.2.9-r1
>
> I have a customized set of create and modify templates that are used for
> address book entries. They're built to containing the full list of
> attributes I've built out for my address system.
>
> Here's the hitch. When I create an address entry all of the possible
> attributes are listed, and they each have a blank field in which I can
> type their values. Pretty simple.
>
> But when I want to modify a preexisting address book entry, any
> currently empty attribute value requires that I have to
> 1) Click on the contact I want to edit and be taken to the
> "Modify Entry" window
> 2) press "add value" on the attribute I wish to add to the contact
> 3) be taken to the "Add new XXX Value To YYY" window
> 4) type in my value
> 5) click "Add New Value"
> 6) be taken to the "Do you want to make these changes?" window
> 7) click "commit"
> before the addition I want to make is finalized.
>
> Whats more, if I have a set of updates I want to do on one contact, such
> as adding a new telephone entry and a postal code, I have to repeat
> steps 2-7 twice, for a depressingly grand total of 12 steps before I've
> finished with my update.
>
> Is there some way to cause the the "Modify Entry" window to populate
> blank fields for all empty attributes, so that new additions can be
> carried out in a simple single step (ala create entry?
>
> In short, can the "Modify Entry" window be made to work exactly like the
> "Create Entry" window, except with previously entered data being
> pre-populated in the attribute fields?
>
> I've found an old feature request here:
> http://sourceforge.net/tracker/index.php?func=detail&aid=1809456&group_id=61828&atid=498549
> It's basically asking the same question. I wasn't able to find any
> response to it though.
>
>
>
>
--
P.S. Please note my e-mail address has changed from [email protected] to
[email protected] The old address will still work, but is unstable,
please update your contacts with this new one:)
Just another synaptic miss fire somewhere in the mind of...
Yennix Siran Gantriean
------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
phpldapadmin-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/phpldapadmin-users
