[horde] ok..... what now....

[Rick Kukiela]

you know what, im a crack head, i didnt put that in there... what i did was,
the part causing the error was because it was parcing the uid for an @ sign,
so what i did was encase that command set in an if statement like so,

if(ereg("\@", $uid)) {
-- codeblock causing error --
}

----- Original Message ----- 
From: "Eric Rostetter" <eric.rostetter at physics.utexas.edu>
To: <horde at lists.horde.org>
Sent: Monday, June 16, 2003 4:03 PM
Subject: Re: [horde] ok..... what now....


> Quoting Rick Kukiela <horde at tech-nine.net>:
>
> > I got that error to go away that was refering to turba by adding a
> > require("config/conf.php"); in that turba file that was having the
> > problem...
>
> That should not be needed, and it is probably masking an error somewhere
> else.
>
> > I also figured out that when i was going through the registry
origionally,
> > the [pim] section i had marked as in active rather than header so it
wasnt
> > showing up on the menu.
>
> That would be a correct problem/solution set.
>
> --
> Eric Rostetter
> The Department of Physics
> The University of Texas at Austin
>
> Why get even? Get odd!
>
> -- 
> Horde mailing list
> Frequently Asked Questions: http://horde.org/faq/
> To unsubscribe, mail: horde-unsubscribe at lists.horde.org