Timeline for Where is the admin bar instantiated?
Current License: CC BY-SA 3.0
9 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Feb 27, 2018 at 20:43 | vote | accept | Nora McDougall-Collins | ||
Feb 27, 2018 at 20:43 | comment | added | Nora McDougall-Collins | This has been a very informative discussion. In the end, the problem was caused by a badly done subdomain redirect. A setup I was not privy to. But, this information helped my student rule out possible causes to the problem. This answered my question, but my question was not about the actual problem! | |
Feb 3, 2018 at 22:39 | history | edited | mmm | CC BY-SA 3.0 |
added 1656 characters in body
|
Feb 3, 2018 at 22:06 | comment | added | mmm | oh yes, I forget the frontend. I have edited my question to add the trace on the home page. | |
Feb 3, 2018 at 16:30 | comment | added | Nora McDougall-Collins | If I understand your comments correctly, I believe that my original question was not specific enough. What I didn't realize is that the admin bar may be called through a different path from the backend (Dashboard) than it is when it shows on the front end (Viewer side) when the viewer is logged in. | |
Feb 3, 2018 at 10:28 | comment | added | mmm | @janh it's totally that, I use php.net/debug_backtrace to find such paths. | |
Feb 3, 2018 at 0:44 | comment | added | janh |
@NoraMcDougall-Collins wp_footer is front end only, this was from the Backend. The relevant action here is in_admin_header which is the second item in the backtrace (wp-admin/admin-header.php:219 ). Can't speak for how mmm did it, but you yould hook into the admin_bar_init action and then use debug_backtrace to get the info.
|
|
Feb 3, 2018 at 0:07 | comment | added | Nora McDougall-Collins | How did you do that? And why doesn't the footer call show up? | |
Feb 2, 2018 at 22:36 | history | answered | mmm | CC BY-SA 3.0 |