Wikidata:Contact the development team/Archive/2015/08

This page is an archive. Please do not modify it. Use the current page, even to continue an old discussion.

Strange display of ourdou language text property

Hello,

On Amanullah Abbasi (Q15983392), I have a strange display of name in native language (P1559) : is this caused by the right-alignment of ourdou, or is it something else.

Could someone please check it for me, if I made an error ? Thanks --Hsarrazin (talk) 18:58, 1 August 2015 (UTC)

Yes, it looks like the root cause of this issue is the right-alignment of ourdou. I think it should be reported to the development team. Tpt (talk) 19:49, 1 August 2015 (UTC)

=> transfered to Dev Team - Thanks :) --Hsarrazin (talk) 20:24, 1 August 2015 (UTC)

It seems to be caused by the left-to-right mark at the end of the statement's value, removing that makes it display properly for me. That probably shouldn't be there anyway, but wrapping the value in <bdi> tags would be one way to stop a statement's value from affecting the language name placed after it in browsers which support that. - Nikki (talk) 20:43, 1 August 2015 (UTC)

Thank you :) I've opened a ticket for this at phabricator:T107861. --Lydia Pintscher (WMDE) (talk) 10:14, 4 August 2015 (UTC)

datatype - number; confidence level

If datatype number and number with units are to have an uncertainty parameter then they should have a en:Confidence level parameter as well. Without this the uncertainty loses half it's meaning. Even if most of the numbers on wikidata leave the confidence level as "unknown" it is still good to have it for those measurements where it is known.
e.g. 2315.6 +-2.49, 95% confidence. Joe Filceolaire (talk) 14:02, 3 August 2015 (UTC)

@Filceolaire: You forget several points:

lower and upper bounds can be different so you should be able to distinguidh between different values
+-2.49 can be relative or absolute, so this is an additional parameter
95% confidence is not enough, you should provide the distribution method: normal, lognormal, triangular, quadratic,...

So we have as parameters: upper bound, lower bound, absolute/relative, method and confidence interval. Five parameters and I hope I forget nothing. Snipre (talk) 15:03, 3 August 2015 (UTC)

+1. --Izno (talk) 15:24, 3 August 2015 (UTC)

It would be better to simplify and then to extend the data type. Now there is an attempt to make a supertype that shall encompass all different use cases, but with a fixed modelling capacity. This will not scale very well. Uncertainty and confidence level is meaningless without a proper error model. You simply can not talk about uncertainty without relating it to errors and confidence levels. Error bounds given by a ±δ is nothing more than a linear error model, which is a overly simple model in many (most) cases. The common case is an error model that is a standard deviation. Jeblad (talk) 15:31, 3 August 2015 (UTC)

action=purge

Tracked in Phabricator
Task T108186

