Timeline for How can I allow core, plugin, theme update checks only for selected admins?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 31, 2018 at 14:24 | comment | added | lkraav | It does make sense to say "update checks should be enabled per-user". Admin page load speed is of great importance on our platform, since multiple people work on content and content configuration, but have no business updating anything. Update checks to a large number of plugins, when it triggers, significantly slows perceived admin page load speed. Plugin set is already linted and only business critical things are in action. | |
| Jan 31, 2018 at 14:21 | history | edited | lkraav | CC BY-SA 3.0 |
Clarified notifications vs checks
|
| Jan 31, 2018 at 8:06 | answer | added | Stefano Tombolini | timeline score: 4 | |
| Jan 31, 2018 at 6:07 | comment | added | Jacob Peattie | WordPress checks for updates for itself, it doesn't really make sense to say that update checks should be disabled per-user. Do you mean notifications, or the ability to update? | |
| Jan 31, 2018 at 6:07 | comment | added | Mark Kaplun | +1 but I do not think you are asking the right question. You are probably more interested in the notifications not displaying, and/or some admins not being able to update | |
| Jan 31, 2018 at 6:01 | history | asked | lkraav | CC BY-SA 3.0 |