1 |
============================================================== |
2 |
patch "utf8" |
3 |
============================================================== |
4 |
target: |
5 |
- patch turba to make umlauts (ä, ö, ü) possible |
6 |
|
7 |
todo: |
8 |
- values stored to ldap should be utf-8 encoded |
9 |
|
10 |
modified files: |
11 |
- horde/turba/lib/Driver/ldap.php (patch is "ldap.php.patch-utf8") |
12 |
|
13 |
|
14 |
============================================================== |
15 |
patch "mapping" |
16 |
============================================================== |
17 |
target: |
18 |
- enhanced mapping of outlook-fields to ldap-fields with horde/turba-import |
19 |
|
20 |
facts are: (not necessary related to "todo") |
21 |
- name (cn) and surename (sn) are required fields |
22 |
- givenname (givenname) is optional |
23 |
- givenname/callname/Rufname is not supplied by outlook 2000 |
24 |
- title/Titel is not supplied by outlook express 5 |
25 |
|
26 |
todo: |
27 |
- map csv-Field "nachname" to Turba-Field "surname" |
28 |
- map csv-Field "vorname" to Turba-Field "givenname" |
29 |
- express Turba-Field "name" as (e.g.) a concatenation, like: |
30 |
name = givenname + surename |
31 |
which could be represented (internally) as |
32 |
expr: {First Name} + " " + {Last Name} (outlook 2000 en) |
33 |
expr: {Vorname} + " " + {Nachname} (outlook 2000 de) |
34 |
|
35 |
done: |
36 |
- multiple usage of fields when mapping csv-Columns to Turba-Fields |
37 |
- removed "null"ing of option-elements from csvmap.inc's JavaScript-Code |
38 |
- introduced virtual fields with expressable values (attention!!! may have side effects!!!) |
39 |
- unavailable keys found in expression will by silently ignored (filled with '', when concatenating) |
40 |
- no further error-handling (sorry) |
41 |
- enhanced error-detection and -notification for general import by $driver->addObject($obj) (in our case the LDAP-driver) |
42 |
- various LDAP-errors trapped since then (caused by development): |
43 |
- Failed to add an object: [68] "Already exists" (attributes: [a:4:{s:2:"cn";s:11:"Name-First ";s:2:"sn";s:9:"Name-Last";s:9:"givenname";s:10:"Name-First";s:11:"objectclass";s:13:"inetOrgPerson";}]). |
44 |
- Failed to add an object: [34] "Invalid DN syntax" (attributes: [a:2:{s:2:"cn";s:32:"{First Name} + " " + {Last Name}";s:11:"objectclass";s:13:"inetOrgPerson";}]). |
45 |
- Failed to add an object: [65] "Object class violation" (attributes: [a:2:{s:2:"cn";s:32:"{First Name} . " " . {Last Name}";s:11:"objectclass";s:13:"inetOrgPerson";}]). |
46 |
|
47 |
modified files: |
48 |
- horde/turba/data.php (patch is "turba_data.php.patch-mapping") |
49 |
- horde/templates/data/csvmap.inc (patch is "templates_data_csvmap.inc.patch-mapping") |
50 |
|
51 |
|
52 |
============================================================== |
53 |
patch "actions-in-list" |
54 |
============================================================== |
55 |
target: |
56 |
- add actions (links, buttons) to each entry in "Adress Book Listing" (Browse) |
57 |
- with "actions" i mean links to "edit" or "delete" an entry directly from this list |
58 |
|
59 |
todo: |
60 |
- implement it ;) |
61 |
|
62 |
done: |
63 |
- functionality for reaching main target was pretty simple |
64 |
- I discovered that after e.g. a deleteobject-action we found ourselves back on the "search.php" - page |
65 |
which i found very inconvenient. Now you will be redirected to "where you came from" by using the |
66 |
$_SERVER["HTTP_REFERER"] - variable. |
67 |
|
68 |
modified files: |
69 |
- horde/turba/templates/search/row.inc (patch is "turba_search_row.inc.patch-actions-in-list") |
70 |
- horde/turba/deleteobject.php (patch is "turba_deleteobject.php.patch-actions-in-list") |
71 |
|
72 |
|
73 |
============================================================== |
74 |
patch "mapping-loadsave" |
75 |
============================================================== |
76 |
target: |
77 |
- load/save, im-/export mapping |
78 |
|
79 |
todo: |
80 |
- simple version: copy/paste from/to textarea |
81 |
- advanced version: up-/download file |
82 |
- use wddx as data-encapsulation instead of rolling our own ("|", " <=> ", ...) |
83 |
|
84 |
done: |
85 |
- implemented simple version with own data-encapsulation |
86 |
|
87 |
modified files: |
88 |
- horde/templates/data/csvmap.inc (patch is "templates_data_csvmap.inc.patch-mapping-loadsave") |
89 |
(attention!!! this patch is an "accumulative" one, |
90 |
"templates_data_csvmap.inc.patch-mapping" is required before applying this one) |
91 |
|
92 |
|
93 |
============================================================== |
94 |
patch "mapping-expressionbuilder" |
95 |
============================================================== |
96 |
target: |
97 |
- better "add virtual field"-interface |
98 |
- hidden - then visible - layer with better (more integrated) gui |
99 |
- "build expression by click & select" |
100 |
|
101 |
done: |
102 |
- that's what i wanted to have as a more comfortable way of editing expressions (more to come) ... ;) |
103 |
|
104 |
modified files: |
105 |
- horde/templates/data/csvmap.inc (patch is "templates_data_csvmap.inc.patch-mapping-expressionbuilder") |
106 |
(attention!!! this patch is an "accumulative" one, |
107 |
"templates_data_csvmap.inc.patch-mapping-loadsave" is required before applying this one) |
108 |
|
109 |
|
110 |
============================================================== |
111 |
patch "utf8-import" |
112 |
============================================================== |
113 |
target: |
114 |
- bugfix: no utf8 conversion when importing |
115 |
|
116 |
todo: |
117 |
- fix this!!! |
118 |
|
119 |
modified files: |
120 |
- horde/turba/lib/Driver/ldap.php (patch is "ldap.php.patch-utf8-import") |
121 |
(attention!!! this patch is an "accumulative" one, |
122 |
"ldap.php.patch-utf8" is required before applying this one) |
123 |
|
124 |
|
125 |
============================================================== |
126 |
things to keep in mind: |
127 |
|
128 |
ideas-horde/turba: |
129 |
- are fine-grained-permissions (add/modify/delete per object *and* user (kinda ACLs) ) possible or already implemented? |
130 |
- perhaps even more? operating on field-level? (per field per object per user???) ;) |
131 |
- e.g. a person allows a group of persons to modify a certain (address)-entry, |
132 |
but they should not be able to change the original owner (field), or maybe others, too |
133 |
|
134 |
ideas-general: |
135 |
- publishing? TWiki? |
136 |
- security/auth? Kerberos? |
137 |
- revisioning LDAP-data? (internal/external/none/via replication/hmmm.....?) |
138 |
|