For some time now, I have to purge larger pages to be able to view them (Generally the constraint reports generated by Ivan's bot). Is there some issue or is this intended? --- Jura 17:07, 3 August 2015 (UTC)

What happens if you do not purge? Do you have a link to one that is affected? --Lydia Pintscher (WMDE) (talk) 10:14, 4 August 2015 (UTC)

It's just a blank page that looks like this (with layout, title, but no content).

It happens frequently with Wikidata:Database reports/Constraint violations/Mandatory constraints/Violations, but not now. I will post the next one I come across. --- Jura 10:23, 4 August 2015 (UTC)

That page is blank now, just after the update. --- Jura 11:45, 4 August 2015 (UTC)

I keep seeing two types of things, sometimes it's a blank page like Wikidata:Database reports/Constraint violations/P409, other times it's in the wrong language like Wikidata:Database reports/Constraint violations/P214. - Nikki (talk) 10:51, 4 August 2015 (UTC)

Reported a bug.--GZWDer (talk) 13:45, 6 August 2015 (UTC)

Size calculations in history

The size calculations are a bit strange. This shows up in recent changes, contributions and history. Take a look at this history. The size actually shrunk while I added a label. Due to conservation of information I now expect that there is a "white hole" somehere that ejects the missing bytes… Jeblad (talk) 22:46, 3 August 2015 (UTC)

An even worse size change is this one. Jeblad (talk) 03:36, 4 August 2015 (UTC)

I guess it's because the datamodel has changed since the last time the page was edited. You can see this also in Wikipedia when you edit pages who hasn't been edited for 10 years. -- Innocent bystander (talk) 07:27, 4 August 2015 (UTC)

See Wikidata:Contact_the_development_team/Archive/2014/08#Why so big size of diff?. --Succu (talk) 08:22, 4 August 2015 (UTC)

The representation of ISO-like timestamps within the serialization changed recently. So we have various timestamps in the serialization that went from eg. "+00000002014-04-24T00:00:00Z" to "+2014-04-24T00:00:00Z". Cheers, Hoo man (talk) 10:05, 4 August 2015 (UTC)

Trailing zeros have to be omitted by now, Hoo man? Is there any place this change is documented? --Succu (talk) 21:44, 5 August 2015 (UTC)

@Succu: This shouldn't affect data input in any way, only the internal serialization is affected. Due to that you should still be able to enter ISO-like dates with leading zeros. If something regarding date input changed, please open a bug about that. Cheers, Hoo man (talk) 22:05, 5 August 2015 (UTC)

Strange behaviour on watchlist

I found new examples of the problem I reported here:

 b   22:40 	Daniel Titinger (Q20003748)‎‎ (2 bewerkingen | geschiedenis) . . (0)‎ . . [KrBot‎ (2×)]
         b   	22:40 (huidig | vorige) . . (+347)‎ . . KrBot (Overleg | bijdragen | blokkeren) (‎Claim aangemaakt: VIAF (P214): 31767157)
         b   	22:40 (huidig | vorige) . . (+819)‎ . . KrBot (Overleg | bijdragen | blokkeren) (‎Referentie toegevoegd aan claim: VIAF (P214): 31767157) [terugdraaien]
 b   22:40 	Lucas Biscombe (Q20004016)‎‎ (2 bewerkingen | geschiedenis) . . (0)‎ . . [KrBot‎ (2×)]
         b   	22:40 (huidig | vorige) . . (+348)‎ . . KrBot (Overleg | bijdragen | blokkeren) (‎Claim aangemaakt: VIAF (P214): 103742680)
         b   	22:40 (huidig | vorige) . . (+819)‎ . . KrBot (Overleg | bijdragen | blokkeren) (‎Referentie toegevoegd aan claim: VIAF (P214): 103742680) [terugdraaien]

Mbch331 (talk) 08:53, 4 August 2015 (UTC)

Thank you. I'm not sure how we can fix this yet but we're reworking the watchlist on the client at the moment. Let's see if that gets us closer to a fix. --Lydia Pintscher (WMDE) (talk) 10:16, 4 August 2015 (UTC)

language links missing from en:Genderqueer

although all the links are present on non-binary (Q48270)

Also missing from en:Genderqueer is the link to wikidata in the left side menu.

I have checked some other articles at random and this seems to be the only article affected. Joe Filceolaire (talk) 23:40, 4 August 2015 (UTC)

It might have been a temporary problem, the links are shown and I couldn't find any reason for it (like an accidental transclusion of {{Noexternallinks}}). Matěj Suchánek (talk) 07:09, 5 August 2015 (UTC)

Working for me now as well. Joe Filceolaire (talk) 16:36, 5 August 2015 (UTC)

Constraint violation which seems like it can't be resolved

When I check the constraint report for Q2005111 it currently gives 2 violations. The violation for lyrics by (P676) has been resolved, but won't show up until the changed constraints have been updated in the report, but it also gives a range error on date of first performance (P1191), which I don't know how to resolve. The entered date is valid when I check the range on the property talk page. So either the range on the talk page is invalid, or the report can't handle dates very well. Mbch331 (talk) 09:35, 5 August 2015 (UTC)

Thank you. I've opened phabricator:T108672 for it. --Lydia Pintscher (WMDE) (talk) 10:24, 11 August 2015 (UTC)

auto descriptions

I see that Reasonator generates descriptions automatically now. See [1]. Is there any chance that wikidata could do this when suggesting values for properties? It really would be helpful, even in English. It would mean that adding a few basic classification statements would mean you could generate descriptions in many different languages. Joe Filceolaire (talk) 20:04, 5 August 2015 (UTC)

A autogenerated description „species and taxon“ for around 1,700,000 species is helpfull to distinguish them? --Succu (talk) 20:13, 5 August 2015 (UTC)

@Succu: You're killing me.

First : Yes, using generic classification tools make the use of generic tool more efficient. Traduction: using more specific instance of (P31) and subclass of (P279) statements instead of parent taxon like any other else would do a lot for the autodescription and would make them better without any adaptation to taxonomy
Second : If you want better autodescriptions, even using "parent taxon", ask for the adaptation of the autodescription tool to the current taxonomy model, with only one feature request you can make those 1,700,000 species description way better.

And please quit that tone to people who only want to make the project better, they are not your ennemies ... author TomT0m / talk page 09:02, 6 August 2015 (UTC)

Unicode issue with the Wikidata API

I am experiencing a problem with unicode characters under certain circumstances. If I retrieve the whole json representation of an WD item with wbgetentities and then try to write it back with wbeditentity, I experience a reproducible error with French language unicode characters in the description, as the WD API returns the following error message:

e.g. for item Q14877651:

{u'error': {u'*': u'See https://www.wikidata.org/w/api.php for API usage',
 u'code': u'modification-failed',
 u'info': u'Item Q14877651 already has label "Il5" associated with language code fr, using the same description text.',
 u'messages': [{u'html': {u'*': u'Item <a href="/wiki/Q14877651" title="\u200eIl5\u200e | \u200emouse gene\u200e">Il5 (Q14877651)</a> already has label "Il5" associated with language code fr, using the same description text.'},
                          u'name': u'wikibase-validator-label-with-description-conflict',
                          u'parameters': [u'Il5',
                                          u'fr',
                                          u'Q14877651']}]},

The WD API is called from a Python script. I normally modify the json representation and write it back afterwards, but even if I just query the API and and immediately write back the unmodified string (except for cropping) to the WD API, the above error occurs. Interestingly, if I edit the french description by rewriting the 'gène' string by hand on the WD webpage before the WD API query attempt, the error does not occur anymore. If decoding the unicode characters in question with Python builtin ord(), they return the same unicode number (232 for è). This problem shows up both in Python2 and Python3. As I retrieved and wrote back the whole item without modification, this suggests to be a bug in the way the Wikidata API handles unicode characters? Thx!

You probably want to set the description for Q14877650 & Q14877651 both to gène. That's not possible if the label is also duplicate (case insensitive). The English description says 1 is a human gene and the other a mouse gene. If you do that to the French description as well (but in French), there should be no problem. Mbch331 (talk) 20:54, 5 August 2015 (UTC)

@Mbch331: Ah, thank you for clarifying that so quickly! I obviously missed the first sentence here: https://www.wikidata.org/wiki/Help:Description Sebotic (talk) 21:12, 5 August 2015 (UTC)

But one more question: I suppose the duplicates existing right now are due to additions way back in time? Sebotic (talk) 21:20, 5 August 2015 (UTC)

There can be two items with the same label, the description is then used to disambiguate between the items. Some people don't know that the description field is used to disambiguate and use it to give a short description. Sometimes however these descriptions are super short (as in you case with only the word gène) and if there are two items with the same label and they are about almost the same thing (as in your case they are both genes), a few more words are needed to disambiguate (in your case you need to make a difference between a human gene and a mouse gene). If no description is provided duplicate labels are always accepted, because there can be multiple items with the same label (and because people are too lazy to add a description or people add labels in multiple languages at the same time) it shouldn't be impossible to add a label just because an item with the same label already exists. To make sure disambiguation is possible duplicates in label+description are prohibited. Mbch331 (talk) 08:54, 6 August 2015 (UTC)

Problems with translating

Either I'm doing something wrong, or there is a bug. I updated Wikidata:Requests for deletions/Header and added a section T:18. Then I marked the page for translation. So far so good. No errors nothing. Then I clicked the translate link on the page and started translating the new section into Dutch. Everything looked fine. I did notice the translation was in a yellow box, but thought nothing of it. When I tried to leave the page, I got a warning that not all my changes on the page were saved. Couldn't find a save button, so went along anyway. I checked WD:RfD and the sentence wasn't translated. I tried several times more to translate, but always the same result: a yellow box and the sentence not being translated. I updated some other translations to the header and in my contributions saw the name of the updated pages. I quickly found out that the page that had to be altered was Translations:Wikidata:Requests for deletions/Header/18/nl. I opened that page directly and pressed create. I didn't get an editor, but I did get an error message:

You do not have permission to create pages, for the following reason:
This namespace is reserved for content page translations. The page you are trying to edit does not seem to correspond any page marked for translation.

Just tested again (knowing the edit to add the new section to Wikidata:Requests for deletions/Header was over 24 hours) and still can't translate it. Am I doing something wrong or is this a bug? Mbch331 (talk) 10:32, 7 August 2015 (UTC)

You have added "" manually which was wrong. This is nothing Wikidata developers should care about. Matěj Suchánek (talk) 10:43, 7 August 2015 (UTC)

As I said when I started this topic: "Either I'm doing something wrong". Thanks for telling me what I did wrong. Mbch331 (talk) 10:47, 7 August 2015 (UTC)

Please don't ".. drop the wb_entity_per_page table"

Wikidata tables missing

From [2]: "We plan to drop the wb_entity_per_page table".

Currently I'm using this to query on http://quarry.wmflabs.org . I think @Matěj Suchánek: and possibly a few others do the same (@Pasleim:?). I suppose it's possible to do without but this seems inefficient in terms of queries. Can we keep this until the Wikidata feature is ready? --- Jura 15:25, 8 August 2015 (UTC)

@Jura1: I'm expecting it to be dropped and have no problem with doing so. Matěj Suchánek (talk) 18:45, 9 August 2015 (UTC)

Matěj Suchánek: There is more recent discussion about it on the mailing list.

Magnus Manske's commment at https://phabricator.wikimedia.org/T95685 is "If you just drop the table without replacing it, I will have to switch to concat-based queries for the page table .., which will be massively slower.". I agree with that.

However, it might be that it simply no longer needed as other tables are changed to enable linking without it.

In any case, CONCAT("Q",id)=page_title is a bad solution.

It would be much easier to comment if there was a summary view of the Wikidata tables with the model before and after as for other tables (File:MediaWiki_1.24.1_database_schema.svg). --- Jura 12:53, 10 August 2015 (UTC)

Nothing new for me, actually. Do you know about phab:T58711? Matěj Suchánek (talk) 13:14, 10 August 2015 (UTC)

No, not that I recall. So it would be "term_full_entity_id = page_title" instead of (page_id = .. ). Is this slower or just as quick? --- Jura 13:25, 10 August 2015 (UTC)

I'm not sure, some experts (devs) could tell us. Don't worry, if queries become slower, Wikidata Query Service will be here for us soon. Matěj Suchánek (talk) 14:57, 10 August 2015 (UTC)

Hey :) Just posting to let you know I've seen this. Marius will have to answer. He's traveling for the next week. Or maybe Katie can in the next days. --Lydia Pintscher (WMDE) (talk) 10:29, 11 August 2015 (UTC)

Values/qualifiers displayed in irrelevant properties

I encountered yesterday and today values/qualifiers displayed in irrelevant properties. See Nikolay Pogodin (Q4366588) and Nikolay Rybnikov (Q4401622) history. --EugeneZelenko (talk) 02:18, 10 August 2015 (UTC)

Can you please clarify what you mean? Is this suggestions from the Primary Sources Tool? Or is it the suggestions you get when adding a new statement/qualifier? --Lydia Pintscher (WMDE) (talk) 10:32, 11 August 2015 (UTC)

I meant values/qualifiers appearance on page before any editing. --EugeneZelenko (talk) 22:29, 11 August 2015 (UTC)

Thank you. Any chance you can post a screenshot of the issue? I just looked at the two pages and they look fine for me. Without a screenshot I fear I can't figure out what's going wrong. --Lydia Pintscher (WMDE) (talk) 12:15, 12 August 2015 (UTC)

@Lydia Pintscher (WMDE), Hsarrazin, EugeneZelenko: I think this is happening to people using JS which changes the ordering of statements. Both EugeneZelenko (here) and Hsarrazin (who posted on the project chat page) have User:Soulkeeper/statementSort.js in their common.js. I use using a more basic version which mostly only moves instance of (P31) and subclass of (P279) and I've also seen similar behaviour. I captured an image of an entire page which failed to render properly and marked all the errors (image here) and it seems like all of the errors are caused by things being off by one, which is what might be expected if the page doesn't realise that all the boxes have shifted down one because of the instance of (P31) statement being moved to the top. After the point where the instance of (P31) statement originally was, there are no more errors.

The strange thing is that it's not consistent. I can refresh the page and have everything load as expected, e.g. I took another page capture of the page I used above after refreshing, it rendered exactly as I expected.

I've also been seeing various other problems with loading, like the authority control gadget will randomly not create links, or my common.js will randomly not work (my common.js includes the code I'm using to collapse the "0 references" section and make the text red instead, which, as you can see, worked in one of the screenshots and not in the other). Like the other people who've mentioned having issues, it only started recently (last deploy?) and I had no problems at all before that. - Nikki (talk) 12:05, 13 August 2015 (UTC)

