[Tickets #2896] RESOLVED: sources.php IMSP bug fix
bugs@bugs.horde.org
bugs at bugs.horde.org
Thu Nov 3 12:29:33 PST 2005
DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.
Ticket URL: https://dev.horde.org/horde/whups/ticket/?id=2896
-----------------------------------------------------------------------
Ticket | 2896
Updated By | Michael Rubinsky <mrubinsk at horde.org>
Summary | sources.php IMSP bug fix
Queue | Turba
Version | 2.0.4
State | Bogus
Priority | 1. Low
Type | Bug
Owners |
-----------------------------------------------------------------------
Michael Rubinsky <mrubinsk at horde.org> (2005-11-03 12:29) wrote:
> I think I misunderstood something:
>
> the Turba's INSTALL document clearly states:
>
> .. Important:: Turba 2.0 requires version 3.0+ of the Horde Framework -
> earlier versions of Horde will **not** work.
The same document also states:
<pre>
Documentation on the format and purpose of those files can be found in
each
file. You may edit these files if you wish to customize Turba's
appearance
and behaviour. ** With the exception of the ``sources.php`` file the
defaults
will be correct for most sites.**
** You must configure ``sources.php`` to list your data sources (both SQL
and
LDAP if necessary). This configuration file contains a large number of
**examples**. Please remove or comment out those examples that **you
don't
need**.**
</pre>
(emphasis mine)
And in sources.php.dist:
<pre>
This file is where you specify the sources of contacts available to users
* at your installation. It contains a large number of EXAMPLES.
</pre>
and in the imsp example section:
<pre>
// Check that IMSP is configured in Horde but fall through if there is no
// configuration at all - in case we aren't using up to date Horde install.
// In that case, be sure to change the params array below to suit your
needs.
</pre>
I agree it might not have been clear enough as to what 'up to date' Horde
install meant and a change in the comments has been added to CVS to help
make this more clear.
> Nevertheless they are correct: I am no longer getting any messages in
> the error log, I checked. I even checked the contents of
> $GLOBALS['prefs'] using print_r -- with second argument, it's all
> there.
Can you provide me the print_r statement you are using and the line number
and file that you are calling it so I can see how IMSP configuration
settings are getting into the prefs - as I cannot reproduce this?
Thanks.
Mike
More information about the bugs
mailing list