> Would it fulfill your requirements doing it the other way round,
> by calling your outside applications via
>
> include("/path/to/application.php");
>
facing simillar problem I found that you cannot use this syntax if
your "application.php" uses header generating procedures (cookies, session
etc.) because your style will produce headers first.. or ypu have to make
code-inits to every such page. I just made special midgard pages like, say,
"topbar" including some midgard action and incldue them
within "application.php" by
include ("http://olga.pl/specials/topbar.php";);
what gives me my layout from midgard style, but right
after "application.php" sent headers. Disadvantage is that such include
produce unnecessary log entries.
Solt
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
