Global overloading in advanced-cache.php
-
This plugin creates “advanced-cache.php” file in the content directory.
Jorbin writes in “Development P2 Blog”:
As a part of the 4.6 release, a change is made to the order of loading files during the bootstrap process. This change included an attempt to protect sites from the overloading of the hook related globals in advanced-cache.php. This change was reverted with [38251]. This means that the 4.5 behavior where if an advanced-cache.php sets one of the globals to an empty array, previously entered records will not exist.
This is a general reminder to not directly touch the globals in WordPress and to always use API functions. The format that the globals are in is not guaranteed to stay consistent from version to version. If you need to interact with the Plugins API in advanced-cache.php, as of 4.6, you can use the Plugins API (add_action(),
He further goes on to say:
This file lives in your wp-content directory as a peer to plugins and themes. Updates to it are not made like updates to plugins. You will never see a notice that there is an update pending. If you did not write this code yourself, you are encouraged to keep up to date with upstream updates.
In simple terms, what am I supposed to do with this file? Nothing? Leave it alone? Update it? If so, how?
The topic ‘Global overloading in advanced-cache.php’ is closed to new replies.