User Details

User Since
Dec 30 2014, 5:46 PM (316 w, 3 d)
Availability
Available
LDAP User
Unknown
MediaWiki User

Wed, Jan 20

Happened e.g. today when trying to install extension HitCounters on MediaWiki 1.35.

Mon, Jan 18

See https://cr.bitplan.com/index.php/Main_Page for the example data shown here.

@Yaron_Koren - i'll certainly try the explanation and add more examples to make my point. As far as i understand the Form definition approach the only way to handle multiple instances is currently explained in https://www.mediawiki.org/wiki/Extension:Page_Forms/Defining_forms#Multiple-instance_templates. For this to work the context of these multiple instances need to be known in advanced. So if i have pages of type:

• Open Source Project
• Git Respository
• Internal Project

...
and I'd love to use the "commit" section in all these i'd need to repeate the definition in the forms.

Could partial forms be made working by putting the definition into a standalone context - e.g. defining a form page as partial and having the form definition be picked up automatically when a fitting macro/WikiSon notation is found?

I have never tried https://www.mediawiki.org/wiki/Extension:Page_Forms/Defining_forms#Partial_forms - does this feature still work?

Before getting rid of Page Forms all together I was thinking of we could have some improvements that would lead to a "workaround" for a start.

Sun, Jan 17

Hi, @Yaron_Koren - thank you for looking into this.

Sat, Jan 16

Seppl2013 updated subscribers of T266935: Regression: Loginmanager does not make proper use of password parameter.

@Xqt - thanks for trying again. I still have some project based on pywikibot although I am trying to avoid it and use mwclient more these days due to this limited useability in intranet situations.

Tue, Jan 12

It's not clear for me how to open a "documentation" ticket from what https://www.mediawiki.org/wiki/How_to_report_a_bug has to offer. I searched for the keyword "documentation" in the page and couldn't find that keyword. What should i search for ? I never created a documentation ticket before and don't know what it looks like.

I don't know whether this a documentation problem or a bug. It's clearly an unexpected change in behavior that makes the system unusable without any warning i'd know of e.g. in a migration guide. So there are two options:

• fix the behavior
• change the documentation

IMHO it's a valid question and might be a bug if there is no proper documentation for answering the questions. I could't find the proper documentation that describe why the behavior changed and what the reason for this is.

The workaround is

# make sure we don't use "pretty urls"
\$wgUsePathInfo=false;

Dec 22 2020

Seppl2013 updated the task description for T270692: Mimetype check should be user rights dependent.

Dec 19 2020

https://github.com/WolfgangFahl/py-3rdparty-mediawiki/issues/35 will have to wait for the release on pypi see https://pypi.org/project/pywikibot/

Dec 18 2020

looks great. How do i get rid of the "family and mylang ar not set ..." messages?

Dec 14 2020

Wouldn't this be a good opportunity to generally add a link to a FAQ Wiki per error-message? I feel that following a link per error-message gives a lot more options for discussing individual situations in which an error might appear, linking to related Phabricator tasks and so on.

Dec 13 2020

It happens when I try to change the protocol for accessinga wiki. What I try is to change the apache settings:

<VirtualHost *:80>
ServerName server.domain.com
Redirect permanent / https://server.domain.com/
</VirtualHost>
<VirtualHost *:443>
....
ServerName server.domain.com
</VirtualHost>

Dec 5 2020

Seppl2013 added a comment to T260330: RFC: PHP microservice for containerized shell execution.

For the extensions https://www.mediawiki.org/wiki/Extension:Diagrams and https://www.mediawiki.org/wiki/Extension:Piwo the approach discussed here might be very useful.

Nov 21 2020

same on my main wiki - showed up after some 3 weeks of migration to 1.35 LTS - it is a showstopper! Why is this low priority if it makes the wiki completly unusable?

Nov 2 2020

Unfortunately https://www.mediawiki.org/wiki/API:Login is inconsistent. E.g. the python example uses login as an example but the text says you shouldn't use it any more but use clientLogin instead. I could not find sufficient information on the cookie issue either.

