[geeklog-devtalk] lib-custom and the include location in lib-common

[Vincent Furia]

I think moving the include of lib-custom.php to the bottom of
lib-common.php is a good idea.  Since you can still set cookies at
that point, I don' t see a need for a two lib-custom.php files
(pre-/post-).

-Vinny


On Tue, 29 Mar 2005 12:22:37 -0500, Blaine Lang <geeklog at langfamily.ca> wrote:

>  

> I was wondering about the location for the inclusion of lib-custom.php at

> the top of lib-common. We have the inclusion of all plugins functions at the

> end of lib-common.php. This means that any code in lib-custom can not use

> plugin functions unless they are called only after lib-common has completed

> executing. 

>   

> Additionally, lib-custom is called before $_USER is initialized so code can

> not use $_USER either (unless it's called after lib-common completes) 

>   

> There is a need to have code in lib-custom execute before any initializtion

> of $_USER (and the main user session) - and believe thats why it's called

> where it is now. 

> 

> Is there not a need for both - a Pre-Initialize and Post Initialize

> lib-custom. 

>   

> Comments? 

>   

> Blaine 

>   

>