Want

Welcome to Meta!

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

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

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

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

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'] = false block. VisualEditor use a custom action named veaction instead. To counteract this I modified the following this bit of code in the userVerify() function:

    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 $wgOut to the global and the following at the end of the if ( ! $wgReadOnlyUser ) block (before $wgReadOnlyUser = true; for example):

$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.

--HtheChemist (talk) 16:11, 4 February 2020 (UTC)

Discussion on correcting typos on svg

Hello, Want. You have new messages at wikipedia:en:User talk:Peaceray#Correcting typos on svg.
Message added Peaceray (talk) 13:49, 24 April 2023 (UTC). You can remove this notice at any time.