https://bugzilla.wikimedia.org/show_bug.cgi?id=57512
--- Comment #5 from Bawolff (Brian Wolff) <[email protected]> --- > *When someone edits something else in the wiki (upload new version of a > photo, > delete a page [changing it to a redlink]), the page won't have its cache > purged > (I'm assuming that flow actually caches stuff, and that it hasn't totally > re-implemented its own version of linkstables or something crazy like that). > I was asked to elaborate on why I think this is a bad thing (Given that "Flow posts are meant to be accurate snapshots of a moment in time"). Failing to update flow posts when templates change (and other things that trigger RefreshLinksUpdates and HTMLCacheUpdate) would be bad because: *Users expect that this is how the wiki works. Imo this belief is very very strongly ingrained (heck, its related to where we derive the work "wiki" from), and users would probably not like it if things didn't update. (Obviously this is anecdotal. I have no data to back that assertion up, but I feel it to be true quite strongly) *In cases of vandalism. People using templates in flow posts well a template is vandalized, won't have their edits fixed when the template is fixed *Things being deleted - Person writes post, person b deletes template a month later, person re-edits their post a year later, suddenly template doesn't work = confusing. This is especially bad when combined with usage lists not working. Also without templates updated, notices that a template is up for deletion wouldn't show up on flow posts where the template is used. *Redlinks. People expect the redness of links to reflect reality instantly *Images (The following may change in some mythical future, how we currently handle images is not ideal): Person uses an image. A couple days later someone uploads a new version of the image that has different dimensions. Flow post would have the image squished (As the new image would get fitted to the old dimensions) *There's probably other things I haven't thought of. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