I concurr with Nikki. The problem is not consistent, and reload generally is enough to fix it.

there is a real problem when, not realising that claims are not properly tagged, you add or remove something without noticing it. I've had a handful of reverts these past days, for that reason... (adding info in the wrong property) :( - you may find them on top of my special Thanks page, as I normally thank people for reverting faulty edits I did unwantingly :)

it looks like the scripts don't load totally, which prevents them from functioning properly. I also had it with Magnus's WDuseful, but this one, you see it when it does not appear ;)

this behaviour is very recent (not before weekend I'd say). --Hsarrazin (talk) 14:44, 13 August 2015 (UTC)

Convert this page to Flow?

I proposed to convert this page to a Flow board. Any users oppose?--GZWDer (talk) 05:05, 10 August 2015 (UTC)

Yes, I do. Unless it has been changed from the bottom up since I looked at it last a few months ago (unlikely), I'll stop editing any page using Flow. Sorry. --Randykitty (talk) 06:24, 10 August 2015 (UTC)
- @Randykitty: Any concrete point ? author TomT0m / talk page 11:23, 10 August 2015 (UTC)
  - I participated in the discussion on enwiki (now in the -14!- archives) and as you can see there, there's massive opposition to Flow. Any particulars you can find there. I must admit that I stopped following the whole brouhaha... --Randykitty (talk) 17:04, 10 August 2015 (UTC)
    - @Randykitty: That's not really specific, and I won't read all of this. Anyway you must know that stuffs changed almost in real time in the Flow test page while I was testing it here, so no, the software is not in the same state it was in June. I don't understand that someone would quit a project just because of that anyway and before even that the system had even a chance to prove itself in day to day situation. Personally I curse every time there is an edit conflict on a big page. That would seem some that passed (community wide) on the wrong side of the rationality line a long time ago. author TomT0m / talk page 17:15, 10 August 2015 (UTC)
      - For the record, I share the position of Randykitty--Ymblanter (talk) 17:41, 10 August 2015 (UTC)
        This does not make it any less mysterious to me author  TomT0m / talk page 17:50, 10 August 2015 (UTC)
        The reason is basically the same. I believe the Facebook-style of talk ages layout is so bad that nothing good can be made on this basis. This has been discussed at length at the pages Randykitty refers to. During the active phases of trial on en.wp things did not get better. Yes, I was told that a bad WMF manager at the time did not want to listen to anybody, and the current good manager is all open for feedback. (The previous one was open as well). Yes, I have heard that some things are improving. Yes, I have seen that many people want to try FLOW on their pages. Since conversion to FLOW is not reversible (at least not without a bot) let them try and see how they manage, and only then we can discuss converting project talk pages to FLOW. (I obviously hope that after a trial nobody would support it anymore, but people have strange ideas sometime). Just to repeat the software I tries was so bed that I definitely prefer edit conflicts.--Ymblanter (talk) 18:02, 10 August 2015 (UTC)
        Still don't get it. Is it buggy ? Is too much space used for signing and username ? Is it just a feeling ? I use this kind of forums since ages and we can totally talk with this ... Think that really bad layouts like PhpBB forums are still in use and that people actually manage ... Flow is way better than both PphBB and facebook, and most online journal discussions systems. author  TomT0m / talk page 18:18, 10 August 2015 (UTC)
        It is indeed very difficult to make a messaging system which would be worse than facebook. My point is that FLOW is way worse than wikitext we are currently using. It solves a problem of edit conflicts, but it creates a dozen of other vital problems, including echo notifications, watchlists, page histories, page archives etc.--Ymblanter (talk) 07:02, 11 August 2015 (UTC)
        It solves a lot of other problems. The post become its own diff. I can very easily forget a post on a discussion in my watchlist which needs tuning and time to load to filtering relevant discussions post compared to mainspace edits. Page archives become useless because the threads are adressable directly and as such bookmarkable, threads are sorted by last activity or by age, ... Seriously, this is full featured. Just in a different way. author  TomT0m / talk page 08:09, 11 August 2015 (UTC)
        I am not really hoping to convince you, but just for the record: This is exactly a feature of FLOW which in my view is highly problematic. If the threads are not archived but are left on an infinite page (Facebook style), old threads are impossible to find. One can still do it via search, but then one needs to know precisely the wording. Additionally, every thread shows up separately in the watchlist (and currently also in notifications, though I believe this can be repaired), making the watchlist unmanageable for those of us who have there thousands of pages including high-traffic discussion boards. Liquid Threads also had this same feature, making it impossible to use.--Ymblanter (talk) 10:22, 11 August 2015 (UTC)
        I bet gadgets like "deluxe history" or personal options will happen very soon with options to regroup discussion on a single page in watchlist. I already could not live without this kind of stuffs so we can't really say it's a regression other the current system. And I really don't get the "old threads are impossible to find" stuffs, as it's just going upstream in the thread history, just like now. author  TomT0m / talk page 10:28, 11 August 2015 (UTC)
        Sure. This is all about scales. Take the Prject Chat, which has 10 new threads per day. In two years, we have around 700 threads. On Facebook, when I have to go down a hundred messages, my browser freezes. I do not see why it should be different here. Not even to mention that a search over a tree is logarithmically more efficient than a linear search.--Ymblanter (talk) 10:40, 11 August 2015 (UTC)
        How is the current system more a tree than flow is ? The linear layout is just for straight answers to the same post in chronological ordering. I bet there will be a split of pages after a number of thread just like it is now if it turns there is a performance issue on big talk pages, just like any special page. And that a special page will appear sooner or later. This is far from beeing an unsolvable issue. author  TomT0m / talk page 10:53, 11 August 2015 (UTC)
        
        https://www.wikidata.org/wiki/Topic:Smsogyhxn8wfx81r here is a tree. Or were you refering to dichotomic search by date of some thread ? author  TomT0m / talk page 10:56, 11 August 2015 (UTC)
        
        anyway, if the flow archive system is not enough, we'll have to ... code bots to maintain an index or do it manually. Not a regression either as this is exactly what we do now. author  TomT0m / talk page 11:10, 11 August 2015 (UTC)
- I can't say I'm sympathetic to your views, but it would still be unfortunate to lose a contributor to the particular pages using Flow. --Izno (talk) 16:50, 10 August 2015 (UTC)
Support. author TomT0m / talk page 11:23, 10 August 2015 (UTC)
Support. Though, I think there's actual page for this that isn't this one. --Izno (talk) 16:50, 10 August 2015 (UTC)
Oppose. This page is the primary contact point for Wikidata developers, who need to be contacted when something goes wrong on Wikidata. Of the things that are likely to go wrong here, Flow is among the most probable. Breaking the bug reporting system is a really bad idea. Sure, we have a Phabricator link at the top, but many people don't know how to use Phabricator. Making this page fragile adds unnecessary risk. --Yair rand (talk) 00:45, 11 August 2015 (UTC)
Oppose It turns out that each message in Flow discussion appears as notification instead of watchlist element. As long as it remains the same I would like to see such thing not enabled on discussions i'm looking after. I still can disable notifications from flow, but i'm missing discussion changes in watchlist a lot. -- Vlsergey (talk) 09:59, 11 August 2015 (UTC)
- @Vlsergey: Wrong. They appear in watchlist element, and you can disactivate Flow notifications in your user preferences.
  - @TomTom: Wrong, they are not. Not in the extended watchlist i'm using. The last change related to 2 flow pages currently in my watch list are:

     00:29 	User talk:Magnus Manske (разн. | история) . . (-679)‎ . . DannyH (WMF) (обсуждение | вклад)
     00:29 	User talk:GerardM (разн. | история) . . (-305)‎ . . DannyH (WMF) (обсуждение | вклад)

- - There are no any later events related to those pages in my watchlist (but there are changes in Flow on those pages). And yes, as i wrote before, i can (and i did) disable Flow notfications. But I still missing changes in my watchlist. -- Vlsergey (talk) 12:35, 11 August 2015 (UTC)
    - @Vlsergey: You may want to hav a word with DannyH (WMF) author TomT0m / talk page 11:25, 12 August 2015 (UTC)
I'm very much in favor of switching to Flow but if there is still reservation I'm good with waiting a month for example where people try it on more user talk pages and then we reevaluate. --Lydia Pintscher (WMDE) (talk) 10:33, 11 August 2015 (UTC)
Yes, I object. We're supposed to be testing flow. Tests should be done on low-importance pages. As I've recently indicated on Wikidata talk:Flow there are significant issues with it. Those should be hard blockers for its deployment elsewhere. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:45, 11 August 2015 (UTC)
Please don't switch this page to Flow. Flow looks like the stuff of nightmares, and Wikidata is fluid, quirky and unpredictable enough without it. - Brya (talk) 16:20, 11 August 2015 (UTC)

Incomplete search result

both API calls should return Q17807075 as a result. -- Vlsergey (talk) 06:32, 11 August 2015 (UTC)

It seems only the second one is actually set as a label. wbsearchentities is only looking at existing labels and aliases. Are you saying it should do a more fuzzy search? --Lydia Pintscher (WMDE) (talk) 10:36, 11 August 2015 (UTC)

@Lydia Pintscher (WMDE): yes. It looks strange that exact string should be provided. I'm using this method for book/sources lookup in Wikidata database, and small title details is not easy to remember. Also, a a feature request, search by property values will be a good feature as well. -- Vlsergey (talk) 11:07, 11 August 2015 (UTC)

Statement semantics and deprecation

It happens that a statement has been deprecated and that we can source the deprecation. We have a property that matches, statement disputed by, but it's unclear to me if this is really an intended use of the Wikibase DataModel to source the deprecation of a statement … What do you think ? If the semantics of a statement is

«it is said in sources … that … »: the deprecation is on the content, and on the source, as it's still true that the sources says that.

Or does the semantics depends on the property used to insert the source ? In which case the semantics could be

«it it said by A and contested by B that …»

then the deprecation is only on the claim because source B may or may not be deprecated. author TomT0m / talk page 16:11, 11 August 2015 (UTC)

I would say strictly speaking it is the former but I think we should just add whatever source is meaningful in that context to have. And that can include one that says it is no longer true. --Lydia Pintscher (WMDE) (talk) 12:24, 12 August 2015 (UTC)

[Fixed] Cannot log in

I have logged into Wikipedia, and when coming to Wikidata I see "Central login: You are centrally logged in. Reload the page to apply your user settings." But after reload, the same message appears and I am not logged in. And when I go to the login page, enter my username and password, and click Login, I enter a cycle. The page keeps reloading, trying to login, failing, trying again, failing, and not stopping. Runner1928, 6:17pm 13 August 2015 CST.

Had that too yesterday. You have to delete your Wikidata cookies in your browser and the problem is solved. Mbch331 (talk) 05:59, 14 August 2015 (UTC)

This is probably due to some changes made in preparation for the query service. Lego opened phabricator:T109038. --Lydia Pintscher (WMDE) (talk) 07:10, 14 August 2015 (UTC)

This should now be fixed. Please report if you still experience this. - Jan Zerebecki 14:18, 14 August 2015 (UTC)

Unit support ... when?

Back in May Lydia expected unit support for numeric properties to be only a few months away. However according to T77977 there still are a number of outstanding matters. I acknowledge "few" to be subject to interpretation, but when should I realistically hope for it? Poul G (talk) 10:09, 15 August 2015 (UTC)

Follow this task: one patch is already developped. Snipre (talk) 21:58, 15 August 2015 (UTC)

We should have the first version on a test system for feedback within the next 2 or 3 weeks. (I'm hoping 2.) --Lydia Pintscher (WMDE) (talk) 10:45, 16 August 2015 (UTC)

Loading ..

I keep getting the loading icon today. --- Jura 07:15, 8 August 2015 (UTC)

I noticed it too. A page load, I get the information, suddenly the loading icon appears for a few seconds and then a few last changes are applied (mostly to the sitelinks). Mbch331 (talk) 07:39, 8 August 2015 (UTC)

The "in further languages" section seems to take quite some time to load. --- Jura 07:50, 8 August 2015 (UTC)

Maybe an option to de-activate it could help. Often, it's not needed. --- Jura 09:58, 8 August 2015 (UTC)

I get it too, and also noticed a few other strange things (see here). Also, I don't see edit buttons any more, except for adding links in the right-hand column and at left for the English label/decription/aliases... --Randykitty (talk) 13:47, 8 August 2015 (UTC)

This all points to java script errors. Are you still having the problem now? We fixed something there just in the last few days that might cause it. If you are still seeing it can you please open the java script console in your browser and see if there are any errors shown? You can open it in Chrome by pressing F12. --Lydia Pintscher (WMDE) (talk) 10:27, 11 August 2015 (UTC)

I'm using Firefox, so how can I check this? And I just opened several pages in several tabs. One came up normal, but when I clicked reload, I got the changed page again with the loading icon. As an aside, I never seem to be able to edit or add any statements, even before I got the problems signalled above and on the project chat. If I go to the site without logging in, I can do that, and also see the 4 languages that I don't see now (see project chat). So it seems to be an issue with the skin I use (monobook), or one of the gadgets. I tried switching them off one by one, but no single gadget seems to be responsible for the problems that I am having. --Randykitty (talk) 15:24, 12 August 2015 (UTC)

BTW, I switched from Monobook to Vector, but that didn't change anything. --Randykitty (talk) 18:24, 13 August 2015 (UTC)

In Firefox, you can open the console by pressing F12 or [Ctrl]+[Shift]+K --Pasleim (talk) 15:31, 12 August 2015 (UTC)

┌────────────────────────────────────────────────────────────────────────────────────────────────────┘ Thanks! That gives a large number of warnings:

"Use of "skin" is deprecated. Use mw.config instead." load.php:156:550

"Use of "wgServer" is deprecated. Use mw.config instead." load.php:156:550

"Use of "wgTitle" is deprecated. Use mw.config instead." load.php:156:550

"Use of "wgCanonicalNamespace" is deprecated. Use mw.config instead." load.php:156:550

"Use of "wgArticlePath" is deprecated. Use mw.config instead." load.php:156:550

"Use of "wgScript" is deprecated. Use mw.config instead." load.php:156:550

"Use of "wgScriptPath" is deprecated. Use mw.config instead." load.php:156:550

"Use of "wgUserName" is deprecated. Use mw.config instead." load.php:156:550

"Use of "wgCurRevisionId" is deprecated. Use mw.config instead." load.php:156:550

"Use of "wgContentLanguage" is deprecated. Use mw.config instead." load.php:156:550

"Use of "wgUserLanguage" is deprecated. Use mw.config instead." load.php:156:550

"Use of "wgEnableAPI" is deprecated. Use mw.config instead." load.php:156:550

"Use of "wgPageName" is deprecated. Use mw.config instead." load.php:156:550

"Use of "wgNamespaceIds" is deprecated. Use mw.config instead." load.php:156:550

"Use of "wgFormattedNamespaces" is deprecated. Use mw.config instead." load.php:156:550

"Use of "wgVersion" is deprecated. Use mw.config instead." load.php:156:550

"Use of "wgPageContentModel" is deprecated. Use mw.config instead." load.php:156:550

"Use of "wgUserGroups" is deprecated. Use mw.config instead." load.php:156:550

"Use of "wgServer" is deprecated. Use mw.config instead." load.php:156:550

"Use of "wgArticlePath" is deprecated. Use mw.config instead." load.php:156:550

"Use of "wgScriptPath" is deprecated. Use mw.config instead." load.php:156:550

"Use of "wgCurRevisionId" is deprecated. Use mw.config instead." load.php:156:550

"Use of "wgPageName" is deprecated. Use mw.config instead." load.php:156:550

I admit that I have no clue what these things mean... --Randykitty (talk) 08:18, 13 August 2015 (UTC)

Any update on this issue? --Randykitty (talk) 08:09, 19 August 2015 (UTC)

We have removed the spinner in the sourcecode yesterday. With the next deployment it will be gone here too. I hope this fixes the issue for you in the next week. --Lydia Pintscher (WMDE) (talk) 10:52, 19 August 2015 (UTC)

The spinner is gone. But all the other problems that I described are still present... Sometimes if I load several pages simultaneously in multiple tabs, one will load normally (until I hit reload...) --Randykitty (talk) 10:04, 20 August 2015 (UTC)

I had the problem too. I disabled all my scripts in my global.js (on meta) and enabled them 1 by 1 until I found the culprit. In my case it was Morebits, disabled that and enabled all my other scripts. Problem solved. So check your global.js and common.js and try to find the script that causes the problem. Mbch331 (talk) 10:11, 20 August 2015 (UTC)

@Mbch331: Brilliant! I fortunately had only two scripts in there, and one turned out to be the culprit (this one, don't even really know what it is supposed to do: "mw.loader.load('//en.wikipedia.org/w/index.php?title=User:AzaToth/morebits.js&action=raw&ctype=text/javascript')"). Many thanks! --Randykitty (talk) 14:21, 20 August 2015 (UTC)

It's exactly the same script I had trouble with. I believe it was related to Twinkle. Well I'm not missing it so far. Mbch331 (talk) 14:57, 20 August 2015 (UTC)

The problem is the script is based on sAjax which no longer works. That breaks the script and it breaks Wikidata. And the person that wrote the script isn't really active. Mbch331 (talk) 15:03, 20 August 2015 (UTC)

item by title and Lua

Tracked in Phabricator
Task T74815

Hi, is there a way to call the equivalent of Special:ItemByTitle in Scribunto apis or via a parser function call ? It's not possible, or I did not find how yet, to get an item object by this way ... author TomT0m / talk page 11:13, 19 August 2015 (UTC)

No, but it's a wanted feature. Matěj Suchánek (talk) 11:20, 19 August 2015 (UTC)

Lua Module in mediawiki & feature request in wikidata

Please excuse, I don't know this is the right place to ask this. After Lua introduction/implementation in mediawiki, template like en:Template:Cite Web is used in all language wikipedias. why can't it be a built-in feature of mediawiki so that it can be rollout to all wikis.
When I wish to update an item in mediawiki (for the language I know), the page displays statements & other project data, because of this, the page size & loading time increases. So I am requesting to provide a special page to display only ITEM section (header) or in settings/preference page I should select which sections I want to display. Thanks --Mahir78 (talk) 03:32, 20 August 2015 (UTC)

The templates vary quite a bit across projects. There are some efforts to unify this but I don't know more bout it. Maybe someone else can chime in. This is not something for Wikidata development.
There is Special:SetLabelDescriptionAliases --Lydia Pintscher (WMDE) (talk) 10:53, 20 August 2015 (UTC)

Feature request: Add "±" in the interface for easy entry

As I don't have it on my keyboard (other than Alt+..), is there a way to add it to the GUI when entering data? Adding "±0" instead of "±1" in a single step would be preferred.

It might be easier to do this change than do a complete re-write of the datatype entry part. --- Jura 09:50, 20 August 2015 (UTC)

You can just type "+-" and it'll automatically do the right thing for you :) --Lydia Pintscher (WMDE) (talk) 10:50, 20 August 2015 (UTC)

Unclean wikibooks templates interwiki move to wikidata

I'm not sure whether the following is a developer or execution problem. If I'm reporting this in the wrong place, then please tell me where to put it.

In Februari wikidata was activated for taking care of wikibooks iw's. However, there seem to be several cases where the appropriate information was added to the wikidata item, but the iw links not removed from the source page. In item Q4847311 (Template:Db), a sampling indicates that the pages whose sitelinks were added here never had their iw's removed.

The trouble is not isolated to that item. I also looked at Q6687153 (Template:Article for deletion), and found a similar pattern. There also seems to be similar trouble with some wikisource templates (at least, I found such at pages linked to from Q14334705, Template:Letter-spacing).

Of course, template iw's may be a bit trickier to handle than many other items, since the iw may be either on the template page itself, or on some kind of documentation page (with the precise name varying from langage to language). Still, IMHO, not removing the local iw lists makes the introduction of wikidata to these projects a bit lopsided. JoergenB (talk) 17:57, 17 August 2015 (UTC)

Hey :) This is something to take up with the bot operator who moved the links. --Lydia Pintscher (WMDE) (talk) 10:54, 19 August 2015 (UTC)

@JoergenB: @QuiteUnusual: and @Pi zero: disallow interwiki removal bot running in enwikibooks for flaggedrev issues. see b:Wikibooks:Requests for permissions and b:Wikibooks:Reading room/Proposals/2015/March#Wikidata and interwikis.--GZWDer (talk) 02:18, 20 August 2015 (UTC)

GZWDer Thanks, I was not aware of these discussions on enwikibooks!

Do you think that the reason templates retain their iw links in some wikisource and wikipedia projects is similar? JoergenB (talk) 17:47, 21 August 2015 (UTC)

Login issue

I logged in to tawiki after that when I open wikidata and clicked login it redirects to login then automatically to home screen with message "You are centrally logged in. Reload the page to apply your user settings." but still the header shows I am not yet logged in. Reloading (ctrl+f5) the page too not working. --121.123.137.215 03:19, 21 August 2015 (UTC)

Delete your cookies. Sjoerd de Bruin (talk) 06:08, 21 August 2015 (UTC)

They're still looking for someone that can provide the headers that are sent to the server when the issue occurs (especially the cookies part). Mbch331 (talk) 09:01, 21 August 2015 (UTC)

Which pages really uses Wikidata

Hello! I remember, that I read something about it, but forgot what and where I read it. So my question is. How to get those Wikipedia pages (in some project), that really are using properties data from Wikidata, like P18 (image) in infoboxes. I don't mean which templates/modules invoke #property/Wikidata module/Wikibase module, but real Wikipedia pages. --Edgars2007 (talk) 09:03, 21 August 2015 (UTC)

Good question, Edgars2007, i'd like to know that too. My information level is this:

HTH, --Atlasowa (talk) 18:30, 21 August 2015 (UTC)

elwiki and frwiki partially track property usage, see Category:Page using Wikidata data (Q15574247). --Zolo (talk) 20:38, 21 August 2015 (UTC)

Thank you, both. Yes, that first discussion was the one, which I read, but there were so many links, that I didn't pay attention to it :) Yes, some special page, where user can search by page title and Wikidata item/property would be nice. --Edgars2007 (talk) 03:34, 22 August 2015 (UTC)

We have phabricator:T103091 for figuring out how to surface this information in a way that is useful to you. I'd appreciate your comments there. --Lydia Pintscher (WMDE) (talk) 07:09, 22 August 2015 (UTC)

Something weird with the property suggester

Where an item is 'instance of:company' the property suggester is now suggesting properties to add which are only appropriate for persons - sex, date and place of birth, date and place of death, occupation. This is new and is in addition to the problem where the value suggester is showing things twice. Joe Filceolaire (talk) 21:16, 22 August 2015 (UTC)

I don't have this problem. Are you sure you've selected the right item? Sjoerd de Bruin (talk) 21:23, 22 August 2015 (UTC)

Wikidata : mais où sont passés les geeks inspirés de Wikipedia ?

J'utilise Wikidata uniquement pour créer des liens interwiki. J'irais éventuellement plus loin mais la documentation accessible ne me permet pas de mesurer les apports des autres rubriques figurant dans la page centrale donc je m'abstiens. La création de liens entre les articles des différentes langues constitue sans doute 99% des maj des contributeurs. Or ces liens sont relégués dans un coin, sans mise en évidence, avec un titre énigmatique (Wikipédia), sans aucun texte explicatif sur la manière de procéder. Quatre fautes lourdes sur le plan ergonomique : la présentation est inadaptée à la pratique de la majorité des utilisateurs. Un problème pourtant simple à régler. Est ce que les concepteurs ont testé le résultat avec un contributeur moyen qui crée quelques articles par an ? Je ne le pense pas. Donc suggestions :

La rubrique lien intewikis doit occuper une position centrale dans la page
Elle doit être mise en évidence par rapport aux autres rubriques (fonds coloré, autre...)
Elle est précédée par une phrase permettant de rassurer le contributeur occasionnel : c'est bien là qu'il doit intervenir pour créer le lien
Une petite aide en ligne est disponible à travers par exemple un point d'interrogation
Plus généralement : toutes les autres rubriques de la page sont précédées d'une phrase explicative et d'une page d'aide directement accessible depuis la page de mise à jour.
Il faudrait également revoir le texte affiché dans la fenêtre de type pop up qui s'ouvre lorsqu'on tente de créer un lien depuis un article qui n'en comportait jusque là aucun. Le terme "site" par exemple ne fait pas partie des termes utilisés par le contributeur moyen.

Un bon développeur se met à la place de l'utilisateur final pour concevoir un écran et ne le conçoit surtout pas selon ses propres critères d'utilisateur qui sont atypiques. Cela m'inquiète qu'autant de geeks soient passés sur cette page majeure sans que ces réflexes de base n'aient joué... D'où le titre de mon intervention. --Pline (discuter) 22 août 2015 à 15:21 (CEST)

My French isn't good enough to understand everything (and don't want to use a translation tool at the moment), but 1 point I want to comment on: You want Interwikis to have a central position, however they aren't the core part of Wikidata. The core part are the statements. Interwikis is just a special type of statement and certainly not leading. Mbch331 (talk) 15:09, 22 August 2015 (UTC)

That may be so but it is an important function and especially for newbies. This comment needs to go to the team looking at the UI. For a while we had a table of contents at the top which at least let people jump to the sitelinks section. It would be good to bring that back. Joe Filceolaire (talk) 21:20, 22 August 2015 (UTC)

In that case, it would be good to have different UIs for different types of users. Often enough, pages are taking very long to load, even when not burdened by all the "newbie-friendly features" suggested here. - Brya (talk) 07:51, 23 August 2015 (UTC)

+1. We definitely need some different skins. Joe Filceolaire (talk) 21:42, 23 August 2015 (UTC)

Valid commonscat not accepted

The Commons category (P373) for Mission: Impossible – Ghost Protocol (Q628154) is invalid according to the constraints report (Special:ConstraintReport/Q628154). I noticed this is also true for it's predecessor Mission: Impossible III (Q288173) (See Special:ConstraintReport/Q288173). According to the constraints report for P373 (Wikidata:Database reports/Constraint violations/P373) there is nothing wrong with the commonscats. (For Q288173 the commonscat was already present on August 12th, so if it were a violation, it should already be on that page) Mbch331 (talk) 10:50, 24 August 2015 (UTC)

I don't think the special page can actually verify the validity of the link. It should be under "to do" or "wont be done". --- Jura 11:00, 24 August 2015 (UTC)

Hmm I'll need to investigate more but at least for the item about me it works: Special:ConstraintReport/Q18016466. Maybe an issue with "-"? --Lydia Pintscher (WMDE) (talk) 11:02, 24 August 2015 (UTC)

@Jura1: It can be tested by fetching the HTTP responsecode (based on Lydia's link it can't do that yet). An invalid category responds with HTTP error 404 (Page not found).

@Lydia: I think the issue is the colon (:) in the category name. Mbch331 (talk) 11:07, 24 August 2015 (UTC)

Ah! That is actually quite possible. I opened phabricator:T110029. --Lydia Pintscher (WMDE) (talk) 12:52, 24 August 2015 (UTC)

Entering references is a bit complicated

Hi, before I can add reference to a statement, I have to open the list of references. Which means two clicks and a mouse move over half of the page. I would prefer to do this with 1-click*. Especially if the number of references is zero. The add-button / + button should be nearer to the dropdown button.

Adding the same reference for multiple statements in an object is tedious. Could you imagine to add a reference to a selectable collection of statements in a single step? Or offer a c/p mechanism for complete references (property & value).

keyword: Usability --Herzi Pinki (talk) 22:41, 24 August 2015 (UTC)

Hey :) You're right. We're in fact working on that right now. Which is also why the expansion by default vanished accidentally. We'll fix that as part of phabricator:T87759. phabricator:T76233 is about finding ways to duplicate references. --Lydia Pintscher (WMDE) (talk) 08:59, 25 August 2015 (UTC)

