User talk:Want
Add topicWelcome to Meta!
[edit]Hello, Want. Welcome to the Wikimedia Meta-Wiki! This website is for coordinating and discussing all Wikimedia projects. You may find it useful to read our policy page. If you are interested in doing translations, visit Meta:Babylon. You can also leave a note on Meta:Babel or Wikimedia Forum if you need help with something (please read the instructions at the top of the page before posting there). Happy editing!
—MarcoAurelio (talk) 16:12, 23 June 2019 (UTC)
Untitled
[edit]Hello,
I've got a problem with the search - function on my mediawiki. Since I have installed the extension "AccessControl", the search doesn't find the right results anymore. I created a couple of test pages, some of them with an accesscontrol - tag and some others without this tag. If I search for content that is in a few articles, I only get the message "MY:No Access ... There is currently no text in this page." Without this extension, I get a list with the results that I expected.
I hope for help.
- What version of extension did you use? --Want (talk) 07:37, 19 August 2019 (UTC)
Fundraising translation feedback
[edit]Hey Want,
I wanted to ask for your help. As you may be aware we have been running banners on many language wikis. We have a lot of new content this year and I really want to conduct a thorough review of our translations. This is a combination of feedback from the community, readers, donors as well as those with professional translator experience. This will help us ensure the highest quality of translations used in our messaging.
To help us out with this I wonder if you would be willing to give us feedback for Polish using This Link
Simply follow the simple instructions on that page and if you have any questions feel free to contact me on my talk page.
Many Thanks
Jseddon (WMF) (talk) 17:45, 26 March 2013 (UTC)
Translation admin
[edit]Hello Want. I hope you're doing okay. There's a question at your request in case you've not noticed. Best regards, —MarcoAurelio (talk) 16:13, 23 June 2019 (UTC)
- @MarcoAurelio:Thank you for your message. I am currently completing a new version of the extension mw:Extension:AccessControl and writing a manual to it, so the translations must wait a while. In 10 days I leave for a month on vacation and I need to finish it. -- Want (talk) 06:29, 24 June 2019 (UTC)
- Good day. Thanks for replying. I've granted you the requested permissions. Best regards, —MarcoAurelio (talk) 12:52, 24 June 2019 (UTC)
- @MarcoAurelio: Thank you. --Want (talk) 13:30, 24 June 2019 (UTC)
AccessControl and VisualEditor
[edit]It seems that in AccessControl, a user in Read Only mode can successfully edit a page with the VisualEditor even if the history and edit option are not available. Is this a normal behavior?
- Certainly not. Analyze of this problem and simulate a similar situation is not easy. I know nothing about the content of page. Edit without Visual Editor it's ok? I don't use Visual Editor, because it produce invalid code for the complicate pages. Want (talk) 10:47, 3 February 2020 (UTC)
- I found out a way to solve the problem. What is happening is that VisualEditor wgAction is "view" and not "edit" (see here), this means that it bypass the
$wgAction['edit'] = falseblock. VisualEditor use a custom action namedveactioninstead. To counteract this I modified the following this bit of code in theuserVerify()function:
- I found out a way to solve the problem. What is happening is that VisualEditor wgAction is "view" and not "edit" (see here), this means that it bypass the
if ( $rights[VIEW][$wgUser->mName] ) {
return true;
} else {
- to the following:
if ( $rights[VIEW][$wgUser->mName] ) {
if ( $wgRequest->getText( 'veaction' ) ) {
return self::doRedirect( 'accesscontrol-redirect-users' );
} else {
return true;
}
} else {
- This stop the user from going with the &veaction=edit. However, one of the problem is that the "Edit" tab still allows access to the VisualEditor (but block access to the WikiCode Editore). I don't understand exactly why but the workaround for this is the remove completely the Edit tabs for those in ReadOnly mode. You may also remove the Edit link on each header (if this is activated in the option), since they are useless. The easiest, but probably non-elegant way to do this was to modify the
readOnlyUser()function to add$wgOutto theglobaland the following at the end of theif ( ! $wgReadOnlyUser )block (before$wgReadOnlyUser = true;for example):
- This stop the user from going with the &veaction=edit. However, one of the problem is that the "Edit" tab still allows access to the VisualEditor (but block access to the WikiCode Editore). I don't understand exactly why but the workaround for this is the remove completely the Edit tabs for those in ReadOnly mode. You may also remove the Edit link on each header (if this is activated in the option), since they are useless. The easiest, but probably non-elegant way to do this was to modify the
$wgOut->addInlineScript( "document.getElementById('ca-history') && document.getElementById('ca-history').parentNode.removeChild(document.getElementById('ca-history'));" );$wgOut->addInlineScript( "document.getElementById('ca-edit') && document.getElementById('ca-edit').parentNode.removeChild(document.getElementById('ca-edit'));" );$wgOut->addInlineScript( "document.getElementById('ca-ve-edit') && document.getElementById('ca-ve-edit').parentNode.removeChild(document.getElementById('ca-ve-edit'));" );$wgOut->addInlineScript( "Array.from(document.getElementsByClassName('mw-editsection')).map(element => element.parentNode.removeChild(element));" );
- The first three lines remove the Edit tab and the History one (since it is blocked anyway). The last line remove the Edit direct link from the header. This will block the use from going through internal page link and direct address.
Discussion on correcting typos on svg
[edit]
Message added Peaceray (talk) 13:49, 24 April 2023 (UTC). You can remove this notice at any time.
Updates from Capacity Exchange (CapX)!
[edit]
Hello Want,
My name is Joris Darlington Quarshie, and I am an Outreach Facilitator for the Capacity Exchange (CapX) — a platform for finding and connecting with peers to exchange knowledge and skills on a global level.
CapX is a community-built tool, designed by and for the Wikimedia Movement, to make it easier for Wikimedians across the world to find and connect, collaborate, and exchange skills and knowledge with peers.
If you don't know it yet, I invite you to access capx.toolforge.org and create your user profile with your Wikimedia account. But, if you already have a profile, I invite you to check out the new features and possibilities we just launched. I am sure you will be delighted.
CapX's new version incorporates valuable community feedback gathered over the past months, including the Organization Profile - a feature for Wikimedia affiliates, initiatives, or community groups to create their own CapX presence (see here how to create yours).
Click to log in using your Wikimedia unified account through authentication:
Explore CapX's new features
[edit]→ Access: capx.toolforge.org
→ Watch the launch video:Meet the Capacity Exchange
→ Navigate CapX's User Guide and Frequently Asked Questions
→ Share your profile on Meta by adding the predefinition {{CapacityExchange}} to your userpage.
→ Visit our Meta Page for all documentation on the project
→ Join our telegram channel: Capx Telegram Group
Please, let me know if you think your community would enjoy a presentation, workshop demonstration, or feedback session. I would be happy to support you on that. Just reach out, and we can schedule the best date and time together.
Best regards,
Joris Darlington Quarshie
Outreach Facilitator,
Capacity Exchange Project – Wikimedia Brasil
MediaWiki message delivery (talk) 16:02, 29 October 2025 (UTC)
Join us for “Many Tongues, One Movement: Voices Across Languages”!
[edit]
Hello Want,
We’re excited to invite you to an inspiring global virtual gathering: the first Capacity Exchange Translat-a-thon.
Together with Language Diversity Hub, the Capacity Exchange (CapX) team will host its first Translation Marathon dedicated to ensuring linguistic equity in access to this amazing tool aimed to connect Wikimedians.
If you enjoy contributing to Wikimedia projects through translating and adapting content into different languages, this event is for you! Join us in the celebration of the multilingual spirit of the Wikimedia Movement at an event where communities that contribute in diverse languages will be able to share local knowledge and collaborate across borders.
Many Tongues, One Movement: Voices Across Languages
- Date: December 6, 2025
- Time: 12 PM (UTC) - Check the event page for your local timezone
- Location: Online (Meta-Wiki + live session links)
If you can’t join the live event, you can still contribute to the translations! Edits will be counted for two weeks, until December 20th. And everyone who participates will receive a special badge to display on their CapX profiles.
Strengthen your collaboration through CapX
[edit]
We invite you and your community to join the Capacity Exchange (CapX), a Wikimedia community-built platform for connecting, collaborating, and exchanging skills with peers across the movement.
CapX helps Wikimedians and organizations find each other, share expertise, and build stronger, more connected communities.
Whether you’re an individual contributor, a user group, a community initiative or an affiliate, CapX helps you grow through knowledge exchange.
More information
[edit]→ Explore the CapX platform: capx.toolforge.org
→ Read: User Guide & FAQ
→ Watch: Meet the Capacity Exchange video
→ Join our Telegram community chat: CapX Telegram Group
If your community, usergroup or affiliate would like to have a CapX organization profile, please reach out at capx@wmnobrasil.org, and we’d be delighted to support you.
With warm regards,
Joris Darlington Quarshie
Outreach Facilitator,
Capacity Exchange Project – Wikimedia Brasil
MediaWiki message delivery (talk) 14:55, 13 November 2025 (UTC)