Wikidata:Contact the development team/Archive/2013/12

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

Property list limited to 1000

This page is showing only properties up to p999, when I try to search a higher range it just displays a blank page. Is it a bug or am I doing anything wrong?--Micru (talk) 18:40, 25 November 2013 (UTC)

The properties are sorted alphabeticly, not by number. The sorting order becomes: P10, P100, P1000, P1001 ... P1009, P101, P1010 ... -- Lavallen (talk) 18:51, 25 November 2013 (UTC)
It is quite confusing to enter "from P100 to P1039" and that it only shows from p1000 to p1039... at least that works...--Micru (talk) 18:55, 25 November 2013 (UTC)
Can one of you file a bug for a special page listing all properties in a sensible way please? We somehow need to solve this but I don't think Special:AllPages is the way to go. Will need to discuss this some more. --Lydia Pintscher (WMDE) (talk) 13:44, 2 December 2013 (UTC)
Done, I think a good way to improve property lists would be to base it on the correction of bugzilla:49554.--Micru (talk) 15:58, 2 December 2013 (UTC)
This list can help maybe. It is sorted by property identifier by default. — Ivan A. Krestinin (talk) 17:29, 2 December 2013 (UTC)

My suggestion about site link to redirect page and red link

@Lydia Pintscher (WMDE):

  • Redirects should still be bypassed if possible (i.e. no item is linked to the target), because most of redirect link adding isn't on purpose, and should be bypassed;
  • We need 2 (or probably 3) types of sitelink, which we should have only one of two (three) kind in a language usually: one is common sitelink and the other is redirect sitelink; (I have purposed the third kind of sitelink: red sitelink, which can migrate internal link helper which was mostly used in zhwiki)
  • Redirect sitelink are possible as rare links may exist. However, because of most of redirect link should be bypassed, if someone is adding a redirect link, a notice like "The page you're linking is a redirect. bypass the redirect or still adding?" should be shown, and if someone moves a page links to a common sitelink, Wikidata page should still be updated.

--GZWDer (talk) 15:05, 1 December 2013 (UTC)

Verified statements

Hi! Could you please check this conversation? It would be interesting to know if it is something that the wikibase software could manage, or if we should seek for a "hackish" solution with a gadget+properties.--Micru (talk) 15:49, 28 November 2013 (UTC)

The system I am refer to in Wikisource has 5 levels. 0 - No content or no need of proofreading. 1 - Not proofread. 2 - Problematic (uncomplete or have to be discussed). 3 - Proofread once. 4 - Validated i.e. proofread by at least two users. I can imagine that we could have use for all of these, except for number 4. The username is stored, so that the same user cannot change from level 3 to 4, and policy tells that bots, ips and alternative accounts are normally not allowed to change these levels. -- Lavallen (talk) 16:26, 28 November 2013 (UTC)
I can imagine having something like that in the future but looking at the todo list I don't see this happening before end of next year. So having some interim solution is probably a good idea. --Lydia Pintscher (WMDE) (talk) 16:29, 28 November 2013 (UTC)
They want to introduce the flagged revisions system used on de:WP ??? Snipre (talk) 11:40, 29 November 2013 (UTC)
I don't think so, rather a system to make it easier to see if somebody has verified that the statements added by bots, really is what the sources tells. Flagged revisions would not solve that for us, since bots are immune to flagged revision. -- Lavallen (talk) 12:09, 29 November 2013 (UTC)
@Lavallen: the software could be configured so that only (auto)confirmed users, bots excluded, could verify edits. --Ricordisamoa 01:06, 5 December 2013 (UTC)
Partly yes, I doubt it can exclude all kinds of unflaged bots. AFAIK, on Wikisource it's policy who excludes bots to verify pages, not the software. -- Lavallen (talk) 07:48, 5 December 2013 (UTC)

Searching Q-Numbers

If I search for a Q-Number like Q6038179 I don't get a result now. --Succu (talk) 21:53, 3 December 2013 (UTC)

