Fri, Jan 18
@KaMan Can you try again and let us know if you still encounter issues? :)
Thanks @Pamputt for the report.
Wed, Jan 16
Hello @deryckchan, and thanks for creating this task!
We're actually considering this for the year to come, but before starting developping anything, we need to understand better what people would like to do with the data, how they would like to display it on their wiki, what kind of Lua functions they would need.
If you already have some ideas, or use cases, feel free to share :)
So, here's the idea: we add in the code a way to identify the level of the constraints (mandatory or not). Then, people can add a line in their common.js to hide the non-mandatory constraints if they want to. We would also write this line for them. @Lucas_Werkmeister_WMDE Does it correctly summarize what we discussed about?
Tue, Jan 15
Mon, Jan 14
Mon, Jan 7
Hello to all the subscribers of this task,
I'd like to raise awareness on this consultation about issues encountered when requesting new languages in Wikidata. Since this is directly connected to the process that currently goes through creating subtasks here, I thought you may want to give your opinion before we try to address the issues. Thanks a lot for taking a bit of time for this :)
Thu, Jan 3
Wed, Dec 26
Task has been completed during the hackathon in Paris in December 2018
This task has been completed during the hackathon in December https://lingualibre.fr/wiki/Help:Create_your_own_lists#Generate_lists_from_queries
I created the task for the hackathon but we didn't work with Phabricator in the end, so I think this task can now be closed.
Dec 19 2018
Ouch. I guess we could start with adapting the width of the area to the length of the text, and increase the space between language and gloss.
Dec 16 2018
Dec 15 2018
Dec 13 2018
Deployed, announced, thanks for fixing this annoying bug \o/
Works after making an edit on the Lexeme page and purging the Commons page.
Tested on the sandbox on wikidata.org. The expected behavior (error message) happens correctly for properties of datatype string. However, for external IDs and monolingual string, no error message shows up, the publish link is disabled.
Dec 12 2018
Live, announced, works well \o/
I expected it to be deployed today. Just tried to test it on Luftballons but no change, maybe it's not deployed yet, or some pages need a purge?
It's deployed and it works well \o/ Example https://www.wikidata.org/wiki/Q6691
I think that @Ladsgroup's workaround is still in place on some items, like https://www.wikidata.org/wiki/Q5, can we disable it now?
Dec 11 2018
@Jan_Dittrich Would you have a creative idea to solve this problem?
Dec 10 2018
Any idea when it's going to be deployed?
@Michael I see, thanks!
Hey! I just tested it with Human and realized that the reference section is unfolded by default, with no possibility to fold it.
This is different from the behaviour of the non-protected pages, where the content of references is folded (which makes sense especially when the content is very long), and one can click on "X references" to expand it.
Can we make the reference section folded by default?
Dec 4 2018
OK, thanks. So there's no need for announcement for this ticket.
So if I understand correctly, the result of this ticket is not changing anything for users? ie it's not enabling arbitrary access on all Wiktionaries?
@Tarrow Could you give me an update on this? Is it already deployed, what's the final max length? Thanks :)
Now deployed and announced. Will do another announcement when the changes in editing mode are ready :)
Hey, I have a question, are all the Lexemes indexed already? Because apparently https://www.wikidata.org/wiki/Special:PagesWithProp?propname=wbl-forms&sortbyvalue=1 is not returning the Lexeme with the max number of Forms (it currently returns "dostatni (L21348): 84" when the Lexeme having the biggest number is atm mądry (L24242) with 140 Forms.
Just tested, I still encounter the issue when logged out.
If you don't mind I'll keep it open and in the Needs Announcement column until I make sure that it's live and announce it :)
Nov 29 2018
That's awesome, people will be happy. When will it be deployed?
\o/ When will it be live?
Nov 27 2018
Could it also be the cause of T210495 ?
Nov 22 2018
Nov 20 2018
@Lucas_Werkmeister_WMDE Could you draft something for the announcement?
Nov 15 2018
Oct 27 2018
@Vogone Because some of the words (form, sense) can be used both to define and to describe the data types, we decided to have them upper case. Otherwise the senses would not make sense if we keep this form, same for the forms :)
Oct 22 2018
Announced to the Wikidata admins
@Lydia_Pintscher Can be bring this to Camp soon?
Live and announced 👌
Oct 21 2018
It seems to happen again, example
Oct 19 2018
The issue was mentioned again here.
Oct 18 2018
@Addshore The thing seems to happen again with Senses. Some users ran into a "Handling of "wikibase-entityid" values is not yet supported." error message while adding the translation statement to a Sense.
Spotted another one: "add sense" link on a Lexeme page haz no capital
Oct 17 2018
It's live and announced
Hey @Nikki , this should be fixed on wikidata.org tomorrow. Let me know if you encounter other issues!
Oct 16 2018
Oct 12 2018
User:Jason.nlw told me that during the effected period, he was in the middle of a batch upload, and some data was not restored yet.
Tested here, it works well \o/
Tested here, it works well \o/
Tested here on L5-S3, it works! \o/
Oct 11 2018
Oct 2 2018
Oct 1 2018
@Addshore Could you have a look?
Sep 27 2018
@Jonas That looks good! I just reordered the paragraphs and changed a bit of formatting.
Later when the beta feature is enabled, we should probably add a section "how to enable it", just in case someone finds the page and wants to try it.
Sep 26 2018
Sep 19 2018
Sep 17 2018
@Addshore I just made an edit on L5600 and now it appears on Special:WhatsLinksHere. I guess for the oldest Lexemes, purging is not enough ^^