Nov 1 2020

E.g. how would a curl access with cookie work?

Opening up the wiki for public read access:

One of the issues seems to be that I don't know how to get rid of the "You need read permission to use this module." messsage on MediaWiki1.35 so that things would at least work for my public wikis.

curl -s "http://test.bitplan.com/api.php?action=query&meta=siteinfo&siprop=general|namespaces|namespacealiases|statistics&format=json" | jq .
{
"error": {
"info": "You need read permission to use this module.",
"*": "See http://test.bitplan.com/api.php for API usage. Subscribe to the mediawiki-api-announce mailing list at &lt;https://lists.wikimedia.org/mailman/listinfo/mediawiki-api-announce&gt; for notice of API deprecations and breaking changes."
}
}

Oct 31 2020

If you try to debug the situation and click on "site" in the loginmanager a sequence of API call is initiated ... that makes it even harder to find out what is going on ...

If checking the version is the issue please user the information from the family file (and trust it) instead of trying to find out via Mediawiki API doing an http request before being logged in ...

There is a

WARNING: API error readapidenied: You need read permission to use this module.

warning with no details on what the API called is. When debugging it reveals that a meta=siteinfo is tried and if that fails a login is performed. This doesn't make any sense if a proper user/password combination is given. Why try to use the API - how can this be switched off because of course you can't use the API if you are not logged in ...

What is the proper procedure to tell pywikibot the password for login via API ? I am using

python
# needs patch as outlined in https://phabricator.wikimedia.org/T248471
lm.login()

and i get a WARNING:

WARNING: Could not check user '...' exists on wiki:lang

With pywikibot 5.0.0 i have to start all over again ... sigh ..

Oct 1 2020

The same secondary message might appear in other contexts. In my case it is:

Sep 30 2020

I can't see where the problem is.

I tried debugging the line 595492 mentioned in the error message. See my stackoverflow answer to How to get few lines from a .gz compressed file without uncompressing

Sep 29 2020

For me it's a showstopper. I'd love to work on https://github.com/somnathrakshit/geograpy3/issues/15 and currently I have the following options to run the SPARQL query for it

Sep 28 2020

I retried the download which took another 16h but the problem persists

Sep 25 2020

tried

git pull
mvn package

today and problem persists

Still the message could be improved into "File missing or config error" and having a pointer to the FAQ and may be such a checking code or extension.

Sep 6 2020

Seppl2013 added a comment to T262114: Need Math extension for Mediawiki 1.33.4.

The issue here is the undecipherable error message. Since the invalid status of this task is only based on the version MW 1.33.4 that i was trying things out on is EOL. It's not clear whether the error message has been improved so that "normal" people would understand what the real problem is in more recent versions of MW. I tried out different git states yesterday and always go the same error message so that i assume there is a "real" issue behind this task. It's just that the rules within MediaWiki foundation are such that the followup will not happen immediately for this task as it's reported based on a MW 1.33.4 experience. So i think it's good to have this task for reference so that other users that might run into a similar situation can reference it. Even the hint for the workaround https://www.mediawiki.org/wiki/Extension:SimpleMathJax - was a bit hidden in the documentation.

Sep 5 2020

Seppl2013 closed T262114: Need Math extension for Mediawiki 1.33.4 as Resolved.
Seppl2013 added a comment to T262114: Need Math extension for Mediawiki 1.33.4.

According to https://www.mediawiki.org/wiki/Manual:Math the work-around is to install https://www.mediawiki.org/wiki/Extension:SimpleMathJax which i did successfully.

Seppl2013 added a comment to T262114: Need Math extension for Mediawiki 1.33.4.

I am not asking for a solution but a work-around. And it would be good if such situations could be avoided in the future by proper impact analysis which extensions break on API changes and not doing API changes with too much impact.

