Sep 5 2019
Some observations: If the wikitext is slightly modified, the problem will go away:
Sep 2 2019
Sep 8 2018
After seeing the new proposals I changed my order of preference a bit:
Sep 5 2018
This bug is quite annoying for Lua wrapper templates, because they inevitably use nesting. I will be very pleased if this gets fixed.
Aug 18 2018
T202190 is probably the same issue.
Oct 16 2017
CSS selectors like q:lang(cs) should be added as well, I think.
Jul 26 2017
(Obsoleted by T171581#4568792)
My favorites in the order of preference (best first):
refines (definitely with -s to indicate direction) extends (definitely with -s to indicate direction)
Jul 3 2017
Maybe this advantage has been mentioned as SEO already, but stating it explicitly:
Machine-understanding of HTTP redirects does not require any advanced parsing.
Jun 28 2017
It seems that even some usage is tracked, although I am not sure if it is 100% correct: Employment of the new function leads to the following text appearing in the Edit source page:
Wikidata entities used in this page
- United States of America: Title
mw.wikibase.getEntityIdForTitle( pageTitle ) seems to work as expected at testwiki:Template talk:Country ID.
Jun 27 2017
Jun 26 2017
@Krinkle Thank you for your thorough explanation. I just thought that the rdfrom parameter's purpose was to be able to provide the "Redirected from .." message while using a HTTP 302 redirect:
If /wiki/Redirect responds with something like
302 Found; Location: /wiki/Target?rdfrom=Redirect#Section, we will:
- not need to purge /wiki/Redirect upon modification of Target,
- not need to alter <a href="/wiki/Redirect"> in rendered pages,
- not need to purge pages linking to Redirect upon its modification,
- have to purge /wiki/Target?rdfrom=anything upon modification of Target.
Jun 25 2017
Among other things, I have inserted the words ", unless <ref name="A"> info2 </ref> exists as well" into the task description. If I got the consensual intention wrong, please correct it.
Jun 24 2017
Jun 23 2017
Still inconsistent in MW version 1.30.0-wmf.6 (85da774).
I have removed the sentence about performance issues from the description. It seemed to imply that this enhancement is not going to happen, but in fact it is just a problem that has to be solved as part of this task. Some of you already dipped in it above.
Jun 20 2017
Jun 12 2017
This problem can be fixed easily. Here is a dysfunctional (as Lahwaacz pointed out below) solution based on @TheDJ's proposal: If request_URI targets a redirect to Section and request_URI does not contain any fragment part then respond with a HTTP redirect to canonical_URI#Section. Otherwise respond like MediaWiki always did.
Jun 10 2017
For the sake of naming consistency, maybe the new function's name should be mw.wikibase.getEntityIdForSitelink because we already have functions mw.wikibase.sitelink and mw.wikibase.entity:getSitelink. The latter has an optional parameter globalSiteId with values like "enwiki".
Jun 7 2017
@matej_suchanek pointed out during the review, that mw.wikibase.getEntityIdForTitle(pageTitle) should add an entry to pagelinks, i.e. (if I am correct) record the target page as linked from current page, and I think that he is right. However, I believe it is ok to proceed without that now and leave it for the "improvements in the future", as @Tpt said. In majority of cases, the target page will be linked by other means anyway. For example, a flag template, which uses property P41 (flag image), will create a clickable link to the article about the country.
Note that this has nothing to do with usage tracking (T142093).
Jun 5 2017
Someone please review @Tpt's patch mentioned in T74815#3314217. The most important functionality is already there and we have been waiting for it for years. That part of API is not going to be affected by the discussion of the final API.
Dec 30 2016
Jun 6 2016
Mar 31 2016
Mar 13 2016
Mar 12 2016
Setting the highest priority to hasten the investigation, which is possible probably only until the article is touched.
Mar 2 2016
Feb 29 2016
Feb 27 2016
Feb 9 2016
The patch also fixes the following problem:
@matmarex Yes, if I switch the interface to Czech language, I do see it, but in English I don't.
Feb 8 2016
@Fomafix That means that my claim applies only to $wgMaxRedirects = 1. I edited the post once again and hope that my critique is correct now.
@Mdann52 Are you sure you have not fallen victim to the bug T32359? Let us have $wgMaxRedirects = 2 and a redirect from A to B. If you complete your redirect chain by moving B to C, then the double redirect from A through B to C will not be followed due to that bug. However, if you create the redirect from A to B as the last operation, it should work.
I edited the post in an attempt to improve it, hope it's clear now.
This task cannot be a duplicate of T67064, because the bug described here is not mentioned there.