https://bugzilla.wikimedia.org/show_bug.cgi?id=64685
--- Comment #5 from Gilles Dubuc <[email protected]> --- OK, I think I've figured it out. Basically that caching was introduced and it has a couple of limitations, which I don't think we can avoid: The link between the campaign and the templates it uses will only be created if you create or save the campaign while the template exists. If you create the campaign before the templates it references, the connection won't be made and subsequent updates to the template won't get picked up. The workaround is to re-save the campaign once you've created the template. That create the link between the two and any subsequent update of the template will update the campaign. Secondly, the parent template (in this case https://commons.wikimedia.org/w/index.php?title=Template:Wiki_Loves_Earth_is_running ) needs to be saved in order for the update to trickle down to the template. That's a single save to update all the campaigns though. This is what you used to have, right? Lastly, the update that trickles down to the campaigns runs through a job, so it won't be immediate. I don't know what the job queue on Commons is usually like, but it could be seconds, minutes, or hours depending on the job queue at the time of the template update. Does that all make sense? I imagine you either ran into the red link issue (referencing templates before they exist) or the fact that the update is asynchronous. As for this caching, I imagine it was introduced for performance reasons. -- 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