Where are you searching for this? --Lydia Pintscher (WMDE) (talk) 21:56, 3 December 2013 (UTC)
I'm using the search box placed right at the top of the page. No drop down appears. There are more UI issues I think. --Succu (talk) 22:07, 3 December 2013 (UTC)
Ok confirmed. Did this work for you before and is now broken? (Or is this a feature request?) If the former it probably broke because of today's deployment and I need to have someone investigate. --Lydia Pintscher (WMDE) (talk) 22:05, 3 December 2013 (UTC)
It's broken now. --Succu (talk) 22:07, 3 December 2013 (UTC)
Work for me (IE 11/Chrome + WIN 8.1) --ValterVB (talk) 22:08, 3 December 2013 (UTC)
Hmm working again for me too now. Might just have been a clitch during deployment? --Lydia Pintscher (WMDE) (talk) 22:13, 3 December 2013 (UTC)
I'm pasting the value into the box. But yes, it seems to work now. --Succu (talk) 22:17, 3 December 2013 (UTC)
We have bugzilla:57983 now for the paste issue. --Lydia Pintscher (WMDE) (talk) 10:41, 5 December 2013 (UTC)

Access of the full precision in datetime datatype

Hi, currently the web interface does not allow to enter fully what is known about an uncertain date, precisions are limited to a few possibilities. When/can we expect to be able to access the full range ? (The question has been asked on wd:bistro when people did not know the datatypes allowed to enter what a user wanted to do, and people seemed to search an alternative solution). A code contribution would be accepted ? TomT0m (talk) 11:00, 4 December 2013 (UTC)

Hey Tom. I can only give you an unsatisfactory answer at this point: I don't know when we'll get to it. If someone else wants to work on that that would be great but this would need coordination/design documents to make sure it fits in with the rest. --Lydia Pintscher (WMDE) (talk) 11:08, 4 December 2013 (UTC)
Other question then, can the API handle the bounds atm ? If I try to code a gadget, will I be able to store the bounds in the database, and more importantly, how will this be displayed in the front end ? Maybe a first step would be to patch Wikibase to be able to display different kinds of informations if it's not possible now. TomT0m (talk) 12:15, 4 December 2013 (UTC)

Q14269834 is deleted but do not appear as deleted in statements

see Q14269890. I have cleaned the cache.--GZWDer (talk) 14:46, 4 December 2013 (UTC)

Thanks. Will have a look. --Lydia Pintscher (WMDE) (talk) 10:43, 5 December 2013 (UTC)

Problem XML on test.wikidata after new deployed

Api request: /w/api.php?action=wbgetentities&format=xml&ids=Q16 result in

<?xml version="1.0"?>
<api servedby="mw1017">
  <error code="internal_api_error_MWException" info="Exception Caught: Internal error in ApiFormatXml::recXmlPrint: (en, ...) has integer keys without _element value. Use ApiResult::setIndexedTagName()."  xml:space="preserve" />

Work with json format. --ValterVB (talk) 20:12, 6 December 2013 (UTC)

Thanks so much for testing this continuously and reporting issues. We'll look into that one. --Lydia Pintscher (WMDE) (talk) 20:50, 6 December 2013 (UTC)

sitelinks to non-Wikimedia sites

I think it has already been discussed but I have forgotten the conclusion (if any) :(. Is there any chance that we can some day replace properties like VIAF ID (P214) with sitelinks. They seem so much more suited for that, and presumably, it would also improve performance, as we could move a substantial part of some items from properties (somewhat complicated) to sitelinks (apparently much more lightweight). --Zolo (talk) 10:11, 7 December 2013 (UTC)

Hey :) It is not off the table. I have to be honest though. It's not particularly high on the priority list right now either. Queries, quantities and so on are bigger fish to fry first. Lydia Pintscher (WMDE) (talk) 10:21, 7 December 2013 (UTC)

Wikidata and Wikinews

Russian Wikinews decided to integrate with Wikidata. Primarily we are interested in cross-project linking. We need a "curator" from Wikidata who will help do it. My English is bad, but I will do everything else that is necessary. --sasha (krassotkin) 14:06, 8 December 2013 (UTC)

