[horde] address book lookup error

[Joe Fisher]

> -----Original Message-----
> From: horde-bounces at lists.horde.org [mailto:horde-
> bounces at lists.horde.org] On Behalf Of Michael Rubinsky
> Sent: Wednesday, July 23, 2008 12:31 AM
> To: horde at lists.horde.org
> Subject: Re: [horde] address book lookup error
> 
> Quoting Joe Fisher <Joe.Fisher at citylightsmedia.com>:
> 
> >
> >>>>
> >>>> > Thanks is this something which can be done in prefs, or
> something
> > I
> >>
> >>>> > need to edit in a file somewhere?
> >>>>
> >>>> Most likely the bad value resides in your preferences backend
> >> already.
> >>>>   So fix it there.
> >>>>
> >>>> michael
> >>>>
> >>>> --
> >>>> ___________________________________
> >>>> Michael Slusarz [slusarz at horde.org]
> >>>
> >>> May I ask what's a "preferences backend?"
> >>
> >> It's the backend data storage for preferences.  A sql database,
> files
> > on
> >> the filesystem, IMSP, basically whatever you configured for the
data
> >> storage in administration->setup->horde->preference system.  What
> >> Michael S. is saying is that the bad value is a stored user
> >> preference value as opposed to a default value that is contained in
> a
> > configuration
> >> file.
> >>
> >> Thanks,
> >> mike
> >>
> >> So, it turns out this has nothing to do with Address Book but is an
> >> issue that when I change the text editor from plain text to html is
> > when
> >> I get this error:
> >>
> >> Warning: array_search() [function.array-search
> >> <http://mydomain.com:2095/horde/imp/function.array-search> ]: Wrong
> >> datatype for second argument in
> >> /usr/local/cpanel/base/horde/lib/Horde/Editor/xinha.php on line 73
> >>
> >> I really would like to know how I can fix this so that I can use
> HTML
> >> editing in composing.
> >
> > And this is *exactly* what I previously told you - a problem with
> your
> > prefs.
> >
> > michael
> >
> > Sorry to belabor this item, but I would like to deploy HTML
composing
> > and currently I'm getting the error and all the pref files I checked
> > seem to be plain vanilla with no modifications so it's not clear
> where
> > one would change anything.
> 
> Your not listening to what we are saying.  The bad value is in the
> preference storage...where each individual user preference is stored,
> and *not* in any pref.php configuration file.  If your using a SQL
> database for storage, you need to nuke the value for this pref.
> 
> 
> Thanks,
> mike

Thanks Mike

It's happening for EVERY user which is why I was more focused on the
general prefs. Anyhow where would the individual prefs be stored
typically?

Joe