[imp] expand names (fwd)
Apis Hytt
php3dev@carousel.tabcat.com
Mon, 25 Jun 2001 00:11:22 -0500 (CDT)
I resend mail..
---------- Forwarded message ----------
Date: Sun, 24 Jun 2001 23:56:43 -0500 (CDT)
Subject: Re: [imp] expand names
On Mon, 25 Jun 2001, Chuck Hagenbuch wrote:
> Quoting Sam Przyswa <samp@arial-concept.com>:
>
> > My problem it's the expand name don't work I got :
> >
APIS+
Solaris7 Apache-cvs, php-cvs, horde-cvs, imp-cvs, turba-cvs etc
I have been trying various combos of prefs lock/share and
whatevers...
I tried to see what might be possible troubles *if* this had
been done at site (maybe above?):
Scenario -- allow `expand names' in [compose]
but not have [turba] in horde bottom navbar.
config: remove `turba' from horde/config/registry.php .. as
there is no option in each registry module defines
to *not* display the module in the navbar *but*
still retain the expand name and [prefs] addressbook
preferences.
One will now have errors in expand names and in turba and prefs
for addressbook as the needed turba arrays are not around.
... but the turba is indeed gone from nabvar, of course.
So .. if one wants to *not* have any module in the navbar
and still to use the new
module/lib/api.php functions .. things break such
as expand names in [compose] and prefs addressbooks.
Possible solution?
Maybe have a new define in registry for each module
to show module name in navbar or not as site
likes.
That would allow one to have the backdoor, inter-module
api functions, but not display the module in
navbar. Sites that just want turba lookups for
expand names, but don't allow users to manage
in turba can have the brass-ring, then.
Similar for nag where site might generate tasks into
the store engine, but not want users to have
hands-on nag in navbar .. but use the new
nag api Login check status/event report.
APIS-
NNNN