Issue:Listing certain subcategories of articles

Description:	listing articles with subcategories - but how?
Extension / Version:	DPL   /   1.8
Type / Status:	Change Request   /   open

Problem

There are lots of projects with universities in my wiki-db, connected with categories like "dep03", "Wien TU", "Regensburg U" and "project-id" and containing project-descriptions. When I use "*universities" and "dep03" as page-selectors (namespace=category) I don´t get a list of universities which are only connected with department 03. Why?--Hannds 0920 15:40, 20 September 2009 (UTC)

Reply

I think there will be some logical reason for this - either a bug in DPL or a problem on your side. I recommend to reproduce your problem here in this wiki with some sample data. I am quite confident that we will find out the cause.

BTW: The "*" - operator only searches one level deep in the cat tree, "**" goes two levels deep (more is not possible atm.)

You can use pseudo-recursion to traverse deeper trees as is shown in some examples on this web site.

Gero 09:30, 21 September 2009 (UTC)

Reply

With these lines I solved my basic problem .. <noinclude><dpl></noinclude>

 category=+*universities
 category=-dep03
 category=-projects current
 ordermethod=category,sortkey
 headingmode=ordered
 include=#..some sections..

<noinclude></dpl></noinclude> .. but without being completely content. For example because there appeared out of the resulting list a new question - after about 400 lines (presenting 130 institutions) there was a break, a cut without any error message. Please, tell me how to debug effficiently dpl-errors. --Hannds 0920 22:16, 3 October 2009 (UTC)

Reply 2

DPL has a configurable safety limit for the maximum number of recors in the result set. By default this is set to 500. You can increase the limit in your LocalSettings.php after the require_once for DPL, as described in the manual, see DPL:Manual_-_Source_and_Installation and look for MaxResultCount or AllowUnlimitedResults.

However, if your result is so big, you should consider to use results scrolling. I suggest to use an approach as in DPL_Example_027. Gero 04:56, 4 October 2009 (UTC)