Add ability to hook into generic CP page output production after session has started

[jcogs-design]

Add / amend EE so that either / or:

• the cp_end_js hook fires after the session is started (so member info can be accessed)
• add a hook with similar function to template_post_parse that fires when a CP page is generated

Either of these options would provide some mechanism to add dynamic elements to a generic CP page that could reflect (for example) the role / status of the member currently logged in: something that appears not to be possible currently.

• I am capable and would like to work on implementation of this feature if it is considered.

[intoeetive]

@jcogs-design It's been a while since this was requested, but I think we could add cp_boot hook similar to existing core_boot with the difference that it will be run after ee()->core->run_cp()

Do you think that will cover what you need here?

[jcogs-design]

To be honest I'm not aware of the core_boot hook - as mentioned in opening post what would work would be anything that allows a process to be run after the member status has been determined: the request came from a need to put a marker on a CP page depending on role of logged in member - currently the only way we found was to load a trigger element that fired a js process after template was constructed that ran an ajax job to determine current role and the insert html into page based on what that determined; a solution that is rather long-winded and would not work for some purposes. A better option would be something equivalent to template_post_parse for the CP HTML generation - so amendments / additions could be made based on logged in status etc.

[intoeetive]

So for this case, you actually need the hook to run after the views have been compiled (or at least fetched), so you could inject your own HTML there, is that correct?

With the cp_boot you'd be able to set variables to ee()->view or load JS with ee()->cp->add_js_script or add CSS to head with ee()->cp->add_to_head - but not modify the compiled view files, because that would be happening later on. But you would already know who's logged in

[jcogs-design]

OK - sounds like that might work.