Tue, Oct 27
Sep 29 2020
Sep 26 2020
For OSM standard tiles anyone can trigger tile refresh by appending /dirty to tile URL (documentation). Couldn't Wikimedia use the same scheme, or for some reason would it be more of a vector of vandalism in Wikimedia's case?
Sep 12 2020
My expectation would also be that messages are configurable on a wiki where they are actually used. Closest example to this functionality that I can think of is sitelink change done on Wikidata in the name of user who moved/deleted local page. Wikidata edit summaries related to these actions are configurable on Wikidata. In FileImporter's case perhaps you could make this functionality intervene with FileExporter that is available on local wikis, and ship messages for these two edit summaries with the latter extension instead?
Aug 3 2020
It seems that icon overflow remains to be an issue, as lately reported on wiki.
Jul 17 2020
I also remember that these numbers were displayed correctly before 2018. Probably this regression was introduced along with map improvements 2018. Perhaps someone who knows how to test older versions of Kartotherian and/or osm-bright style can track down which change exactly is responsible for these malformed number shields?
Jul 9 2020
Jul 2 2020
Jun 26 2020
A few thoughts about general options to track imports. I think ideally the import log could have a field which allows filtering imports by source (maybe by wildcarding interwiki prefixes that are already present in log entries of page imports in order to link to source page). So imports could be found by source via simple interface, and in more reliable manner, without depending on page content that can be changed during/after import.
Jun 8 2020
A possible workaround is to actually "revision delete" the problematic file revisions before triggering the import. I haven't tested this but believe it should work.
Jun 5 2020
So files with invalid versions are expected to be imported manually without preserving file history, even if original author already uploaded fixed version?
May 23 2020
Apr 5 2020
Apr 3 2020
Apr 2 2020
For me map snapshot is missing for certain language variants (zh-cn, ch-my). So mostly it seems the same as T246314. Current differences between how browsers and/or mobile treat missing image is covered in T248722, I think.
Mar 31 2020
Actually I observe the same behaviour (window resize makes JSON overlay/all tiles appear, as in Evad's frameless map example) also when not using autozoom, particularly when map has new/updated (uncached) JSON. There apparently are some difference between browsers (or browser versions) for this behaviour, but for me, until very recently this didn't happen and content for dynamic maps generally loaded well, including when previewing and in Commons/Wikidata that don't use static frames. I don't know if related, but it's also new for me that these improperly initialized frames are collapsed during page load (related to switching to <img>?).
Mar 30 2020
Interestingly resizing a browser window gets JSON overlay object loaded and map centered to it for frameless dynamic map. Similarly, since recently I observe that when using auto-positioning (omit frame coords/zoom), then JSON overlay and some tiles don't appear until after window resize for both frameless and framed dynamic map (at least in some browsers).
Mar 23 2020
Is it known that missing config pages cause significant problems in the first place? If users really are stuck and can't import files, then maybe for a start relevant error message should be expanded by adding further instructions (e.g. link to help page) on how to create a config page.
Mar 20 2020
Mar 19 2020
Now zoom defaults to level 13 again when latitude and longitude are specified.
Mar 18 2020
Mar 17 2020
Mar 13 2020
Mar 12 2020
It's not specific to Malayalam sites. It was reported years ago also for ru.wikipedia and fi.wikipedia (T122241). I can add that there have been similar complaints on et.wikipedia.
Feb 25 2020
Currently this appears to be resolved by an accident (T246071). Could you keep Accept-Language detection enabled for some multilingual wikis like Commons and Wikidata? It seems some work has been done in the meanwhile towards alleviating caching issues (see T203179).
Feb 19 2020
Feb 5 2020
This appears to be be because maplink element currently expects latitude and longitude attributes to be used with zoom attribute, but Wikibase in GlobeCoordinateInlineWikitextKartographerFormatter.php provides latitude and longitude value for maplink without zoom value.
Jan 29 2020
This should be fixed now. See T242517.
Jan 28 2020
@Jdlrobson, do I get this right that "Blocked on Others" means that you are not going to +1 the patch? If so, then who is the "others" that I should request review from before I can arrange a deployment?
Jan 26 2020
Jan 18 2020
I'm closing this as language fallbacks have been adjusted as a workaround, and example given in task description apparently displays in correct language now. Underlying LanguagePicker issues are covered in parent task.
Jan 13 2020
Perhaps it's the same as T214984? These examples on mediawiki.org currently include newlines in SPARQL, which apparently isn't allowed in proper JSON.
Jan 8 2020
Dec 25 2019
Dec 15 2019
Without entering mapframe_lat and mapframe_long in "Infobox park" it takes coordinates from Wikidata. I fixed this on Wikidata.
Dec 14 2019
Nov 18 2019
Oct 31 2019
Oct 22 2019
Oct 15 2019
I doubt if this fix attempt changes anything in regard to validity of this water area.
Oct 8 2019
Do I get this right, to make the following showcase map work without Lua, now there isn't a more readable way than removing all newlines from SPARQL?
Sep 30 2019
Indeed, sorry. I only looked that original report was about edit conflicts and I figured that file imports don't have much to do with signatures. Now I recall that file description pages sometimes do include signatures. :)
Sep 27 2019
Sep 25 2019
Sep 20 2019
I didn't notice this recent changeset as I checked the relation earlier. Comparing previous version with current one, it doesn't seem like duplicate segments or nodes were removed, though. I see that two new nodes were created almost in place of deleted ones. Also, while member way segments were altered a little, neither version seems to have duplicate segments. So I doubt if this fix attempt changes anything in regard to validity of this water area. However, previously when some objects were missing I noticed that mere dummy edit (no actual change) to a relation made Wikimedia system to pick up this object. So maybe this fix attempt will have similar effect.
Doesn't seem like water area was broken on OSM as then at least zoom levels 10+ would be expected to have some fixed tiles by now. Lake Victoria (mentioned earlier in T231691#5460894) is also still gone. Is this something like T218097 again?
Sep 18 2019
And now there are also URLs in source wiki edit summaries (T227358). In addition to edit summaries and log comments on target wiki, those would also benefit from clickable wikilinks. Does that warrant a separate task?
Sep 17 2019
Sep 14 2019
This can be considered a long-standing design choice on Wikipedia, rather than a bug. Some alternatives are discussed in T120809. Of which some may be poorer choice cartographically. It probably needs to be discussed on Wikipedia if they want to shift towards more wide-spread use of different kinds of location maps.
Sep 12 2019
Sep 11 2019
Update: We haven't seen this error yet.
@awight, do you mean that you can't reproduce this? I still run into an error if I try to to import "Image002.gif" mentioned above. On Grafana this shows up as "duplicateFiles" error. On July 28th, when another user reported this on wiki and when I created this ticket, I see 12 errors of this type recorded.
Sep 9 2019
Sep 8 2019
I had the same problem after editing https://et.wikipedia.org/wiki/MediaWiki:Citethispage-content yesterday. Now after about 24 h it finally started to work when visited via sidebar link.
Sep 2 2019
Looks good to me on beta wiki.
Sep 1 2019
@Gehel, there's also a lake in Norway waiting for monthly automatic update to reappear in smaller zoom levels (T230511). What are the guidelines on how should users report such issues so that they would get fixed reasonably quickly?
Aug 29 2019
Aug 27 2019
Aug 15 2019
Aug 13 2019
Aug 12 2019
Aug 7 2019
I'm closing this as Chinese fallbacks were improved in a pull request. Please reopen if it doesn't work as intended.
Aug 6 2019
Aug 5 2019
Repeating the object over and over doesn't seem necessary to me and if tech people say it isn't a good idea then I defer to this assessment.