Opened 8 years ago
Last modified 4 years ago
#30855 new defect (bug)
wp_get_update_data() calls are not pluggable
Reported by: |
|
Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | 4.1 |
Component: | Administration | Keywords: | |
Focuses: | Cc: |
Description
Up to 4.1 I was able to disable core, themes and plugin updates and related HTTP traffic.
In 4.1 new wp_get_update_data() calls are much like hardcoded than pluggable, I wasn't able to disable them all. Especially not the ones in wp-admin/menu.php
https://github.com/WordPress/WordPress/blob/master/wp-admin/menu.php#L33-L34
https://github.com/WordPress/WordPress/blob/master/wp-admin/menu.php#L183-L187
Could you make wp_get_update_data() calls pluggable? Or give me an advise to disable them?
My current workaround is to fiddle with the transients:
https://github.com/szepeviktor/wordpress-plugin-construction/blob/master/mu-disable-updates/disable-updates.php#L98
Thank you!
Change History (3)
This ticket was mentioned in Slack in #core by jorbin. View the logs.
8 years ago
#3
@
8 years ago
https://github.com/WordPress/WordPress/blob/master/wp-admin/menu.php#L31-L32
Here you can see that wp_get_update_data()
is executed without condition.
The only way to make it ineffective is to alter the transient's value.
Actually the transients could contain update data because my mu-plugin allows update by pushing the "Check again" button.
do the following filters in place already not work for this?