That didn't do the trick - it's more complicated than this. Nevertheless thanks for giving me a reason to assess $INFO vs. pageinfo()!
The content of $INFO differs. In my module's handle(...)
call, it's null. During render('metadata',...)
, it's null, also. Later on, during render('xhtml',...)
, it contains the address of the including page. This value seems to remain throughout the rest of following handle
's and renders()
's. So in any case, $INFO is useless to my module.
pageinfo()
, on the other hand, appears to deliver the ID of the page being handle
'd, which also yields the ID of the included page. This is good! But within render('xhtml',...)
, pageinfo()
delivers the ID of the including page - useless to my module.
I was not able to see through this, because I didn't expect different results depending on whether pageinfo()
is called within render
, or handle
. So I started this thread.
With this knowledge, though, I decided to pass the result of pageinfo()
given within my module's handle(...)
function into the array being returned (coming back to render(...)
as $data
. Now the ID of the included page is ready to be used within render(...)
, even though both $INFO, and pageinfo()
fail to give me the included page's ID.