Labels |
Added:
?
|
Category | ⇒ | Plugins |
As far as I understood, we can't revert this as it can create issues for users implementing "register_shutdown_function()" callbacks in extensions.
Another solution is required.
The reason it worked before #7279 is because of the order of shutdown of the various objects. The database driver's destructor would get called before the system plugin's destructor, and the database driver destructor calls a shutdown routine (usually $this->disconnect()
). In order to make the log data work again without reverting #7279 in the debug plugin you will need to call $db->disconnect()
before starting to get all the data out of the driver.
Reverting #7279 will send an implicit message that Joomla does not offer 100% feature support for cases where someone registers a custom shutdown function via register_shutdown_function()
. Logic like rendering the debug console should not be placed in a class destructor for this reason.
Status | New | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2015-11-12 18:34:37 |
Closed_By | ⇒ | zero-24 |
I can confirm this
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/8362.