Wikinews is on the list to do, just not in the near future. The next we're going to integrate is Wikisource. Be patient. :) --Izno (talk) 16:26, 8 December 2013 (UTC)
I think the point was that the English Wikinews were discussing this for a month and could not decide whether they need the integration (and they can very well discuss it for another year), whereas the Russian Wikinews are clearly interested and are willing to help on their side.--Ymblanter (talk) 16:37, 8 December 2013 (UTC)
It's a little early either way, unless you can think of something that would help prior to integration that they can do? --Izno (talk) 17:03, 8 December 2013 (UTC)
Right, I just look at it as a message to Lydia and developers that the Wikinews integration should be kept on plans despite the inconclusive discussion on en.wn (where Lydia participated as well). Also I guess it would be a good idea to open a task force and to discuss the wishes of the Wikinews communities - what do they expect specifically.--Ymblanter (talk) 17:15, 8 December 2013 (UTC)
Wikinews may be next? What is the schedule? What can we do to speed up this process? --sasha (krassotkin) 17:13, 8 December 2013 (UTC)
Ymblanter's suggestion is good. Start a page for Wikinews at Wikidata:Sister projects. Lay out how you think linking should work between the different Wikinews editions for the namespaces used. Make a list of people who could be ambassadors for the individual language editions. List a few things where you consider Wikidata most useful beyond interwiki links. Having this put together would be great and would make me push Wikinews up the list. Next however is Wikisource as already mentioned. Lydia Pintscher (WMDE) (talk) 21:56, 8 December 2013 (UTC)
(WD:Wikinews). --Izno (talk) 23:54, 9 December 2013 (UTC)
Thanks! Done. What next? --sasha (krassotkin) 11:44, 10 December 2013 (UTC)

My advice would be to go leave a note on the other language Wikinews pages that they might want to add to the Wikidata page. I think starting an RFC here might be premature though.

I am going to make a note that I don't know that the "categories <-> articles thing" is going to happen, as there was a rather strong opposition to that in the Commons RFC that just completed. From what I understand there are Javascript implementations which handle that... --Izno (talk) 13:57, 10 December 2013 (UTC)

Moving a statement to the bottom

You can do this, but after reloading the page you can see the statment was not really moved. --Succu (talk) 11:46, 11 December 2013 (UTC)

+1. I think this is again a flaw in combination with the authority control gadget. If the gadget is disabled, you can save the claim after moving. Then, the change is permanent. With activated gadget, clicking "edit" once lets you move the claim but not save it.  — Felix Reimann (talk) 13:28, 11 December 2013 (UTC)
Yep. If I deactivate AuthorityControl (again) moving to the bottom of statements works. @Henning (WMDE):... --Succu (talk) 19:45, 11 December 2013 (UTC)

Problem with absolute ages of geologic periods

Has anybody reported the bug yet, that the date-datatype does not allow decimal places and no margin of error? I tried adding the start and end date of the Mississippian (Q744718), 358.9 ± 0.4 and 323.2 ± 0.4 Ma. But when choosing a hundred million years, I can't add decimal places and error margins are not recognized by the UI. Not high priority, but should be fixed. --Tobias1984 (talk) 09:05, 9 December 2013 (UTC)

For the decimal part why not just use the next smaller period and write it out? And for the margin error: You mean you can enter it when using million years but not hundred million years? --Lydia Pintscher (WMDE) (talk) 13:30, 9 December 2013 (UTC)
Does the date-datatype even take error margins? I tried it a number of ways and it doesn't work. I entered the value now at Mississippian (Q744718), but the formatting is not really ideal for geologic time scales. There is also a problem with the trailing zeros, because they are mathematically meaningless, but in metrology they are signficant digits, and make the measurement look far more precise than it is. Example: You find an Roman artifact and date it to 300 BCE. If the method is precise to the year then the right-most 0 is the significant digit of measurement. You can't abbreviate it to 3x10^2 BCE, because that would look like 3 is the significant digit. --Tobias1984 (talk) 14:48, 9 December 2013 (UTC)
I think one problem is that the GUI shows only the first comma separator between the one hundreds place and the one thousands place. The others, before million and billion, are not shown. I added per API end time (P582) to Mississippian (Q744718) with the following snak for time:
{'after': 4, 'precision': 4, 'time': '-00298900000-01-01T00:00:00Z', 'timezone': 0, 'calendarmodel': '', 'before': 4}
If I understand the API documentation correctly, this should exactly state 298.9 ± 0.4 Ma, or? Unfortunately, the year is shown as "298900,000" instead of "298,900,000" and also the error margin is missing. Both are only GUI problems, as the data is stored correctly: [1] Do I understand the usage of time datatype right? Best would be, of course, if the GUI would repect the precision and display "298.9 million years ago".
@Tobias1984 You did not set before and after, which represents the margin error. Currently, you cannot set this using the frontend. Only works with using the API (or, pywikibot).  — Felix Reimann (talk) 09:54, 10 December 2013 (UTC)
Thanks for the explanation. I will just wait for the UI to be expanded. Someday I might even try to learn how to work a pywikibot. --Tobias1984 (talk) 10:39, 10 December 2013 (UTC)
@Lydia Pintscher (WMDE): I did not find a bug report related to the missing commas. Shall I create one or is this only an already known flaw in the "time ui"-complex?  — Felix Reimann (talk) 20:58, 11 December 2013 (UTC)
No it'd be great if you can create one. Then it doesn't get lost and one of the developers can have a closer look at it. Thank you! --Lydia Pintscher (WMDE) (talk) 08:23, 12 December 2013 (UTC)
Done.  — Felix Reimann (talk) 11:51, 12 December 2013 (UTC)

