You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
List of steps to reproduce (step by step, including full links if applicable):
On an "Apple" page, make a Notes section with content, followed by a category for the page in either noinclude or includeonly tags.
Put on another page:
{{#dpl:
|title=Apple
|include=#Notes
}}
What happens?:
The page with the dpl statement will be erroneously categorized because it ignores the noinclude/includeonly tags, as can be observed here.
What should have happened instead?:
DPL3 should be able to correctly noinclude/includeonly, and not cause unintended categorization.
Browser information, screenshots and other applicable information:
Not related.
The text was updated successfully, but these errors were encountered:
An update , I now see |eliminate = categories can be used to filter off categories, though I still suspect it is unintentional/undesired for DPL3 to ignore noinclude/onlyinclude tags. Though perhaps there's some reason for this behavior that I'm just not understanding (likely)?
I have the same issue. I need to exclude footnote tags from the section transclusion and put them in noinclude tags. But the noinclude tags have no effect.
DPL3 version: 3.5.1
DynamicPageList3 version: 3.4.5
MediaWiki version: 1.37.2 (Miraheze)
PHP version: 7.4.28
TLDR: Problem observed here:
https://dpl3.miraheze.org/wiki/Criteria_for_page_selection/Parameter:_title_(example_1)
List of steps to reproduce (step by step, including full links if applicable):
What happens?:
The page with the dpl statement will be erroneously categorized because it ignores the noinclude/includeonly tags, as can be observed here.
What should have happened instead?:
DPL3 should be able to correctly noinclude/includeonly, and not cause unintended categorization.
Browser information, screenshots and other applicable information:
Not related.
The text was updated successfully, but these errors were encountered: