These two queries are using different tables (revision for the query with a user, recentchanges for the query without). So this is affected by the value of $wgNukeMaxAge and $wgRCMaxAge. Are the pages found in the first screenshot newer than $wgNukeMaxAge but older than $wgRCMaxAge? Because in that case, this would be expected behavior.

It's worth noting that there's currently no warning message for when the user provides a date range that falls outside of $wgRCMaxAge and no target (which forces use of the recentchanges table).

In T384960#10502817, @Chlod wrote:

These two queries are using different tables (revision for the query with a user, recentchanges for the query without). So this is affected by the value of $wgNukeMaxAge and $wgRCMaxAge. Are the pages found in the first screenshot newer than $wgNukeMaxAge but older than $wgRCMaxAge? Because in that case, this would be expected behavior.

It's worth noting that there's currently no warning message for when the user provides a date range that falls outside of $wgRCMaxAge and no target (which forces use of the recentchanges table).

Got it. I think I know what happened here. I increased $wgNukeMaxAge and $wgRCMaxAge in my local environment, but the recent changes table had probably already deleted the information. It would be a good idea to add a note to explain when the recent changes table is used and when the revision table is used. Otherwise, admins will be expecting different results like we did. I'm going to leave the task open for now, but will probably mark it as Invalid later on.

@Scardenasmolinar suggested adjusting the "from date" to align with the max age based on the query used for the given filter combination.

Hi @Scardenasmolinar!
As discussed below is the new design (Figma).

Summary of changes:

• No more default dates
• No more description text under the SQL pattern filter.
• New 'Date range' header with a description text: "If a username or IP address is provided, pages up to 90 days old can be retrieved. Otherwise, for performance reasons, pages up to 30 days old can be retrieved."
• For Codex: The new 'Date range' header is bolded with a description text below it. The "from" and "to" date input fields will be inside a border (with header text unbolded).

New design

Change #1118177 had a related patch set uploaded (by Kgraessle; author: Kgraessle):

[mediawiki/extensions/Nuke@master] Nuke's help text for the different MaxAge ranges is confusing

https://gerrit.wikimedia.org/r/1118177

In T384960#10521987, @OTichonova wrote:

Hi @Scardenasmolinar!
As discussed below is the new design (Figma).

Summary of changes:

• No more default dates
• No more description text under the SQL pattern filter.
• New 'Date range' header with a description text: "If a username or IP address is provided, pages up to 90 days old can be retrieved. Otherwise, for performance reasons, pages up to 30 days old can be retrieved."
• For Codex: The new 'Date range' header is bolded with a description text below it. The "from" and "to" date input fields will be inside a border (with header text unbolded).

New design

@OTichonova for the Date range description text, is this always visible or only when the nuke max age is different than the recent changes max age?

@OTichonova for the Date range description text, is this always visible or only when the nuke max age is different than the recent changes max age?

Hi @Kgraessle! It is always visible.

In T384960#10538680, @OTichonova wrote:

@OTichonova for the Date range description text, is this always visible or only when the nuke max age is different than the recent changes max age?

Hi @Kgraessle! It is always visible.

Thanks!

@OTichonova Sorry, one more question for you.

If the date ranges are the same (this can happen on some wikis) it shows like this:

Is this ok?

Hi @Kgraessle! Sorry, so in the case where it is the same we should have the text copy be:
"Due to performance reasons, pages up to $wgNukeMaxAge days old can be retrieved."

And have the longer text appear only when there is a difference between the ranges.

Change #1118177 merged by jenkins-bot:

[mediawiki/extensions/Nuke@master] Nuke's help text for the different MaxAge ranges is confusing

https://gerrit.wikimedia.org/r/1118177

Putting this back to ready per https://gerrit.wikimedia.org/r/c/mediawiki/extensions/Nuke/+/1118177 comments about adding plural message handling.

Change #1123049 had a related patch set uploaded (by Scardenasmolinar; author: Scardenasmolinar):

[mediawiki/extensions/Nuke@master] Add PLURAL to Nuke messages

https://gerrit.wikimedia.org/r/1123049

Change #1123049 merged by jenkins-bot:

[mediawiki/extensions/Nuke@master] Add PLURAL to Nuke messages

https://gerrit.wikimedia.org/r/1123049

Verified working on testwiki; leaving open until train finishes rolling out.