Seppl2013 updated the task description for T262114: Need Math extension for Mediawiki 1.33.4.
Seppl2013 updated the task description for T262114: Need Math extension for Mediawiki 1.33.4.

Aug 3 2020

Bawolff asked on project support desk:
How would mediawiki distinguish between the config being wrong and the file just happening to be missing?

Seppl2013 added a comment to T224854: maintenance/cleanupUsersWithNoId.php doesn't do anything.

work around:

delete from logging where log_user_text="";

Aug 2 2020

Maybe this could be a step in the update.php file to check that there is a reasonable file configuration if lots of files are pointed to in the SQL file but do not properly resolve ..

Is this a request to edit https://www.mediawiki.org/wiki/Manual:Errors_and_symptoms#Image_Thumbnails_not_working_and/or_appearing ? - yes thats's part of the issue and I added a section.

The issue is in the confusing message "File missing" - it's not true that the file is missing. The configuration is wrong and the pointer to the directory of files is not configured correctly. For a single such message it would not be a problem but if in "browse files" every single image shows the same misleading message "File missing" than that is an issue which should be fixed to allow administrators to get informed about the problem by their users much more quickly and more detailed than is the case right now.

Jul 28 2020

Seppl2013 added a comment to T224854: maintenance/cleanupUsersWithNoId.php doesn't do anything.
select count(*) from logging where log_user_text="";
+----------+
| count(*) |
+----------+
|      879 |
+----------+
1 row in set (0.001 sec)
Seppl2013 added a comment to T224854: maintenance/cleanupUsersWithNoId.php doesn't do anything.

same here ...

 select * from actor where actor_name='';
+----------+------------+------------+
| actor_id | actor_user | actor_name |
+----------+------------+------------+
|     3164 |       NULL |            |
+----------+------------+------------+
1 row in set (0.000 sec)

Jul 7 2020

Please reopen this issue - marking it invalid since it's not reproducible in the Wikimedia Universe is not helpful for those having the problem in their own environment .

Jul 6 2020

You trial was obviously on Windows and not Ubuntu 18.04 LTS

Jul 5 2020

It was a bit frustrating.

Jul 4 2020

Seems to happen again e.g. pip3 install --no-cache-dir -I pywikibot==3.0.20200508

Jun 5 2020

Seppl2013 added a comment to T254003: How to use pywikibot to get data from SMW ask API?.
from pywikibot.data.api import Request
Seppl2013 added a comment to T254003: How to use pywikibot to get data from SMW ask API?.

The https://pypi.org/project/py-3rdparty-mediawiki/ SMW support now works quite nicely to handle the SMW API. This task can IMHO be closed.

May 29 2020

Seppl2013 added a comment to T254003: How to use pywikibot to get data from SMW ask API?.

@Xqt - thanks for looking into this. I am currently adding this to https://github.com/WolfgangFahl/py-3rdparty-mediawiki/issues/1 with https://github.com/WolfgangFahl/py-3rdparty-mediawiki/blob/master/wikibot/smw.py where I am happily using a standard Request for the time being to simplify things. It seems that APIGenerator adds caching handling and some legacy stuff as well as continuation - for the time being i'd focus more on the core functionality of unpacking the printrequest structures delivered and being able to use cut&paste for ask queries. The implementation will be mostly along the lines of https://github.com/BITPlan/com.bitplan.simplegraph/blob/master/simplegraph-smw/src/main/java/com/bitplan/simplegraph/smw/SmwSystem.java where this was already succesfully implemented in Java.

Seppl2013 updated the task description for T254003: How to use pywikibot to get data from SMW ask API?.

May 22 2020

Seppl2013 added a comment to T253378: pywikibot transitive dependency on crypto.

Looks like this is a general pip problem with transitive dependencies. The pycrypto library is also explcitly mentioned in the requirements.txt file for py-3rdparty-mediawiki. I'll try to release that library on pypi to see if that fixes the issue.

