Topic on Extension talk:CategoryTree

Extension:LockDown can cause issues when $wgGroupPermissions['*']['read'] = false;

Moin moin.

The CategoryTree didn't find any subcategories. I hope the following image will show the problem:

While clicking "Erosion durch Wasser" (see the image) the correct pages an the subcategory appears.

Paul

On which wiki did this occur? Is it persistent (have you tried it again as it told)?

1.27.1

There are no changes when reloaded

I meant can you give a URL for debugging?

no sorry. It's under construction yet.

The CategoryTree version is

I have updated the wiki from version 1.24. Maybe there is an old stuff of the previous version?

Then please check your browser console. It can usually be accessed with the F12 key and/or Ctrl+Shift+I (if you can't find it, write me what browser you use and I try to find it out).

If it's under construction, can't you delete the whole wiki and install the most recent versions with a clean installation?

{"error":{"code":"readapidenied","info":"You need read permission to use this module","docref":"See https://fbs01/MethodenWiki/api.php for API usage"}}

The given link throws a 500 error.

Oops. Here is the cmd answer:

What's wrong?

The web error message says that you don't have read permission through the API (while you obviously have through the normal HTML interface). This can be somehow CategoryTree's code error if your wiki's private (i.e. anonymous users can't read pages). It was designed for Wikipedia, where read access is not a problem. The command line error is OK, api.php isn't designed for command line access (it wants to access $_SERVER which I think is an empty array or something like that). For development, you can set $wgShowExceptionDetails = true; in LocalSettings.php (it's not recommended for production use!), although it won't produce any error message in this case, since it's not an error in PHP level.

Ok, it is a private wiki. So it can be a code error in CategoryTree. I think i have to live with this problem.

Thanks

No, the developers should fix it. I reported here.

Maybe you're using Extension:LockDown? (would be a dupe of task T148582 in that case)

Yes :-(

The problem is the restriction with

$wgGroupPermissions['*']['read'] = false;