Jul 27 2019
Jul 23 2019
Got you. Still, I've done that multiple times now (click "Reload", get asked to login again, and login with the new credentials), yet the Full name still shows "Waldir" as shown in the screenshot above.
Jul 20 2019
I've managed to log in to Wikitech now.
Jul 15 2019
@akosiaris, I seem to be having trouble following those instructions. I can't log in on Wikitech nor on Gerrit. Please see the screenshots attached below:
Jul 8 2019
Jul 1 2019
Also, is there any similar process for renaming my related account(s) on Wikitech, Gerrit, Toolforge, etc.?
Thanks! Are there any cleanup changes I need to perform after this? I noticed for example that my watchlist RSS feeds became invalidated, and I needed to manually resubscribe to them by manually changing the subscription URL from
Jun 24 2019
Jun 9 2019
Jun 8 2019
Makes sense, thanks. Btw, sorry I pinged you using the wrong username, I wasn't sure which one to use :)
- Go to https://www.wikidata.org/wiki/Wikidata:Tools/Query_data#SPARQL_query_builders
- Click "edit source" in the "SPARQL query builders" section
- Add a <translate> tag, e.g. change |name = Vizquery to |name = <translate><!--T:999-->Vizquery</translate>
- Click "publish changes"
Sorry for the large update. Phabricator doesn't make the diff easy to read, but I changed mostly formatting for consistency and readability, and updated the introductory test to reflect the status of the Etherpad document. Here's a more readable diff: https://www.diffchecker.com/SKGQWjli
May 23 2019
@Ryasmeen please let me know if you need any details of my setup to be able to reproduce this issue. I'm happy to assist however I can.
Understood, @bd808. I suggest keeping this issue open to track clarification of that UI so this confusion no longer happens for others. In the opening comment I suggested two ways that IMO could make the interface clearer.
May 21 2019
@Lydia_Pintscher agreed. The reason I wanted these tools to be live was to allow them to be experimented on, and allow identifying the good design choices and UX patterns, to help build the default builder. T223852 was about precisely identifying these tools and listing them in an accessible location, and T223853 was about doing some preliminary UX testing work (it can be reopened if there are plans to expand that work further — /cc @Charlie_WMDE).
PR #83 has been merged as well. I'll leave this open until @alaa_wmde voices his thoughts.
May 20 2019
There was an attempt to revive the tool by:
May 19 2019
The tool's code has been recovered with @Chicocvenancio's help, and put into a github repository at https://github.com/waldyrious/sparql-query-generator, to which @Jakob_WMDE has write access.
Also of note that @Bene's sparql tool, which used to be available at https://tools.wmflabs.org/bene/sparql/, was down; it was restored to a GitHub repository (see T223858), and is currently available at https://waldyrious.github.io/sparql-query-generator, and the new URL has been added to the list mentioned above.
Done. Various approaches were investigated and experimented with, and the simplest one was documented thoroughly, in a step-by-step guide, in Help:Toolforge/Auto-update a tool from GitHub. Links to the new guide were added to Help:Toolforge#Using Github or other external service and Help:Toolforge/How to, for discoverability.
Done. The collected information is now available at d:Wikidata:Tools/Query data, in a new dedicated section for query builders.
This is now done, with the merge of PR #60.
This is now done. The tool is now available at https://tools.wmflabs.org/primerpedia.
@bd808 understood, but what about the last suggestion in the task description?
May 18 2019
May 17 2019
Apr 1 2019
Feb 20 2019
Dec 28 2018
Oct 27 2018
Aug 18 2018
Aug 16 2018
Jul 23 2018
Jun 16 2018
Just for completeness, I'm copying the comment I added in T195754:
We don’t want any of those
May 29 2018
FWIW, I use this quite often (manually), when the search results are too numerous and I'm looking for items with a specific name, since the intitle: operator doesn't work for Wikidata items.
Is there any way an error message could be shown to users to explain why Special:ItemDisambiguation is being redirected to Special:BlankPage? It's quite puzzling for someone who isn't aware of the current issues.