Computer freezes

I know that it was planned to improve somehow the performance, but right now it has worsened. Even items with a few statements freeze my computer and throw the Mozilla's "unresponsive script error". Is there anything that I can do to disable certain features to improve the load time? --Micru (talk) 13:17, 11 December 2013 (UTC)

This problem breaks Wikidata. Lydia, help! Emw (talk) 13:38, 11 December 2013 (UTC)
Also confirming this. I can not visit most of the item's pages atm. -- Bene* talk 14:16, 11 December 2013 (UTC)
Yes we're aware of it and working on fixing it. Sorry :( --Lydia Pintscher: (WMDE) (talk) 14:23, 11 December 2013 (UTC)
Does a bug/ticket exist for that? --Bene* talk 14:45, 11 December 2013 (UTC)
No. We're all sitting here trying to fix it asap. In the meantime Chrome and Opera seem to be better than Firefox. Sorry for the problems :( --Lydia Pintscher (WMDE) (talk) 15:16, 11 December 2013 (UTC)
Even with Chrome pages with a couple more statements are terribly slow to load try Kaiserslautern or Berlin, they take > 15 seconds for me, which is repeated on every single save! If you need a javascript profiling run in chrome let me know. Joern (talk) 21:53, 11 December 2013 (UTC)
Yeah it's just less bad in Chrome... :/ The current status is that we will turn sorting off again if we don't find another fix until 18:00 Berlin time today as I already posted on Project chat. --Lydia Pintscher (WMDE) (talk) 08:26, 12 December 2013 (UTC)

Exception Caught: Specified index is out of bounds

I frequently get the message: "Exception Caught: Specified index is out of bounds" when I try to save a new statement. -- Lavallen (talk) 09:17, 11 December 2013 (UTC)

