Fri, Jan 17
Mon, Jan 6
Tutorial is perfect! You can close this .....
Sat, Jan 4
Ok, I got it. I just removed the alias from the wikibase instance. This way he is passing through the "real internet" where the certificate is exposed and not over the internal network. Thank you very much for the support!
I was able to fix the above and to reload the data in the query service as described in:
I understood a bit by chance when this error appears. In my case I was modifying some configuration in the LocationSettings files and I used wrong syntax. Then the Wikibase instance is broke and the APIs do not replay correctly anymore causing this error.
Fri, Jan 3
Ok, this is related to this:
If I set the variable now I get the following log:
Sorry, the error above was quite clear .... the mistake was:
Here is the full log:
I understand that the updater is considering the wrong URL, but should that not work by only setting the environment variables in:
Dec 21 2019
Yes, I mean the image previews
Dec 20 2019
Sorry for pointing again on this .... in fact also another main feature is not working due to this. It is not possible to add manually new statements to items.
So currently we are in the following situation:
- either we have a running SPARQL endpoint, or
- the search and adding statements is running
Both are really important and not just some optional features or minor bugs.
Could you please prioritise this.
Cool thank you!
Dec 19 2019
Ok, this works out! Thank you!
I tried to debug a bit more and I can confirm. If I set:
Dec 17 2019
Dec 14 2019
Dec 10 2019
Perfect! Thank you!
Hi I guess the mistake was that the change has not to be done in the:
Mhmmmm ..... still not working somehow, I do:
thank you for you answer! Unfortunately I do not get it fully. In different places it seams that the configuration is slightly different. I now put:
Dec 8 2019
not sure if this is the right place, hopefully yes!
Nov 15 2019
Ahhh, my mistake, ok, fine for me. I saw that you opened this:
So for me we can close this one.
Thank you very much for the help!
Mhmmm .... on github I cannot find the "ban" language in the wikipedia_family:
yes, I did:
Mhmmmm, I use this version of Pywikibot: pywikibot-3.0.dev0
could that be the problem?
Nov 14 2019
@Xqt : hi, would you consider again this patch, currently I make this modification locally to have some code running
Nov 5 2019
ok, cool, I try to go through it until the end of the week and give you feedback! Merci
Oct 29 2019
When importing the sitelinks of Earth I get a similar problem:
I reduced it down, apparently the language code that makes problems is:
Oct 28 2019
Ok, thank you! I will try it out.
ok, I understand the problem. I'm currently changing the host by going inside the wikimedia docker instance and manually editing the LocalSettings.php file. Can you explain me how to change the host. Is it this line?
Oct 26 2019
Oct 23 2019
This are the labels I'm trying to import:
Oct 22 2019
Hello, could we push this change forward?
Oct 17 2019
The difference is the following .... if you try to put in the wiki twice the same property:
Oct 16 2019
I suggest to replace this line:
Ok, to give back the error message to the user I propose the following change:
Alternatively, is there an option to get the id of the existing Item/Property?
Ahhhh, I got it. The problem is that a property with this label is already existing. But the error message is really not clear. I only understood it after sending the same request over the API sandbox. Is there a way to ignore this check and create the property anyway?
Oct 15 2019
Oct 2 2019
Sep 29 2019
fine for me
Sep 27 2019
this one ....
Jun 23 2019
Jun 21 2019
I have some other pull requests that I didn't do up to now because they seam not to be accepted:
- adds a property Wikidata ID so that one has a link between the new and the old entities
- some refactoring making the import faster
- a bug about the number of statements of entities
Jun 18 2019
This pull request should fix the issue:
Jun 16 2019
Jun 11 2019
I had only now time to check. Everything working, thank you!
Mar 6 2019
Feb 27 2019
No, now a new error appears:
Feb 21 2019
maybe it is related to T215870, so let's wait for this issue being resolved.
Feb 20 2019
This should answer it:
Ok, thank you. Can you please post here when this happens. Do you know how much time it will take?
Feb 19 2019
Sorry, I do not fully understand what this means. It is a problem with the dependencies that ones updated will dissapear? Or is Topic:Usk12zxjx7m3krhu not fixed yet?
PS: my error is concerning elastic search, not CirrusSearch.
Sorry, any ideas about that?
Does this error not occur to you?