Edge Rewrite
// HTMLRewriter · presentation

This page was redesigned at the edge.

Cloudflare fetched the original article and streamed it through HTMLRewriter to apply an entirely new visual system without rebuilding the source page.

// request.cf · coarse context

A page that knows where it met you.

Only coarse request metadata is shown. This demo does not display or persist visitor IP addresses.

Country
US
Cloudflare location
CMH
Connection
HTTP/2
Language
Not provided

Ray ID: a22228dd5c1eb965

Jump to content

Module talk:Database reports/Hot articles

Page contents not supported in other languages.
Add topic
From Wikipedia, the free encyclopedia
(Redirected from Module talk:Database reports/Hot articles/doc)
Latest comment: 6 months ago by StefenTower in topic border-collapse: separate;

Article and days limits

[edit]

Hi, out of curiosity, is there a technical reason behind the parameter limits, specifically the 5-10 article limit and 1-7 days limit? Or are these completely arbitrary limits that could be increased? Thank you! Ganmatthew (talkcontribs) 09:11, 24 September 2025 (UTC)Reply

They are same as the limits imposed in HotArticleBot. They can be increased. The only hard restriction is that the db query should take less than 10 minutes. – SD0001 (talk) 10:54, 24 September 2025 (UTC)Reply
Ah I see. For the article limit, does setting it to 15 or 20 come close or exceed 10 minutes when used on the big WikiProjects? Maybe increased limits could be allowed based on the article count of the WikiProject or category? Ganmatthew (talkcontribs) 14:17, 25 September 2025 (UTC)Reply
I don't think it would, but I haven't checked. The bot anyway applies the 10-minute timeout so I think there's not much point to having the limits on articles and days, except a nicer error message than the one for query timeout. I have just relaxed the days limit to 30 and removed it entirely for articles. – SD0001 (talk) 14:53, 25 September 2025 (UTC)Reply
Alright nice. Thanks! Ganmatthew (talkcontribs) 15:12, 25 September 2025 (UTC)Reply

Table row numbers

[edit]

Hi, I realized having row numbers would be beneficial for the table reports and I noticed that the SQL query used by the module already has a Row parameter that returns the row/index number, so I went ahead and added commented-out changes to both the header and row template to make them visible in the tables.

But when it came to this module and the Database report template, I couldn't figure out a straightforward way to pass an optional parameter from the report template to both the header and row templates to determine whether to show row numbers, or maybe I'm just not familiar with how it could be done.

Is there a way to have some kind of parameter like `rownumber = yes` that could be read by the header and row templates? Thanks! Ganmatthew (talkcontribs) 09:58, 7 October 2025 (UTC)Reply

There's currently no straightforward way to do that (one of the reasons I had to make Module:Database reports/Hot articles by category altogether separate).
Instead of using Row parameter, you could use {{static row numbers}}, so that header and row templates don't need to be modified. See bullet 3 of Template:Database report#SQL formatting tips – it suggests making it a header template, but as another header template is already used here, you can put it in report:setHeadContent() instead. – SD0001 (talk) 18:26, 7 October 2025 (UTC)Reply
That helps. I'll also go and revert the changes to the header and row templates. Thanks! Ganmatthew (talkcontribs) 09:12, 8 October 2025 (UTC)Reply

Article limit surpassed

[edit]

Hi, would you know why |lua_arg_articles=10 was not heeded in ? It shows 16 rows instead of 10. Thanks, czar 16:27, 1 January 2026 (UTC)Reply

I assume it might be because the last seven entries all have the same amount of edits. Ideally it would cut off at 10 entries regardless of how many are "tied" for that tenth row. czar 16:32, 1 January 2026 (UTC)Reply
I think it makes sense to show the ties at the end as otherwise you're leaving out valid results, giving short shrift to them just because of lexical order. That said, I wouldn't be against having a setting that forces a cut-off for anyone who needs that "clean 10" for spatial or other purposes. Stefen 𝕋ower HuddleHandiwerk 02:46, 2 January 2026 (UTC)Reply
In WikiProjects where there will often be ties for low-edit articles, it will mean the list will always be longer than 10, so that option of forcing a cutoff would be appreciated. czar 02:57, 2 January 2026 (UTC)Reply

border-collapse: separate;

[edit]

Why is this style parameter needed? I'd suggest removing it so the table dividers are no longer twice as thick but wanted to check first. czar 16:46, 1 January 2026 (UTC)Reply

I copied it from @StefenTower's templates. I presume it's to give a more aesthetic look. – SD0001 (talk) 17:01, 1 January 2026 (UTC)Reply
Most tables don't use that aesthetic so I'd recommend removing it here czar 02:58, 2 January 2026 (UTC)Reply
This isn't an article table so there's no requirement to follow a specific style. That said, like the other thing, this can be a setting. I personally like this presentation but if it's not the default, that would be fine. Stefen 𝕋ower HuddleHandiwerk 03:05, 2 January 2026 (UTC)Reply