| @@ -790,8 +790,15 @@ | ||
| 790 | 790 | * addresses that receive the alerts is another, and nobody presses a button |
| 791 | 791 | * called "restore defaults" expecting that. Both the Standard preset and the |
| 792 | 792 | * two reset buttons leave these alone. |
| 793 | 793 | * |
| 794 | + * Read from outside the plugin: the third-party network plugin Vigilante | |
| 795 | + * Network Sync calls this from its 2.0.3 to decide what NOT to copy between | |
| 796 | + * the sites of a network, so a key it does not know about is preserved per | |
| 797 | + * site instead of overwritten. Adding keys here is safe and helps it; | |
| 798 | + * renaming or removing the method, or changing the shape of what it returns, | |
| 799 | + * silently changes what that plugin replicates across a whole network. | |
| 800 | + * | |
| 794 | 801 | * @since 2.9.8 |
| 795 | 802 | * |
| 796 | 803 | * @return array<string,string[]> |
| 797 | 804 | */ |
| @@ -854,8 +861,12 @@ | ||
| 854 | 861 | * administrator can approve, so a main-site administrator without network |
| 855 | 862 | * rights must not be able to silence it by turning either one off. Closing |
| 856 | 863 | * the ignore list and the clear-results button in 2.11.8 left these two as |
| 857 | 864 | * the remaining routes; found by the audit of the admin surface. |
| 865 | + * | |
| 866 | + * Since 3.0.0 the self-check has no setting at all, so there is nothing to lock: Vigilant's own | |
| 867 | + * files are shared by every site, and on the main site the self-check is | |
| 868 | + * the one that reports a change to them for the whole network. | |
| 858 | 869 | * |
| 859 | 870 | * On a subsite all of them only act on that site, so they stay editable |
| 860 | 871 | * there (get_locked_file_settings() adds this set only when owns_shared_files()). |
| 861 | 872 | * |