I have tried today with pywikibot>=3.0.20200508 and on my local machine the tests run. I am having some trouble in the travis environment of a project I am using things now - I'll create a separate issue for that.

Apr 1 2020

Could you please put a release on test.pypi.org so that I can install the master with pip ... or simply create a release candidate on normal pypi.org and put the link here.

Mar 31 2020

Thx for the offer. I am fine as long as i have a workaround ... no need to hurry then.

Again i had to do a patch to make sure the password is not forgot with two lines:

Mar 30 2020

Sigh - this is like a catch 22 see how https://phabricator.wikimedia.org/T248673 got closed while i am stuck with MW 1.27.3. So neither my old wiki nor my new wiki is useable in the process of semi-automatic migration ... and in the meantime my "new wiki" which i have been trying to migrate to for a year now is not new any more ...

I suspect:

Thx. There is a followup problem. When trying to login to a Mediawiki 1.33.2 system I get:

WARNING: API error readapidenied: You need read permission to use this module.
WARNING: API error readapidenied: You need read permission to use this module.
[help: See http://.....bitplan.com/api.php for API usage. Subscribe to the mediawiki-api-announce mailing list at &lt;https://lists.wikimedia.org/mailman/listinfo/mediawiki-api-announce&gt; for notice of API deprecations and breaking changes.]
WARNING: API error readapidenied: You need read permission to use this module.
WARNING: API error readapidenied: You need read permission to use this module.
WARNING: Could not check user ... exists on ...:en
Password for user ... on ...:en (no characters will be shown): Warning: Password input may be echoed.

Mar 28 2020

Very good. I think this task can be closed now.

Mar 27 2020

Thx the data.api LoginManager works. How do i get rid of the warning:

https://test.pypi.org/project/py-3rdparty-mediawiki/0.0.2rc0/ has the latest code that works with the patch. https://github.com/WolfgangFahl/py-3rdparty-mediawiki/blob/master/wikibot/wikibot.py#L135 has your proposal but commented it since it breaks the tests. You'll need to prepare at least one ini file with your credentials if you want to test your self so you might be the first to create the issue mentioned in http://mediawiki-japi.bitplan.com/index.php/Py-3rdparty-mediawiki#Features

I am trying to figure out how to create a patch file with https://cocoon.apache.org/2.0/howto/howto-patch.html - the unified diff there looks different than the rcsdiff patch above. What is needed for a proper patch file?

The new patch seems to be:

https://pypi.org/project/pywikibot/ shows a build error ...

When i debug the code i end up in:

It looks like site.py is gone now and code moved to site/__init__.py ... what is the motivation for this inorthodox coding style?

now my software is broken again and I need to repatch manually since pip uninstall removed the RCS directory ...

Tried it and it does not work as advertised. pywikbot.api does not seem to exist and for:

Seppl2013 added a comment to T248673: Nuke does not work or is documented poorly.

Indeed on 1.33.2 things seem to work as advertised.

Seppl2013 added a comment to T248673: Nuke does not work or is documented poorly.

1.27 is the only version we can currently use. That is unsupported is very unfortunated but we can't migrate although we are trying hard. Too many breaking changes have been introduced in the last few months and we don not have the capacity to keep up with all these incompatible changes. Not being able to use the nuke extension does not help for the migration since we still have a lot of tests to do in which we generate pages and need to quickly remove them again.

How? I didn't see an example and proper doc for it and couldn't find a way to decipher the source code. Passing the password as the constructor suggests seems to be natural to me.

From my point the proposed change is not a workaround. It's fine. The encryption in this case was motivated to be MediaWiki-Japi compatible which uses https://github.com/WolfgangFahl/py-3rdparty-mediawiki/blob/master/wikibot/crypt.py inspired by https://stackoverflow.com/questions/24168246/replicate-javas-pbewithmd5anddes-in-python-2-7 that's why it's important to be able to set the password via API and not from a configuration file. In fact https://test.pypi.org/project/py-3rdparty-mediawiki/0.0.2b0/ only uses