Template talk:VideoGallery: Difference between revisions

Line 4: Line 4:
:I understand page caching a lot better now than I did. MediaWiki has really good documentation about everything, it turns out, it just might be a bit buried where it's at. Pages are processed in a [https://www.mediawiki.org/wiki/Manual:Job_queue job queue] wherein any pages using templates/images/etc that were edited, or any categories that need to be updated, are added to a big stack and processed one at a time. The default setting is per 1 page load from a visitor to the site, 1 task on the top of the job queue is processed, but this can be changed in server configuration. Pages are given an automatic "expiry" time when they're cached, so a page that's not edited and has no templates for example should still be added to the job queue occasionally, just on a more periodic basis. You can see this refresh date and a lot of other miscellaneous cache info like performance statistics by [https://i.gyazo.com/3278f0e25c5be52a7e40ea46b8b89bf5.png viewing the page source] for different wiki pages in your browser. Basically as I see it, all game pages are already being added to the job queue at least once a day and reprocessed because of {{tl|CurrentGitRevision}}. Even making all the site's templates faster/slower doesn't affect the job queue because the tasks are processed depending on page loads and don't actually continuously run in the background unless explicitly told to do so. Short of rewriting the template completely to not have random elements, there's nothing that can be done to fix this from the user side. That's why I held off on touching this at all. - [[User:Xerxes|Xerxes]] ([[User talk:Xerxes|talk]]) 10:33, 27 September 2017 (CEST)
:I understand page caching a lot better now than I did. MediaWiki has really good documentation about everything, it turns out, it just might be a bit buried where it's at. Pages are processed in a [https://www.mediawiki.org/wiki/Manual:Job_queue job queue] wherein any pages using templates/images/etc that were edited, or any categories that need to be updated, are added to a big stack and processed one at a time. The default setting is per 1 page load from a visitor to the site, 1 task on the top of the job queue is processed, but this can be changed in server configuration. Pages are given an automatic "expiry" time when they're cached, so a page that's not edited and has no templates for example should still be added to the job queue occasionally, just on a more periodic basis. You can see this refresh date and a lot of other miscellaneous cache info like performance statistics by [https://i.gyazo.com/3278f0e25c5be52a7e40ea46b8b89bf5.png viewing the page source] for different wiki pages in your browser. Basically as I see it, all game pages are already being added to the job queue at least once a day and reprocessed because of {{tl|CurrentGitRevision}}. Even making all the site's templates faster/slower doesn't affect the job queue because the tasks are processed depending on page loads and don't actually continuously run in the background unless explicitly told to do so. Short of rewriting the template completely to not have random elements, there's nothing that can be done to fix this from the user side. That's why I held off on touching this at all. - [[User:Xerxes|Xerxes]] ([[User talk:Xerxes|talk]]) 10:33, 27 September 2017 (CEST)


:: Thanks for the further explanation around caching. And yeah, I'm not clear there is a lot we can do in the pure wiki. Admins can revise the site JavaScript and had thought some script running on a list of links could likely resolve this more cleanly. Though I think I'd forgotten about an aspect you brought up, in that the regular version updates force page refreshes. I wasn't clear that those sorts of refreshes updated the video order, if they do this is less of a concern; though preventing the user edit's trying to game the system (even if their "fixes" reset the next day) would probably be for the best. [[User:Kolano|Kolano]] ([[User talk:Kolano|talk]]) 12:40, 27 September 2017 (CEST)
:: Thanks for the further explanation around caching. And yeah, I'm not clear there is a lot we can do in the pure wiki. Admins can revise the site JavaScript and had thought some script running on a list of links could likely resolve this more cleanly. Though I think I'd forgotten about an aspect you brought up, in that the regular version updates force page refreshes. I wasn't clear that those sorts of refreshes updated the video order, if they do this is less of a concern; though preventing the user edit's trying to game the system (even if their "fixes" reset the next revision) would probably be for the best. [[User:Kolano|Kolano]] ([[User talk:Kolano|talk]]) 12:40, 27 September 2017 (CEST)


= Old Discussions =
= Old Discussions =