Issue:Minoredits=exclude broken

Description:	minoredits=exclude broken
Extension / Version:	DPL   /   1.8.1
Type / Status:	Bug   /   closed

Problem

It seems that with 1.8.1 (I suppose with 1.8.0, too) the function minoredits=exclude is broken. When I execute the following DPL statement with DPL 1.7.4 in our wiki http://www.thomas-krenn.com/de/wiki/ it works:

<DPL>
debug=3
namespace=
columns=1
ordermethod=lastedit
minoredits=exclude
order=descending
count=5
shownamespace=yes
nottitlematch=Hauptseite|Produkt-News:%
addeditdate=true
userdateformat=(d.m.Y)
format=,\n* [[%PAGE%|%TITLE%]] %DATE%,,
</DPL>

Because of debug=3 I get the following SQL statement with DPL 1.7.4:

DPL debug -- Query=
SELECT DISTINCT `page`.page_namespace as page_namespace,`page`.page_title as page_title, rev_user, rev_user_text, rev_timestamp FROM `revision` AS rev, `page` WHERE 1=1 AND `page`.page_namespace IN ('0') AND NOT (`page`.page_title LIKE 'Hauptseite' OR `page`.page_title LIKE 'Produkt-News:%') AND rev_minor_edit=0 AND `page`.page_is_redirect=0 AND `page`.page_id=rev.rev_page AND rev.rev_timestamp=( SELECT MAX(rev_aux.rev_timestamp) FROM `revision` AS rev_aux WHERE rev_aux.rev_page=rev.rev_page ) ORDER BY rev_timestamp DESC LIMIT 0, 5

With DPL 1.8.1 I get:

The DPL extension (version 1.8.1) produced a SQL statement which lead to a Database error.
The reason may be an internal error of DPL or an error which you made,
especially when using DPL options like titleregexp.
Query text is:
SELECT DISTINCT `page`.page_namespace as page_namespace,`page`.page_title as page_title,`page`.page_id as page_id, `page`.page_touched as page_touched FROM `page` WHERE 1=1 AND `page`.page_namespace IN ('0') AND NOT (`page`.page_title LIKE 'Hauptseite' OR `page`.page_title LIKE 'Produkt-News:%') AND rev_minor_edit=0 AND `page`.page_is_redirect=0 ORDER BY page_touched DESC LIMIT 0, 5

Error message is:
Unknown column 'rev_minor_edit' in 'where clause' (localhost) 

--Wfischer 09:43, 10 June 2009 (UTC)

Reply

The error is found and will be corrected in the next version. For the moment it may help if you add "addauthor=true" to your statement. Gero 12:29, 11 June 2009 (UTC)

Thank you for this information. "addauthor=true" works for me as a workaround. --Wfischer 08:16, 12 June 2009 (UTC)

With 1.8.3 it works for me. Thanks a lot! --Wfischer 07:08, 15 June 2009 (UTC)

I experienced the same problem (using DPL 1.8.9) and it is still persisting, no matter if I add "addauthor=true" or not. Is there another bug about to be fixed? --Robb 01:36, 24 October 2010 (UTC)