Are you editing via the website or the API? --Lydia Pintscher (WMDE) (talk) 09:54, 11 December 2013 (UTC)
It's in an orange box in the GUI (the same box who sometimes tells me about edit conflicts or lost edit sessions). -- Lavallen (talk) 09:57, 11 December 2013 (UTC)
Ok thanks. Did you simply add a statement or also change the position of one? Can you link me to an item and edit this happen on? --Lydia Pintscher (WMDE) (talk) 09:59, 11 December 2013 (UTC)
Playing with the new UI feature I got this message too. With AuthorityControl off my scenario was: 1) moving a statement to the bottom, 2) save it, 3) error message appears, 4) Cancel, 5) reloading the item, 6) statement was moved down by one postion, 7) moving the same statement to the bottom, 8) save it => no error message. Hope this helps. --Succu (talk) 20:03, 11 December 2013 (UTC)
I overlooked a little detail: in all my cases I added statements first and then moved an existing one. Before this edit the only statement was P18. The new statement was added as the topmost. So the index of P18 changed. :( --Succu (talk) 20:26, 11 December 2013 (UTC)
Thanks! That's very helpful. --Lydia Pintscher (WMDE) (talk) 08:25, 12 December 2013 (UTC)
bugzilla:58394 for further tracking of this. --Lydia Pintscher (WMDE) (talk) 15:06, 12 December 2013 (UTC)
To me, after I got this message, I reload the page and the statement is suddenly in the top of the page. -- Lavallen (talk) 11:51, 13 December 2013 (UTC)

Utilisation données wikidata

transféré depuis Wikidata:Bistro Ljubinka (talk) 22:42, 12 December 2013 (UTC)

Bonjour, wikivoyage utilise les données de wikidata en particulier les coordonnées des lieux et les liens vers wikipédia. Tout a bien fonctionné durant plusieurs mois lorsque tout à coup hier, les système a cessé de fonctionner. Aucun changement de code n'a été effectué (voir Module:Basic et Modèle:Latitude par exemple). Quelqu'un a t'il une idée? Un spécialiste en Lua peut il y jeter un coup d'oeil ou dois je directement écrire un rapport de bug sur bugzilla? Je précise que sur wikivoyage en portugais on m'a rapporté un problème similaire.--Adehertogh (talk) 20:33, 12 December 2013 (UTC)

Translation: Hello, Wikivoyage in french uses data from Wikidata in particular the coordinates and links to Wikipedia. Everything worked well for several months when suddenly yesterday, the system stopped working. No code change has been made (see for example: Module:Basic and Modèle:Latitude). Someone has an idea? Could a specialist in Lua take a look or should I write a bug report on bugzilla? I have heard that on Portuguese Wikivoyage there is a similar problem.--Adehertogh (talk) 06:27, 13 December 2013 (UTC)
Thank you for the translation. We fixed a very nasty bug with that last night. Can you please see if that fixes it? You might need to purge the page. --Lydia Pintscher (WMDE) (talk) 07:31, 13 December 2013 (UTC)
It works thanks... a lot!--Adehertogh (talk) 08:01, 13 December 2013 (UTC)

Edit interface should fall back to foreign languages for label

Sometimes you don't have a label for an entity in your interface language. In this case the entity seems to have no label to noobs like me, even though it actually might have a label, just in a different language.

IMO it would be helpful if the UI would present labels from other languages with a greyed out checkmark behind it. If the user hovers over the checkmark, it could explain which language the label is from and ask if she wants to approve it for her main language. As there might be several labels from other languages it might make sense not to show them all, but for example the 3 most common ones over the different languages and then a drop down arrow for more.

(I know about the labels list ui extension, but that seems way more complicated this "one click".)

What do you think? Joern (talk) 15:09, 12 December 2013 (UTC)

Yes we need language fallbacks. Parts of that was worked on during a Google Summer of Code project last summer. Still needs quite a lot of work though. --Lydia Pintscher (WMDE) (talk) 15:12, 12 December 2013 (UTC)
cool. Just an example which i forgot :-/ Q1604171 Joern (talk) 15:33, 12 December 2013 (UTC)
+1. Helder 14:04, 13 December 2013 (UTC)

I wrote an altLabels.js script as a proof of concept. If you're viewing an item for which there's no label in your current language it will insert the 3 most common labels across other languages below the input box. A simple click on one of them will approve & submit it for the current user language. The proof of concept currently isn't localized. Joern (talk) 02:15, 14 December 2013 (UTC)

Redirect issue

Surely this issue has already been discussed somewhere here and I must have probably missed it, but anyway, can someone tell me whether the problem, that the interwikis don't appear if redirect is used, is known and is there a solution to be expected. This is perhaps one of the severest drawbacks of wikidata, since inexperienced users following redirects may decide that there are no interwikis at all. --David.s.kats (talk) 22:56, 12 December 2013 (UTC)

Not sure if I understand you correctly: ru:Vipera berus is a redirect to ru:Обыкновенная гадюка. Nonetheless, when I click on the first link, I am redirected to Обыкновенная гадюка and this page also shows the interwiki links. Besides the message "(перенаправлено с «Vipera berus»)" there is no difference.  — Felix Reimann (talk) 10:10, 13 December 2013 (UTC)
Now it works. I don't understand why I didn't get the same result with the article ru:Спички some days ago. Following this redirect I've been redirected to ru:Спичка without any interwiki links. --David.s.kats (talk) 17:22, 14 December 2013 (UTC)
Two days ago, we had severe problems due to software malfunctioning. The apparent absence of interwiki links may be related to this issue. From what I see, now they are fine.--Ymblanter (talk) 17:54, 14 December 2013 (UTC)
David, could you please explain in more detail what you mean.--Ymblanter (talk) 19:44, 13 December 2013 (UTC)
I was just trying to understand why the interwiki links sometimes appear when a redirect is used and sometimes don't, see above an example with ru:Спички. --David.s.kats (talk) 17:22, 14 December 2013 (UTC)
David: The only time sitelinks to redirects are used in Wikidata is when the main wikipedia article already has a sitelink to a different wikidata item. This is the 'Bonnie and Clyde problem'.
Some wikipedia have articles about 'Bonnie and Clyde'. Others have separate articles about 'Bonnie Parker' and 'Clyde Barrow'.
All the articles about 'Bonnie and Clyde' are linked to the wikidata item for 'Bonnie and Clyde'.
All the articles about 'Clyde Barrow have sitelinks from the wikidata item for 'Clyde Barrow'. This item can also have sitelinks to redirect pages titled 'Clyde Barrow' wihch redirect to a 'Bonnie and Clyde' article.
This means that articles about 'Clyde Barrow' can have sitelinks to articles about 'Bonnie and Clyde' via redirects.
For this to work in reverse you need to have a redirect from 'Bonnie and Clyde' to 'Clyde Barrow' on those wikipedias which don't have a 'Bonnie and Clyde' article and a sitelink to this from the 'Bonnie and Clyde' wikidata item.
If the language wikipedia decide to change the 'Bonnie and Clyde' redirect to redirect to the article about 'Bonnie Parker' then 'Bonnie and Clyde' articles in other languages will link to the article about 'Bonnie Parker' in this language, via that redirect.
Most likely they will decide 'Bonnie and Clyde' should not be a redirect page and we get the situation you describe above, with no link in the reverse direction.
Hope this helps. Filceolaire (talk) 22:25, 13 December 2013 (UTC)
Thank you for the detailed answer. I actually meant a simple technical issue that the interwiki links don't always appear if a redirect is used. The problem which you describe is although a severe one, but it is not caused by the wikidata in my humble opinion, as such semantic collisions can occur between any two languages and with any connections. In ruwiki we have a special page devoted to such problems. --David.s.kats (talk) 17:22, 14 December 2013 (UTC)

Featured articles

Maybe Wikidata team is innocent but is better to ask :) On wiki Template for Featured articles (en:Template:Link FA) don't work (see en:Roger Federer for an example). I know that Wikdata badge is near to be complete, so is possible that something of wrong it was deployed with last update on Wiki? --ValterVB (talk) 19:09, 13 December 2013 (UTC)

We should not be touching those templates in any way, no. --Lydia Pintscher (WMDE) (talk) 19:53, 13 December 2013 (UTC)
ValterVB, this was caused by gerrit:94899. See also w:en:MediaWiki talk:Common.js#LinkFA is broken and how the script was fixed on viwiki. (talk) 11:24, 18 December 2013 (UTC)

Item by Label ?

Hi, the special page ItemByTitle is useful, but what to do if the item is labelled in our target language, but has no Wikipedia article ? A special page Item by label would be a good thing in those cases (of course the label is not always unique so it is a problem, and not always stable either ...), to have something to link, to use with a lot of caution. TomT0m (talk) 13:46, 15 December 2013 (UTC)

Would special:itemdisambiguation help? Maybe I misunderstand your suggestion. Matěj Suchánek (talk) 13:57, 15 December 2013 (UTC)
Absolutely, would be perfect with a redirection to the item page if there is no ambiguity. TomT0m (talk) 18:03, 15 December 2013 (UTC)

Maximum number of values in wbgetentities

After yesterday deployment "Maximum number of values in wbgetentities" is changed from 500 to 250 200 (for bot) Is a bug? --ValterVB (talk) 18:35, 12 December 2013 (UTC)

@Addshore: --Lydia Pintscher (WMDE) (talk) 07:32, 13 December 2013 (UTC)
Looking into it now! What error message do you get? ·addshore· talk to me! 10:52, 13 December 2013 (UTC)
:@Addshore: The error message is: 500 - InternalServerError, sorry I haven't other details. If you need string, you can found it on pasteall. --ValterVB (talk) 17:48, 13 December 2013 (UTC)
I don't believe the limit has been changed. If you were hitting the limit the request would not run and you would get the standard API error message with a code and a string. This seems like something else is breaking. When I run the query I get no response! ·addshore· talk to me! 22:55, 13 December 2013 (UTC)
Yes, no standard message, only Internal server error. Is changed something in API, because my framework is always the same, I have tried with "HttpWebRequest" with C# and with Visual Basic but the response is always the same. Some developer can check the problem? --ValterVB (talk) 19:42, 20 December 2013 (UTC)
In the same time, without a bot flag, I can query 131 items succesfully, while the API documentation says the limit should be 50. If I query 132, I get the normal error message, and if I query 140, I get the Internal Server Error. --YMS (talk) 12:54, 21 December 2013 (UTC)
Ehm, no, what I just called the "normal error message" (that I get for a query with 132 to about 139 items) also is the internal server error message, but for some reason, when called via a browser, it displays the HTML code. --YMS (talk) 13:00, 21 December 2013 (UTC)
I have added to bugzilla. Is my first submit so I hope is correct. --ValterVB (talk) 14:22, 21 December 2013 (UTC)

