Last modified: 2012-01-08 01:53:56 UTC
Please do not store Categorylinks/Templatelinks from .css and .js pages in Categorylinks table/Templatelinks table, because there are not shown on that page. (No 'catlinks' section/template will shown as normal wikitext). Thanks. Example: When scripting there can be code like '"[[Category:"+cat.substring(0,1).toUpperCase()+cat.substring(1)+"]]"', this will produce a disadvantageous entry in 'Category:"+cat.substring(0,1).toUpperCase()+cat.substring(1)+"'. Pagelinks table is useful to have backlinks and can find/support all usage of a script. I have no observation about Imagelinks table
Looks related to bug 10410; since the page isn't parsed as normal, it may not be saving links entries.
Is this is related to bug 8761?
(In reply to comment #1) > Looks related to bug 10410; since the page isn't parsed as normal, it may not > be saving links entries. That's exactly how it should be, but the point is that it does. I've fixed the summary of this bug to reflect what Umherirrender describes in his message, which is a confirmed bug. Stuff like that causes it to be saved to the categorylinks and templatelinks tables. Pagelinks and imagelinks are useful since they allow WhatLinksHere and GlobalUsage to easily detect where things are used or referenced.
(In reply to comment #3) > (In reply to comment #1) > > Looks related to bug 10410; since the page isn't parsed as normal, it may not > > be saving links entries. > > That's exactly how it should be, but the point is that it does. I've fixed the > summary of this bug to reflect what Umherirrender describes in his message, > which is a confirmed bug. > > Stuff like that causes it to be saved to the categorylinks and templatelinks > tables. > > Pagelinks and imagelinks are useful since they allow WhatLinksHere and > GlobalUsage to easily detect where things are used or referenced. I really think such pages should either parse everything or nothing. Only populating pagelinks but not categorylinks sounds like un-intuitive behaviour to me.
related bug 32450
*** This bug has been marked as a duplicate of bug 32858 ***