Consumer Rights Wiki talk:Bugs

Welcome — Issues of Interest to Developers

When reporting a bug, please include as much detail as possible to help developers reproduce and fix the issue. Please do not report security issues here. Email them to [email protected] instead.

• Check for duplicates: look through existing reports before posting to avoid repeats.
• System details: include your operating system, browser, and platform (e.g. Windows, macOS, Linux, x86, ARM, Chrome, Edge, Safari, Firefox).
• Inputs and outputs: describe what you did, what you expected to happen, and what actually happened.
• Reproduction steps: provide clear, step-by-step instructions so developers can replicate the bug.
• For general discussions or suggestions not related to bugs, please use the Moderators' noticeboard instead.

Report a new bug

• You will receive a response from User:JakeL, who is contracted to provide professional support for this wiki in a production environment.

Previous discussions
1 2

Wiki search engine indexing

There are a couple of posts asking about search engine indexing of this wiki: Consumer Rights Wiki talk:Moderators' noticeboard#Should CRW be indexed by search engines? and Talk:Main Page#Suggestion: Implementing a /robots.txt page. 📎 JackFromWisconsin (talk | contribs) 02:20, 24 August 2025 (UTC)

We are currently looking into this and I will update the thread as and when we have a solution or any further news. JakeL (talk) 00:38, 8 September 2025 (UTC)

How do you edit beginning of an article with StubNotice?

I was trying to edit the beginning of the article on Medical ventilator (to add a see also link to the medical equipment article).

The article has a StubNotice template at the beginning (on the same line as the beginning of the first paragraph).

When I try to save changes after making ANY change to the text on the same line as the stub notice template, it will not save (it gives me a message telling me about the procedure for requesting stubnotice removal). I am not trying to move or remove the stub notice, I didn't touch that. Even if all I try to do is put a newline or space after the template, or change words on the first line, it won't let me. This happens whether I use the visual editor or the source editor. I am using firefox running on linux.

I can save changes later on in that article, and I have edited other articles marked as stubs without issue.

The stubnotice documentation and talk page do not seem to document this behaviour, or tell me what to do. If this is desired behaviour, then the template should explain how to handle it.

Thank you. Drakeula (talk) 21:31, 24 September 2025 (UTC)

Not a mod, but I think I can respond to this. You can’t and this is pretty much desired behaviour. The Abuse filter is the reason for it. It does attack more than just that area too as it thinks you’re changing the notice. AnotherConsumerRightsPerson (talk) 07:40, 28 September 2025 (UTC)

I don't understand why this behavior would be desired. To me it seems like a bug, where the abuse filter is protecting more than it should.

Regardless, how can we improve the lead paragraph when we can not change it?

• Are we supposed to duplicate the immutable first paragraph, putting any revisions/improvements in a secondary copy of the first paragraph? Is there a standard template or way to document what is going on so it doesn't confuse readers when they see two first paragraphs?
• Do we need to propose edits to the first paragraph in some form on the talk page, then request an administrator to come and actually make the change? (If so, how/where do we make the request?)
• Are we expected to just ignore problems in the first paragraph, and revise the rest of it until the stub can be removed?

Thanks. Drakeula (talk) 01:37, 1 October 2025 (UTC)

I wonder if this edit, where an administrator used the visual editor to delete a deletion tag after the stubnotice might be part of the problem. Prior to that edit, the stubnotice was on its own line. After that edit, the stubnotice is on the same line as the first paragraph.

https://consumerrights.wiki/index.php?title=Shortage_of_medical_ventilators_during_the_COVID_pandemic&diff=prev&oldid=25186

