When a hub feature is created, there are two steps: (a) creating the subpage and (b) "transcluding" it on the hub. However, because the second step happens first, the cache is saved referring to a non-existent subpage, with a subpage created immediately after. This leads to a confusing interface.
Since users can do step (b) by hand and *then* create the feature, I think the system should consistently purge cache when new features are created to avoid the confusion.
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Switching hub feature edit order and adding purge button | mediawiki/extensions/CollaborationKit | master | +70 -62 |
Consensus from discussion on IRC:
Change 343801 had a related patch set uploaded (by Harej):
[mediawiki/extensions/CollaborationKit] Switching hub feature edit order and adding purge button
Change 343801 merged by jenkins-bot:
[mediawiki/extensions/CollaborationKit@master] Switching hub feature edit order and adding purge button
Noting for posterity: This patch also fixed T160937, which was caused by Spam Blacklist not being able to parse the non-existent members subpage, transcluded on the hub, before the hub was saved. (Filtering against spam blacklist happens after the save button is pressed but before the page is saved.) Thank you to @Catrope for identifying this.