fine, that the door is already open. :-) --Herzi Pinki (talk) 09:03, 25 August 2015 (UTC)

@Herzi Pinki: Add

mw.loader.load("//www.wikidata.org/w/index.php?title=User:Bene*/DuplicateReferences.js&action=raw&ctype=text/javascript");

to your common.js to copy and paste references. Will be available as gadget soon.

Bidrectional relations

Hi, I run across located in the administrative territorial entity (P131) & contains the administrative territorial entity (P150). Although this is a 1:n relationship (or mayby n:m), I independently have to maintain both ends individually. This is duplicate work and introduces space for inconsistencies. It would be fine if I can change either side and this will effect both sides (e.g. adding references or qualifiers (like a date when this was true)). --Herzi Pinki (talk) 23:00, 24 August 2015 (UTC)

I started phabricator:T106748 about this. Joe Filceolaire (talk) 22:41, 25 August 2015 (UTC)

Wikidata incremental dumps time lag

Hello, incremental dumps have 12 hour time lag. This lag confuses constraint reports users (for example: User talk:Ivan A. Krestinin#P1959) and makes his work less comfortable. Reasons that described on http://dumps.wikimedia.org/other/incr/ are not fully applicable for Wikidata project. Can this lag be removed or decreased for Wikidata incremental dumps? — Ivan A. Krestinin (talk) 10:21, 23 August 2015 (UTC)

@Hoo man: Can you answer this please? --Lydia Pintscher (WMDE) (talk) 12:53, 23 August 2015 (UTC)

@Lydia Pintscher (WMDE): Need I create task on Phabricator maybe? — Ivan A. Krestinin (talk) 20:11, 27 August 2015 (UTC)

Hmmm yeah that'd be great. Hoo is traveling so probably missed it here. --Lydia Pintscher (WMDE) (talk) 08:06, 28 August 2015 (UTC)

Search broken ?

It seems that some items that show up as prominent suggestions disappeared from search results. Sample: Special:Search/life doesn't show life (Q3). If you type "life" in the search box (interface language English), it comes up first. --- Jura 07:01, 26 August 2015 (UTC)

That's really weird. I opened phabricator:T110648 and hope someone from the WMF search team can check it out. --Lydia Pintscher (WMDE) (talk) 08:21, 28 August 2015 (UTC)

Esperanto Wikidata: Access to data from arbitrary items is coming

Esperanto

We will roll out this feature here on August 18. Is this date have changed ? Thanks. --Pino~eowiki (talk) 19:41, 26 August 2015 (UTC)

It has been postponed. It doesn't say on Wikidata:Arbitrary access yet what the new date will be. - Nikki (talk) 20:01, 26 August 2015 (UTC)

Badges

Another question. I see, that I can find out, does the article is featured, good etc. in XXwiki (see here in doc function "badges"), but can I find out, IF the article in SOME Wikipedia has some badge? Making some loop wouldn't be very good with Lua, I think. My use-cases:

update badges (the yellow background) here (API, Lua, javascript or anything else quite automated is OK)
find out, which articles about Latvia (so probably have something to do with Latvia (Q211)) have some badges in any of Wikipedias. In this case some of User:Magnus Manske tools (WDQ, Autolist or whatever) would be good, as in the first use-case. --Edgars2007 (talk) 09:12, 21 August 2015 (UTC)

User:Bene* is currently looking into a special page to get a list of all pages with a specific badge on a given project. Maybe something to start from. --Lydia Pintscher (WMDE) (talk) 10:29, 31 August 2015 (UTC)

RC variable did not display text

< ‎wbsetdescription-set:1|de: Gebäude des ehemaligen Institut International de Bibliographie> via https://www.wikidata.org/w/index.php?title=Q451&curid=675&diff=245962963&oldid=245779326 in _de:Wikipedia_ visible. Conny (talk) 06:50, 28 August 2015 (UTC).

Looks like it is fixed now (for me at least). Could you please check back yourself as this could be a per language issue (and I don't know what language you are using)! :) ·addshore· ^{talk to me!} 08:01, 28 August 2015 (UTC)

German works now. Regards, Conny (talk) 04:21, 31 August 2015 (UTC).

changes not showing up in Wikipedia watchlist

Hi, I just add a message about someone who was surprised to see a modification of Q42 on his watchlist because of one on my templates on a Project Discussion page on frwiki.

But for me and several users, just nothing is showing up, although the appropriate checkbox is checked in my user preferences of course. I did some tests and no Wikidata change seems to appear in my watchlist. It seems that longs for a long time. Is this a known implementation bug of watchlist integration atm ? author TomT0m / talk page 16:21, 28 August 2015 (UTC)

There can be two causes: You are using the extended watchlist which is not supported yet. Or the dispatch lag is too high and it takes too long for it to show up in your watchlist. We've had some issues over the last days with the latter but should be fine again now. --Lydia Pintscher (WMDE) (talk) 10:38, 31 August 2015 (UTC)

Linkouts on IDs don't work properly ?

My browser (Firefox 40.0.3 on Ubuntu, including in safe mode) fails to add hyperlinks to IDs (e.g. for property MSW ID (P959) at lion (Q140)). It only works after I (!) change languages. Reloading the page sometimes worked too, but not all the time and I wasn't able to understand why. (I couldn't find this bug mentioned anywhere.) Thanks, Tinm (talk) 19:12, 28 August 2015 (UTC) (update reloading Tinm (talk) 20:02, 29 August 2015 (UTC))

This is likely a caching issue. --Lydia Pintscher (WMDE) (talk) 10:39, 31 August 2015 (UTC)

Similar behaviour has been reported by a few people, but the discussions got archived, which might be why you couldn't find them, see Wikidata:Project_chat/Archive/2015/08#Links_are_gone and Wikidata:Contact_the_development_team/Archive/2015/08#Values.2Fqualifiers_displayed_in_irrelevant_properties for example. - Nikki (talk) 13:44, 31 August 2015 (UTC)