| Summary | custom hook support for backend selection |
| Queue | Passwd |
| Queue Version | 3.0 |
| Type | Enhancement |
| State | Rejected |
| Priority | 1. Low |
| Owners | |
| Requester | srrafa (at) usc (dot) es |
| Created | 04/24/2006 (748 days ago) |
| Due | |
| Updated | 05/26/2006 (716 days ago) |
| Assigned | 05/03/2006 (739 days ago) |
| Resolved | 05/26/2006 (716 days ago) |
| Attachments | passwd.patch[1].tgz ![]() hooks.php.dist ![]() |
| Milestone | |
| Patch | 1 |
I guess that, as inticket #3701, the same applies here. I''ll move this functionality to backends.phpState ⇒ Feedback
Taken from
The patch to Passwd.php at least has some formatting issues. Also, I have the same question as for the Ingo ticket - why can't this just be done inside the backends.php file?New Attachment: hooks.php.dist
An example for hooks.php.distNew Attachment: passwd.patch[1].tgz
Here's an updated version of the parch following the guidelines in
ticket #3701.The hook is renamed to _passwd_hook_backend_select
Note that this hook does not return the full structure of a backend like _ingo_hook_backend_select does. It returns the key in the array that leads to the backend structure.
I made it that way because main.php works on keys and I didn't want to make the patch too intrusive
Queue ⇒ Passwd
State ⇒ New
New Attachment: passwd.patch.tgz
Priority ⇒ 1. Low
Summary ⇒ custom hook support for backend selection
Type ⇒ Enhancement
The attached file contains patches against passwd-h3-30
main.php.patch for main.php
conf.xml.patch for config/conf.xml
Passwd.php.patch for lib/Passwd.php
They add suport for one custom hook for backend Selection (_passwd_hook_selectBackendKey)