Last modified: 2006-02-09 21:27:13 UTC
Halló, I experienced in many Wikimedia Foundation wiki's that categories have been added to EXISTING templates. So far I do not know another method then making a minor change to the page containing that MODIFIED template. a) NEIGHTER purge will help b) NOR deleting and restoring the page Nevertheless if the problem affects HUNDEREDS of pages an automated method should be available. c) it would be usefull that purge should update the membership in the category so that if you load the category page after, you will see the page purged before d) if a page is restored the membership in the category should be updated so that if you load the category page after, you will see the page restored before f) if there are reasons not to modify action=purge then a more effectiv action like action=update should be implemented Regards Reinhardt
One way to rebuild categories is to run the refreshLinks.php maintenance script. This is a very expensive operation. I do not believe there is any way of effectively updating a single category listing without looking through the text of /all/ articles. I agree that there should be an action for a page to cause it to rebuild all related index entries - text index, links, category links, etc. Although this won't solve the problem of out-of-date category listings, at least it would make it possible to manually update it without having to open each page and save it again.
What might make more sense for dealing with category entries in templates would be to have a refresh option associated with the template page. This could cause a category refresh for all pages that include that template. However: - You can have nested templates. This complicates the process. - For each page that transcludes the template directly or indirectly, the entire page has to be parsed (including all transclusions) for category membership. This is, as they say, "non-trivial". - Some templates are transcluded into a huge number of pages. Consider {{stub}} on en.wikipedia.
note on comment 0 item f) comparing the "''actual code of a page''" (and knowing how it interpreted in the wiki system) whith the result from action=purge and the known workarounds to fix related bugs these can be split in: a) requiring one (minor) edit to get the requested result example(s): bug 1119: Page move updates categories with sorting tweak ... b) requiring more (minor) edits to get the requested result example(s): bug 1993: Categories added to templates are not added to including pages duplicate of 39: changes to links in a template do not update 'links', 'categorylinks', etc for pages including it bug 2258: Category links in image upload summary field have wrong sort key bug 2327: sort key is not evaluated again if a page is moved bug 2331: undeleting pages does not add the pages to categories ... If you are not shure what is necessary to do (remove the categories and insert them back again) you will need more (minor) edits. In addition a lot of verifying and possible purging will be necessary. The correct implementation of a more effectiv action=update or action=rebuild should be a powerful workaround for all these situations. It is a "handling tool" not a fix for the mentioned bugs. Regards Reinhardt [[user:gangleri]]
see also bug 939: changes to links in a template do not update 'links', 'categorylinks', etc for pages including it
removed http://jadesukka.homelinux.org:8180/mediawiki15c/index.php?title=Luokka:Stub&action=purge because the Nike's test wiki *Betawiki* is behind a firewall new URL http://yi.wiktionary.org/w/index.php?title=template:word&action=history changing to *enhancement* Hallo! Is there anything new about this issue? At http://yi.wiktionary.org/wiki/special:Recentchangeslinked/category:1 you can see that minor edits are required to *"update category membership"* whenever the *basic template* is changed. At the beginning there are quite a lot of changes: http://yi.wiktionary.org/w/index.php?title=template:word&action=history Providing this enhancement would limit the number of revisions and keep the database small storing *onlyreal* content changes. regards reinhardt [[user:gangleri]]
Same as Bug 1119: Page move updates categories with sorting tweak this bug is "half" fixed; see: http://test.wikipedia.org/wiki/User:Gangleri/tests/bugzilla/02098 'A bugzilla 02098' was created and moved to 'B bugzilla 02098' http://test.wikipedia.org/w/index.php?title=Category:Bugzilla&action=purge action=purge was enough to see 'B bugzilla 02098' at letter B *no* "minor edit was required any more. What is still required is to "clear the cache for the category page". The difference between bug 1119 and bug 2098 was: bug 1119 did not specify the existance of a sort key bug 2098 did specify a sort key which changes with pages moves best regards reinhardt [[user:gangleri]]
(In reply to comment #6) This was posted at the wrong place. Now at bug 2327 comment 6. bug 1119 and bug 2327 do not require an action=update or action=rebuild any more This might still be required for Bug 3622: "Rollback doesn't roll back category sort key" Bug 4713: "Moved pages dissapear from "Whatlinkshere" of templates they include"
Duping this up to 4857 since the daemon described there would handle this. *** This bug has been marked as a duplicate of 4857 ***
