Re: 4.7.3 __IMAGE_DIR__ Variable Problem...

Quoting Stefan Hornburg (Racke) (racke@xxxxxxxxxx):
> Jon Jensen <jon@xxxxxxxxxx> writes:
> 
> > On Thu, 14 Jun 2001, Jon Jensen wrote:
> > 
> > > On 14 Jun 2001, Stefan Hornburg (Racke) wrote:
> > >
> > > > Very well spotted, John. Congratulations. Mangling Config stuff is
> > > > fine, because it is not persistent, but we shouldn't touch Variables
> > > > as it seems. Jon, why we need to set IMAGE_DIR in UI_STD_HEAD ?
> > >
> > > I can't remember why I set that originally. It doesn't seem to be
> > > necessary, so I took it out. John, let me know if that fixes your problem.
> > 
> > Now I remember why. The [button] usertag uses $Variable->{IMAGE_DIR} to
> > write image paths. So it's now broken in the UI. I'll see what I can do to
> > fix that.
> 
> Using IMAGE_DIR in a usertag is bogus IMHO. Why isn't $Config->{ImageDir}
> used in the first place ?
> 

I think it was done because it was to develop a directory name, not an
image path. Since the thing won't work unless $Variable->{DOCROOT} is 
set, I decided to make it consistent and read the setting from Variable
only instead of a combination. That way no one gets the idea it is a
core feature.....

-- 
Red Hat, Inc., 3005 Nichols Rd., Hamilton, OH  45013
phone +1.513.523.7621      <mheins@xxxxxxxxxx>

Being against torture ought to be sort of a bipartisan thing.
-- Karl Lehenbauer