Markers
Table of Contents
| Horde/Ldap/Entry.php | 2 |
| Horde/Ldap/Filter.php | 1 |
| Horde/Ldap/Ldif.php | 19 |
| Horde/Ldap/Search.php | 3 |
| Horde/Ldap/Util.php | 11 |
| Horde/Ldap.php | 6 |
Entry.php
| Type | Line | Description |
|---|---|---|
| TODO | 248 | expect utf-8 data. Please note that special characters (eg german umlauts) should be encoded using utf8_encode(). You may use {@link} for properly encoding of the DN. |
| TODO | 629 | Entry rename with a DN containing special characters needs testing! |
Filter.php
| Type | Line | Description |
|---|---|---|
| TODO | 310 | Leaf-mode: Do we need to escape at all? what about *-chars? Check for the need of encoding values, tackle problems (see code comments). |
Ldif.php
| Type | Line | Description |
|---|---|---|
| TODO | 182 | checks on mode possible? |
| TODO | 305 | consider DN add! |
| TODO | 321 | What if the entry has attribute changes as well? |
| TODO | 511 | Is this the job of the LDAP-client or the server? |
| TODO | 599 | Known bug: Wrappings for comments are okay |
| TODO | 182 | checks on mode possible? |
| TODO | 305 | consider DN add! |
| TODO | 321 | What if the entry has attribute changes as well? |
| TODO | 511 | Is this the job of the LDAP-client or the server? |
| TODO | 599 | Known bug: Wrappings for comments are okay |
| TODO | 182 | checks on mode possible? |
| TODO | 305 | consider DN add! |
| TODO | 321 | What if the entry has attribute changes as well? |
| TODO | 511 | Is this the job of the LDAP-client or the server? |
| TODO | 599 | Known bug: Wrappings for comments are okay |
| TODO | 40 | LDAPv3 controls are not implemented yet |
| TODO | 259 | Implement operations on whole entries (adding a whole entry). |
| TODO | 480 | what about file inclusions and urls? "jpegphoto:< file:///usr/local/directory/photos/fiona.jpg" |
| TODO | 709 | I am not sure, if the UTF8 stuff is correctly handled right now |
Search.php
| Type | Line | Description |
|---|---|---|
| TODO | 212 | what about server side sorting as specified in http://www.ietf.org/rfc/rfc2891.txt? |
| TODO | 212 | Nuke evil eval(). |
| TODO | 298 | Entry object construction could be faster. Maybe we could use one of the factories instead of fetching the entry again. |
Util.php
| Type | Line | Description |
|---|---|---|
| TODO | 110 | nuke code duplication |
| TODO | 404 | if the value is already correctly escaped, we get |
| TODO | 601 | To solve this, we might ask the schema. The |
| TODO | 110 | nuke code duplication |
| TODO | 404 | if the value is already correctly escaped, we get |
| TODO | 601 | To solve this, we might ask the schema. The |
| TODO | 110 | nuke code duplication |
| TODO | 404 | if the value is already correctly escaped, we get |
| TODO | 601 | To solve this, we might ask the schema. The |
| TODO | 77 | implement BER |
| TODO | 77 | replace preg_replace() callbacks. |
Ldap.php
| Type | Line | Description |
|---|---|---|
| TODO | 798 | implement search controls (sorting etc) |
| TODO | 1014 | Checking via the rootDSE takes much time - why? fetching and instanciation is quick! |
| TODO | 1109 | Maybe a check against the schema should be done to be sure the attribute type exists. |
| TODO | 1433 | Remove this and expect all data to be UTF-8. Encodes given attributes to UTF8 if needed by schema. This function takes attributes in an array and then checks against the schema if they need UTF8 encoding. If that is the case, they will be encoded. An encoded array will be returned and can be used for adding or modifying. $attributes is expected to be an array with keys describing the attribute names and the values as the value of this attribute: <code>$attributes = array('cn' => 'foo', 'attr2' => array('mv1', 'mv2'));</code> |
| TODO | 1453 | Remove this and expect all data to be UTF-8. Decodes the given attribute values if needed by schema $attributes is expected to be an array with keys describing the attribute names and the values as the value of this attribute: <code>$attributes = array('cn' => 'foo', 'attr2' => array('mv1', 'mv2'));</code> |
| TODO | 1469 | Remove this and expect all data to be UTF-8. Encodes or decodes attribute values if needed |