Jump to content

Tech

Add topic
From Meta, a Wikimedia project coordination wiki

English is the only option when the public looks at my page !

[edit]

I am guiding French speaking visitors of my community to my supposedly bilingual global meta-wiki user page, but there is no language choice for a French speaking visitor. I use Desktop French Linux Mint, French Firefox, but all I get is : Login to change the language This is missing something, like logic. Please help. Ineuw (talk) 00:25, 27 September 2026 (UTC) P.S: Deleted all cookies, before testing this. Ineuw (talk) 00:37, 27 September 2026 (UTC)Reply

Hi, as you wrote "Log in to select a different language for menus", is something unclear with that message? Is this a feature request? Also note that going to https://meta.wikimedia.org/wiki/User:Ineuw?uselang=fr is a potential workaround. AKlapper (WMF) (talk) 19:17, 27 September 2026 (UTC)Reply
I may be missing with something you are trying to archive, but you can add {{languages}} for pages with multiple-lingual subpages when the page is not being managed by the translate extension. P858snake (talk) 19:38, 27 September 2026 (UTC)Reply
The visitor has no Wikipedia account. How can they change the language of their choice???
and where can I upload a screenshot ? Ineuw (talk) 21:26, 27 September 2026 (UTC)Reply
  • As AKlapper wrote, you can add a link with the uselang parameter on the top of the page. This works regardless of whether the user is logged in or not. (Maybe you could create a feature request to include an equivalent of this in the language selector. uselang makes displaying a page for logged-out readers far less efficient than without uselang, so site operators may not like the idea, but maybe they’re fine with it as long as the setting for logged-out readers is only for a single page view.)
  • On French-language wikis (where you don’t have a local user page) like French Wiktionary, the page should display in French by default. (I don’t see any language-dependent content on the latest version of the page, so I couldn’t test it though.)
Tacsipacsi (talk) 08:53, 28 September 2026 (UTC)Reply
Thanks for all the help from everyone. The French Wiktionary never had a home page. When created, it dawned on me and began the changes throughout. As for the language indicator, I emailed the English link beforehand to members of my French community, and then I noticed the issue. The current option is aimed at registered users, and this must be a design oversight. This doesn't serve anyone, and certainly not visitors, even with an account. Ineuw (talk) 20:45, 5 October 2026 (UTC)Reply

Wikidata changes

[edit]

Hi. Why wikidata changes are now not represented in my watchlist? I tried to play with preferences, checked out they are not hidden, but still doesn't work. Hugo.arg (talk) 18:00, 16 October 2026 (UTC)Reply

Hi @Hugo.arg, there was a change where language link changes were removed from Recent Changes and Watchlists (please see Proposal: Language link changes and Remove language link changes for full information. Please write to us at the dedicated Project Talk page and we can help you further.
Our change should only affect instances of (Language link added, removed or changed:) to your watchlisted items. Other types of Wikidata edit should be unaffected, but if you believe this isn't so, we would like to hear from you and help you. Best, -- Danny Benjafield (WMDE) (talk) 11:35, 19 October 2026 (UTC)Reply

Ayuda con Wikimuseum (es ver.)

[edit]

Hola, soy proponente de Wikimuseum y busco a una persona especialista en MediaWiki que me ayude a gestionar extensiones, funcionalidades y espacios de nombres de la plataforma para, posteriormente, poder hacer una solicitud clara en Phabricator.

Muchas gracias.

Atte: Jackie SMG (talk) 16:42, 18 October 2026 (UTC)Reply

Ayuda con Wikimuseum (en ver.)

[edit]

Hello, I am the proposer of Wikimuseum, and I am looking for a MediaWiki specialist to help me manage the platform's extensions, features, and namespaces, so that I can subsequently submit a clear request on Phabricator.

Thanks

Regards, Jackie SMG (talk) 21:27, 19 October 2026 (UTC)Reply

Adding the editpage grant to an existing OAuth consumer

[edit]

Hello,

I'm developing Tourism Mapper, a Wikimedia Toolforge application that helps contributors document Nigerian tourist sites by uploading photographs to Wikimedia Commons and creating or updating Wikidata items.

OAuth authentication and Commons uploads are working. However, when the application attempts to set labels and descriptions on Wikidata items using wbeditentity, the API returns permissiondenied.

My existing approved OAuth 1.0a consumer has these grants:

  • Create, edit, and move pages
  • Upload new files

It appears to be missing the Edit existing pages (editpage) grant. I checked the consumer's update form, but I couldn't find an option to modify the applicable grants.

Could someone advise whether this grant can be added to an existing approved consumer, or whether I need to register a new consumer with the required grants?

I would prefer to retain the existing consumer because its credentials are already configured in the deployed Toolforge application.

Consumer registration: https://meta.wikimedia.org/wiki/Special:OAuthConsumerRegistration/update/64ea9b0279c531c511aa2ea26b66a2b4

Thank you for your help. JosefAnthony (talk) 07:21, 24 October 2026 (UTC)Reply

Hi @JosefAnthony, it's not possible to modify consumer grants now. You have to register a new consumer. – Ammarpad (talk) 08:32, 24 October 2026 (UTC)Reply
Noted with Thanks @Ammarpad JosefAnthony (talk) 10:51, 24 October 2026 (UTC)Reply
Hi @Ammarpad, I registered a new OAuth consumer, Tourism Mapper [1.2], as advised, but its status is still Proposed. Is there anything else I need to do, or should I simply wait for it to be approved? Thank you. JosefAnthony (talk) 08:51, 27 October 2026 (UTC)Reply
Yes, it requires approval. You can post an additional manual request at Steward requests/Miscellaneous#OAuth permissions. You will likely get a faster response there. – Ammarpad (talk) 22:09, 28 October 2026 (UTC)Reply