If the abuse filter intentionally protects everything on the stubnotice line, then the problem may be in the visual editor, which should ensure that it preserves the newline at the end of a protected line. (At the very least, it should warn an administrator when they are suddenly protecting a bunch of text that wasn't protected before.) Drakeula (talk) 02:06, 1 October 2025 (UTC)

I personally don’t like the current ‘stub notice can only be removed by mods’ anyway, and there are loads of article maintenance templates which don’t have this for some reason. Proposing edits in talk page is actually done on Wikipedia in the form of edit requests, where a mod will look at it there, but the thing is it won’t alert mods here to the request by just posting about it. The point about it protects the entire line seems valid to me and makes complete sense from my own experience, so I do think that is the most likely scenario. AnotherConsumerRightsPerson (talk) 15:22, 1 October 2025 (UTC)

This is by design so that editors do not remove the notice until its been removed by staff for completeness. Once work on an article is completed you can post an appeal in the noticeboard or discord #appeals staff do actively check these so that peer edits can be approved and notices removed. This is both by policy and system design; it is not a bug. If you have thoughts on how we can improve this process feel free to bring it up in the dashboard - Atsumari (talk) 15:46, 12 October 2025 (UTC)

If this is desired behavior -- why? What purpose does it serve making it so the entire first paragraph of an article is immutable?

Note that the issue is the protection of the rest of the line, not the protection of the notice itself.

@Atsumari Sorry, I don't know where/what the dashboard is, please give me a link. In the meantime, I will post suggestions for improvement here. Thank you.

How to improve it:

• Fix the code, so that only the stubnotice template is protected, not the rest of the line.
• Fix the code when submitting a change so that it always adds a newline immediately after a stubnotice (or other protected template) if there isn't one there.
• When a moderator submits a change with anything on the same line as a protected template, (either by adding to it, or by deleting the newline at the end of the line) the software should issue a warning, telling them what this will do to everybody else and asking them to confirm that they really want to do that. (Make the warning simple, clear, blatant, something you have to type a response to so people will read it and not autoclick.)

Temporary workarounds:

Add cautionary notices to the stubnotice template and its documentation.

• The documentation should explain this behavior, tell moderators what the intended use of protecting the rest of the line is, and warn moderators about the problems it can cause.
• If the visual editor is part of the problem (as I suspect it may be, given the edit which caused the problem in this article), then the documentation should warn moderators to be especially careful when using it around stubnotices.
• The template text should explain what is going on, so an editor encountering the problem for the first time knows what is happening, and what to do about it. (How to get help to fix this case.) Drakeula (talk) 19:46, 18 October 2025 (UTC)

Just found that the template:incomplete has same problem. Drakeula (talk) 05:17, 19 October 2025 (UTC)

That part about the first paragraph being un-editable is not intended but the fact that users cannot edit the stub notice (or other notices) is created so someone cant just arbitrariliy edit their post removing the notices without staff review and formal appeal of the action by the user. As for where the dashboard is Consumer Rights Wiki talk:Moderators' noticeboard here is a link to it. As for the rest of your concerns I will flag down one of the tech folks or Keith for you to provide a more detailed explaination or look into exactly why everything in a first paragraph is being locked down as if someone adds a stub notices it should be at the top and above all text so there should be a seperation between the article text and the stub notice. This might also just be a policy thing we need to discuss as the stub notice is working as intended but the text after it being locked is not. - Atsumari (talk) 08:24, 1 November 2025 (UTC)

CAPTCHA appears only after pressing Add topic or any other similar main activity button clicked

More of a suggestion, but it would be much better if CAPTCHA appeared if user made changes in all required fields/field. Less clicks to action - better UI, more engaged regular users. Banana (talk) 01:35, 8 November 2025 (UTC)

What do you mean could you provide a more detailed explanation? That way the development team can actually look at this and see what’s possible. - Atsumari (talk) 07:13, 9 November 2025 (UTC)

Numeric usernames in cites produce warnings

Usernames allow a wide range of characters. When |author= is used, the warning should not exist. The numberic warning should still exist on |last= and |first=. Many pages in Category:CS1 maint: numeric names: authors list are false positives. 2A00:23C8:2384:101:B34:3E7B:6AF4:18CF 16:56, 9 November 2025 (UTC)

Broken pages

Hello, there are some pages that were created by the maintenance script that are all a subpage of Broken. You can find them by going down here. AnotherConsumerRightsPerson (talk) 07:43, 2 January 2026 (UTC)

These pages don't even seem to be deletable. AnotherConsumerRightsPerson (talk) 06:18, 15 January 2026 (UTC)

Error when using " Random page " button

I was just poking around at the website, until I've noticed a random page button, hit it once, worked fine, tried it another time and got this error : MediaWiki internal error.

Original exception: [b1219b51071b190a6bd156cf] 2026-01-22 08:02:21: Fatal exception of type "MediaWiki\Exception\MWUnknownContentModelException"

Exception caught inside exception handler.

Set $wgShowExceptionDetails = true; at the bottom of LocalSettings.php to show detailed debugging information. , this is the url: Broken/NS112:Profile:Facetedsearch default profile

86.120.52.41 08:04, 22 January 2026 (UTC)

Thanks for pointing this out! I'll pass it on to the technical guys. weird that it only failed the second time... Keith (talk) 09:02, 22 January 2026 (UTC)

T think the weird thing is you being sent to that page in the first place, rather than the fact that an error appeared when you were. i mashed ramdom page a few times and had no problem so i assume it's an issue with the list of pages it's choosing from. Keith (talk) 09:04, 22 January 2026 (UTC)

Ok, this is the same issue as 'Broken pages' above, and is being worked on. Keith (talk) 12:50, 3 February 2026 (UTC)

Consumerrights wiki not translatable via translate.google.com

I wanted to share a page of this wiki with a Dutch-speal-king friend & Google Translate has this handy feature where you can drop a link, and it will generate a link with the webpage translated to your language of choice. Unfortunately, this feature doesn't seem to work for consumerrightswiki (returning a 403 Forbidden), limiting its reach to EN-only speakers. Is there any chance translate.google.com can be whitelisted?

This link is an example of translating the Microsoft_Windows page to Dutch: https://consumerrights-wiki.translate.goog/w/Microsoft_Windows?_x_tr_sl=en&_x_tr_tl=nl&_x_tr_hl=en&_x_tr_pto=wapp&_x_tr_hist=true

In DevTools:

Google Translate consumerrights.wiki failure

Webketje (talk) 09:35, 23 January 2026 (UTC)

I tested it and am getting the same problem. SinexTitan (talk) 10:30, 23 January 2026 (UTC)

this website isnt indexed by search engines, thats probably why this happens AnotherConsumerRightsPerson (talk) 17:58, 23 January 2026 (UTC)

@AnotherConsumerRightsPerson That is not the issue; it is indexed by search engines (at least the main page). This is a server configuration issue, perhaps to do with X-Frame-Options or other headers Webketje (talk) 11:16, 29 January 2026 (UTC)

Main Page error (Different)

After answering the survey on CryptPad, you get prompted to visit the Main Page. The link however, leads to https://consumerrights.wiki/Main_page, whereas the actual Main Page is https://consumerrights.wiki/Main_Page with a capital P. Should be as simple as adding a redirect for all capitalisation variants of "Main Page", to avoid this issue ever again, since no article will (or should) ever use the name Main Page, anyway. Sebandar (talk) 19:49, 23 January 2026 (UTC)

Created the redirect - thank you for bringing it up! (and sorry for the delayed response) Keith (talk) 09:44, 3 February 2026 (UTC)

Page tabs hidden

Whatever the changes were has caused the first two tabs (article/project & talk) to now appear behind the site logo for CRW. — Sojourna (talk) 00:11, 28 January 2026 (UTC)

Please force clear your browser cache. JakeL (talk) 00:30, 28 January 2026 (UTC)

I have force cleared the browser cache for Firefox v147.0.2. I used the "purge cache" under the "More" tab, and force-refreshed the page - didn't work. I had to change the appearance setting from "Vector legacy (2010)" to a something else for the affected tabs to appear. — Sojourna (talk) 00:49, 28 January 2026 (UTC)

Thanks for letting me know. Could you please use our default skin (Vector 2022) for now until I get around to this? I haven’t done any work to optimise the legacy theme yet, as most people are using the default theme, thanks again for bringing this to my attention! JakeL (talk) 01:00, 28 January 2026 (UTC)

Now fixed! JakeL (talk) 21:16, 1 February 2026 (UTC)

Main page header blues are low contrans, and don't meet WCAG AAA standards.

#7FB6FF for links and #004080 for background are too close to each other. It is improvement over prevous conmination, but still not super accessible for color blind people. Blue and black themes are quite hard to make because both are dark colors. You can ping me here or in Discord if you want to discuss accessibility. Banana (talk) 22:40, 4 February 2026 (UTC)