CSS classes for edit summaries

If I understand right, the first part of all or most of the edit summaries for edits on items and properties are auto-generated. Is this done once per edit or on demand every time a list of recent changes, contributions etc. is built? In the latter case, I think it should not be a big deal to also add a css class dedicated for that type of edit (added/changed/removed, label/description/alias/statement/sitelink, etc. ... maybe even which language was affected). I guess it could be of benefit if a user had the chance to visualize those different types of edits in different colors, or even filter them by a little script. E.g. when patrolling recent changes for vandalism, I hardly care about edits that add sitelinks while changing a claim has a high potential of being vandalism, but chances are that I miss that edit between all those that I don't care for. So would that be possible? --YMS (talk) 13:18, 18 December 2013 (UTC)

I don't know if there would be any technical issues with making this happen. If not we can probably do this. I've filed bugzilla:58716 for it. --Lydia Pintscher (WMDE) (talk) 21:50, 19 December 2013 (UTC)

Get Babel information

While a user's babel boxes are quite important for Wikidata's own GUI, there is no direct way for a user script getting this information. If I did not miss something completely, I have to do this by checking the existence of the "In other languages" boxes on an item/property page or by loading the user page via the API and extracting e.g. the babel categories, but even though Wikidata itself obviously already makes use of that information, there is no way to get this information from any of the mw object's functions or a direct API call. Is this on purpose or just because nobody cared yet? --YMS (talk) 13:27, 18 December 2013 (UTC)

I am not sure if this isn't currently possible in a better way. I am hesitant to put work into this right now though because in the future the universal language selector should store and provide the list of languages a user speaks. I am not sure where this is on their roadmap though. --Lydia Pintscher (WMDE) (talk) 21:52, 19 December 2013 (UTC)

Specified index is out of bounds

I keep getting a very strange error, but it seems to be consistent. For the second day in a row, I manually add data to the articles on administrative divisions of Kyrgyzstan (yesterday) and Kazakhstan (today). Do not ask me why, it is irrelevant. I open a new page (for example, the last one was Q485437). Then I remove P107 entry as deprecated, add manually P36, and start adding entries P47. At exactly third entry of P47, does not matter what, I get an error saying "Exception Caught: Specified index is out of bounds". Trying to add the same or different entry again does not help. Reloading always helps. So far, I never had to reload twice (I mean the 4th and 6th entries are no problem). I use FF (the latest version) and Windows. Really strange, never had it before, but by now my statistics is over 10 entries.--Ymblanter (talk) 20:01, 25 December 2013 (UTC)

I've received the same error message on two occasions, but as you say, reloading helps. - Soulkeeper (talk) 22:56, 25 December 2013 (UTC)
This looks like bugzilla:58394. --Lydia Pintscher (WMDE) (talk) 13:15, 26 December 2013 (UTC)