Apr 15 2021
Apr 12 2021
A bit more high level .... in my opinion there should be something like a global variable in the docker where one can set the public url. This should the automatically set for example:
$wgServer = "https://PUBLIC_URL"; (in the Mediawiki installation)
and also the prefix in the sparql endpoint .....
(and all the other places where it is needed)
just a suggestion ; )
@Dhairya3124 Look good and very complete! It's fine like this.
Apr 9 2021
Thank you for the pointer. Aftre checking I agree I was wrong. One has to set prefixes.conf like this:
For anyone running in this issue. The config can be done in the blazgraph container by editing this file:
Mar 29 2021
: ), it's a bit a hack .... I installed Kartographer as it is, then you have to replace the server that gives you back the tiles with a public one and not the wikimedia one. I changed some lines in the plugin, but I do not remember. So you can try to do the same. In any case you can support this ticket:
I confirm, this is solving the issue! I will make a pull request to the docker images
Mar 25 2021
Sorry guys, we are slightly lost with the Wikimedia workflow. It is also for us the first time ; ) We will try to organise a bit better and come back to you. Anyway, we are happy if you apply for this project and we would love to work with some of you on this cool project!
Mar 14 2021
Mar 11 2021
If you see above, a student already tried the first steps. Maybe you can start from there if you are interested .... we will have to organise a bit for the selection process though ....
Mar 5 2021
ok, working! thank you!
II used this patch:
@Xqt: so one bug is gone, i.e. the configuration file is taken into account:
If you explain me how to test it, I will do. How to I download the code with the latest commits?
@Xqt: it is this commit -e git+https://github.com/wikimedia/pywikibot.git@083ed9341881f562167e732974df35ee051ba994#egg=pywikibot, so it is not even a version ....
Mar 4 2021
any news on this issue? I tried again and I'm really stuck. Basically I think that the current code/documentation for pywikibot on a third party wikibase are not wokring. Could you test?
Feb 25 2021
looks good! but I must admit that I never did it ; ), installed many other extensions though ; )
Feb 24 2021
so .... I think the documentation here:
starts from the fact that there is only the media wiki installation. But you have multiple containers. So you have to go into the one where the mediawiki instance is running:
Hi, this looks normal, the wikibase is empty, when you set it up it is a fresh emtpy install ....
But besides that, what would you like to do?
Feb 23 2021
no, this is the github repo for setting up mediawiki + wikibase ... so basically the infrastructure you need to develop the plugin .....
Feb 22 2021
@Bavisettinarayan hi, I'm not totally sure what installation guide you are following. But I would recommand you to take this docker container:
I set it up multiple times myself. The instructions are here:
Once you are done you should have a fully mediawiki + wikibase environment.
Next step should be to install this extension:
Hope it helps!
Feb 19 2021
yes we are aware of the timeline and the mentor guidelines ...
Jan 12 2021
thank you and sure I will
Moving the issue with the image to T271860
No problem, would be nice if you could look at that though : )
No the problem are the images from wikimedia commons! They are not rendered ....
No wait ... the problem is with the image, not the map, for the map I have a Kartographer issue! But you said the image would render, but it does not ....
Jan 9 2021
Oh, I think I found a related issue:
thank you for the quick replay! This is not set. I didn't know it was existing. I was aware only of the configurations detailed here:
I was able to successfully deploy 1.35. The problem with the image remains. See for example:
I tried it again .... I confirm what you suggested. Additionally to the documentation here:
Dec 30 2020
Nov 24 2020
Hi, yes we downgraded again ..... yes we run update.php on 1.35. The setup is the wikibase-docker setup. We also tried to force reindex .... then strange thing was that when we had both instances 1.34 and 1.35 running then in 1.34 type as you search was working while 1.35 not. Do we maybe need also to update other docker images?
PS: I hope this helps to set up a new migration guide
Nov 20 2020
I upgraded my instance from 1.34 to 1.35 following:
I just installed 1.35 but the images do not seam to be rendered. For example this item:
Oct 20 2020
Thank you for the answer, and thank you for the Project-Chat pointer
Oct 18 2020
Oct 8 2020
@Bugreporter Perfect!!!!! That is what I was searching for! Merci!
Oct 7 2020
Oct 4 2020
so as far I can see this plugin is not integrated into wikibase containers yet. I tried to install it manually. I followed the instructions here:
Aug 24 2020
Ah, good to know ..... thank you! But it is still a bit weird. I would have expected that the variable name matters. I leave it to you to decide to handle it as a bug or not ...
Jul 26 2020
Jul 23 2020
Jul 9 2020
Cool, but what is the link?
May 28 2020
May 6 2020
Yes, this did it! After reindexing I get:
finally I find time for this ......
Apr 22 2020
I'm sorry for taking so much time, I didn't forgot this ... it is only that I'm working on many different things .... on Friday or next week I will be again on this .....
ok, thank you!
I think we will wait for the next release, even if the features are nice they are not essential.
Apr 8 2020
Kartographer, is not a problem, we installed it separately ... the problems are:
Apr 6 2020
yes the bundle for 1.34 exists. But the two features I was describing above are not in 1.34, they are only in latest as far as I know. So the question is how/if we should move to latest ....
Apr 2 2020
Mar 24 2020
thank you! It helped!
Mar 23 2020
Thank you very much for these insights!
here is the size of the biggest tables in Mb
Mar 21 2020
Mar 12 2020
We solved the problem by recreating a new account and a new consumer. So this seams to be a bug on Wikimedia side. If someone runs into the problem he can try to make the same. Thank you for the support!
Mar 10 2020
@Tgr: we made a further experiment .... if we select "This consumer is for use only by DD063520." then we get directly access and verifier tokens. With these the code works ....
@Tgr, could you help us out with this?
Mar 6 2020
@Tgr could you find time to check?
Mar 5 2020
@Tgr Hi, I just made a request at 08:03 Paris time .... could you check .... the consumer is:
Mar 4 2020
I published the code here:
yes the user info is correct. The consumer is this one ....
Would it help if we share some minimal code for the functionality we want, so that someone can debug it with an own consumer? But without seeing what is happening on the server side I'm not sure how we will solve the problem .....
Mar 3 2020
mhmmm, so what to do?
I'm not able to fix this ..... the token is for example
this is the consumer:
Feb 19 2020
is this export (dump) available to download somewhere? Is this planned? Should I add an additional ticket for that?
Feb 14 2020
No, problem .... there is still time to do it ; ) ..... I see what @thiemowmde means. But I'm not sure if I can implement this. The problem is that there can be precision problems if it is done as I propose, right?
I think I found a patch. We can changes this https://github.com/wikimedia/pywikibot/blob/2dfe67426c22c3c11cf9be0eabcf538f8848bd48/pywikibot/__init__.py#L847:
I'm also encountering this. I also saw that it is related to this:
I'm encountering the same problem. I also have seen that this is related to this:
Feb 13 2020
Hi, when this is ready I'm eager to test it. I imported the properties I need from Wikidata with the corresponding constrain properties, e.g.
could you indicate the process to upgrade the current version wikibase/wikibase:1.33-bundle in the docker-compose setting to the master branch. This way I can try out the new feature. I read this: