Re: Module variables being set late

[Mark . Burgess]

On  7 Jan, Chip Seraphine wrote:
> 
> I am running a module at the top of my actionsequence, and it sets a class 
> ("foo").  Foo *is* an AddInstallable class.
> 
> Unfortunately, the module runs only *after* everything else in the 
> actionsequence, even though it is the first item on the list.  (I'm not sure, 
> but I believe that this is new behavior in 2.1; the problems this behavior is 
> causing did not exist prior to that.)  This is causing the "foo" class to not 
> be set until too late to do any good.
> 
> I've tried running the module the old-style way (with "module:modname.foo"), 
> but that did not cause it run a the desired time.
> 
> Any ideas?  Any way I can for the modules to run at the beginning of the 
> first 
> passs, which what I really need it to do?



This is factually incorrect. The modules are run in the correct place
in the actionsequence. Whether or not the variables are "received" by
the actions is a different issue. You need to tell us exactly what
you are doing.

M

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Work: +47 22453272            Email:  Mark.Burgess@iu.hio.no
Fax : +47 22453205            WWW  :  http://www.iu.hio.no/~mark
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~