SimpleTasks with DPL on same page not working

When using the DynamicPageList (DPL) extension together with SimpleTasks on the same BlueSpice wiki page, SimpleTasks stops working correctly.

Even a minimal DPL query that only retrieves pages from a single category is enough to trigger the issue.

Instead of rendering the SimpleTasks entries as an interactive task list with checkboxes, all tasks are displayed as plain text, with the entries running together in a single paragraph.

Removing the DPL query immediately restores the expected SimpleTasks functionality.

Important: If the DPL query returns no results, SimpleTasks continues to work correctly. The issue only occurs when DPL actually returns matching pages.

Steps to Reproduce

  1. Create a new wiki page.

  2. Add the following minimal wikitext:

== DynamicPageList ==

{{#dpl:
 |category=Test
}}

== SimpleTasks ==

[x] Completed task 1
[] Open task 2
[] Open task 3

<!--LIST_END-->
  1. Save the page.

  2. Observe how the SimpleTasks entries are rendered.

  3. Remove the DPL query and save the page again.

Expected behavior:
Both extensions should work independently on the same page.

  • DPL should display matching pages from the specified category.

  • SimpleTasks should render an interactive task list with properly formatted entries and checkboxes, regardless of whether DPL returns results.

Hi Basti 2228,

I copied your example to our test system and it did not produce any error. All SimpleTask entries were rendered and behaved correctly (and DPL returned some results).

I tested in our current version:

Product Version
MediaWiki 1.43.11 (edd0cff)
PHP 8.4.23 (fpm-fcgi)
ICU 78.1
MariaDB 10.5.29-MariaDB-ubu2004
BlueSpice pro (Credits) 5.2.7

which has bundled:

  • DynamicPageList3 3.6.4 (db57791)
  • SimpleTasks2.1.7 (93523da)

Greetings,

Margit

Hi Margit,
Thanks for your reply.
I tested it in your demo wiki with this source-code:

== DynamicPageList ==

{{#dpl:
|category=Anleitung
}}

== SimpleTasks ==

[x] Completed task 1
[] Open task 2
[] Open task 3

It did not work

That’s true. Our test system is next patch version 5.2.7.

The currently published version is 5.2.6. It indeed has the problem you are encountering (thanks for testing on our current demo version).

The outstanding commit should be part of our next patch release which is planned within the next 14 days. The problem was fixed with: