feat: auto-refresh NETWORK.md on multisite structural changes#882
Merged
feat: auto-refresh NETWORK.md on multisite structural changes#882
Conversation
Homeboy Results —
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
datamachine_regenerate_network_md()— same pattern as SITE.md (60s debounce via network transient,<!-- CUSTOM -->marker preservation,site_context_enabledcheck)datamachine_register_network_md_invalidation()with hooks for site lifecycle (wp_initialize_site,wp_delete_site), URL/name changes, plugin activations, and theme switchesbootstrap.phponinit— only fires on multisite installsFixes #881
Testing
Tested on extrachill.com production:
http://tohttps://afterwp option update)<!-- CUSTOM -->marker content survives regeneration