Page MenuHomePhabricator
Create Task
Maniphest T19525

css and .js pages should not store entries in Categorylinks table/Templatelinks table
Closed, DuplicatePublic
Actions

Description

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

See also

Details

Reference
bz17525

Related Objects

Event Timeline

• bzimport raised the priority of this task from to Low.Nov 21 2014, 10:31 PM
• bzimport added a project: MediaWiki-Parser.
• bzimport set Reference to bz17525.
• bzimport added a subscriber: Unknown Object (MLST).
Umherirrender created this task.Feb 16 2009, 9:08 PM
• brooke added a comment.Feb 17 2009, 6:48 AM

Looks related to bug 10410; since the page isn't parsed as normal, it may not be saving links entries.

He7d3r added a comment.Apr 3 2011, 1:21 PM

Is this is related to bug 8761?

Krinkle added a comment.Apr 3 2011, 6:17 PM

(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.

Bawolff added a comment.Apr 3 2011, 9:11 PM

(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.

duplicatebug added a comment.Nov 17 2011, 6:11 PM

related bug 32450

Platonides added a comment.Dec 8 2011, 5:32 PM

*** This bug has been marked as a duplicate of bug 32858 ***

He7d3r closed this task as a duplicate of T34858: Do not parse .js/.css pages and save their parsed content in database tables.Apr 13 2015, 2:53 PM
He7d3r mentioned this in T10761: Template transclusion done "behind the scenes" when saving a user .js page.Oct 22 2016, 1:04 PM
He7d3r updated the task description. (Show Details)Oct 22 2016, 1:06 PM
Content licensed under Creative Commons Attribution-ShareAlike (CC BY-SA) 4.0 unless otherwise noted; code licensed under GNU General Public License (GPL) 2.0 or later and other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL