Open Source enthusiast and contributor.
User Details
- User Since
- Feb 20 2024, 3:52 PM (102 w, 4 d)
- Availability
- Available
- LDAP User
- Unknown
- MediaWiki User
- Destiny Obamwonyi [ Global Accounts ]
Jan 30 2025
Dec 28 2024
Hi, I have pushed the fix, 1107054
please let me know if there is anything else. Also I tried to replicate the issue locally for verification of my fix and I was unable too. My main blocker was creating a privilege user or assigning privilege to user with my admin account.
OK, thanks.
first is it the en.json at "Translate/i18n/core/en.json", if it is, I have been looking for a key that has anything related to special aggregate group so I can add the message to it, but I am unable to find any. If am supposed to create a key value pair for it , then what's the naming convention for creating the key so it will load properly.
Dec 27 2024
OK, let me attempt it.
Dec 23 2024
Hi, can I work on this ?
Dec 19 2024
Sorry @Amarjitsinghbca have you already raised a PR for the task, if you have has it been merged? so I can close my PR as it is yet to be reviewed.
Dec 17 2024
I was able to find this property and values representation in the en.json file , Note this is after applying my fix and they where not declared together.
{
"session-page-restricted": "{{GENDER:$1|He|She|They}} is not authorized to edit this page using the current grant",
"block-success": "[[Special:Contributions/$1|{{GENDER:$1|He|She|They}}]] has been blocked. See the [[Special:BlockList|block list]] to review blocks.",
"unblocked": "[[User:$1|{{GENDER:$1|He|She|They}}]] has been unblocked.",
"session-page-restricted": "{{GENDER:$1|He|She|They}} is not authorized to edit this page using the current grant",
}I was unable to find such configurations for Centralauth-renameuser-merged, and Userrenametool-success
I have been able to narrow the problem down to the file en.json in the languages/i18n folder. I hope this is the right place to implement the fix ?
Dec 16 2024
Hi @srishakatux take a look at this Pull Request
Hi, I will like to take this on
Nov 25 2024
Hi, can you add information on how to replicate this issue?
Nov 18 2024
Sep 30 2024
Sep 26 2024
@Jdlrobson, Yes I did use Darkmode extension, I will remove it and follow you suggestion. Let me try that for now.
Sep 25 2024
I tried replicating this issue locally, but I am unable to. Below is the normal view of the babel in light mode
- Light Mode (Image 1)
Sep 23 2024
You're welcome Sir, do have a great day.
This is the patch, link
Hi, please I have submitted a patch for this, and it has been merged, but the status is still flagged as a bug, so I don't know if there is something else to fix?
Also please note, when I mean my MediaViewer I mean I am currently running a local setup of Mediawiki and MediaViewer, I also saw the issue in the link you provided. I am just trying to replicate it in my local setup, then add a patch, verify that the patch is working and push as a branch, as stated above.
Also I think the reason the trademark is coloured blue is because it's a link, so making the blue brighter might be a good suggestion as white will not make it stand out as a link.
Hi, I am currently testing the media viewer to replicate the Issue , so far I cannot do so, my Media Viewer does not show any trademark
this is a picture of my Media Viewer below
Sep 22 2024
Hi, I know Python and CSS, can I take up this task?
Please I have been able to fix this, I used the exact for of cloning the project provided in the url below .
Hi @Jonesey95 , I am still finding it difficult to replicate the bug . Also it would be great to add response on the What should have happened instead?: part of the bug format, also I can hardly tell how the links above helps replicate it as I am unable to find the issue, please any add on guide would be very help full towards fixing the bug.
Hi, does the above need a fix, I don't mind trying to fix it, if it's necessary?
Aug 6 2024
Ok, the reason I asked is that after installing the specified version of MediaWiki, mine worked perfectly even after installing oathauth, when I checked MySQL to see if there was any database virtual, there was no such thing, also when creating the LocalSettings.php file some of this information are requested, like the database name and user, by default it uses root, so if the default was left as root it might course the reason of denied permission. So maybe a little context on what the virtual database is about would help. Thanks for your response so far.
I have followed the steps above, and so far I have been unable to replicate the issue. Is it possible to know the exact update script that was ran
e.g
php maintenance/run.php update
also what was the database name and database username that was filled when creating the LocalSettings.php file ?
lastly it will also help to know the means of installation, be it with tar ball or gerrit repo, I used that of tar ball for my test so far.
Aug 5 2024
OK, thanks
Hi, please is this issue still open?
If yes can I work on it?
Apr 5 2024
Mar 31 2024
Hi @Novem_Linguae , has this bug been fixed ?
Mar 28 2024
Mar 21 2024
Mar 20 2024
Please I think a lot of bugs has been fixed in the fabricator but are still being left as bugs, cause when I replicate some of the bugs I realize they have been fixed , is this correct or are all the bugs in the phabricator still unfixed?
Hi is this a good replica of the bug
I tried to replicate this and it seems like the problem has been fixed. as all the pages I created (15) are being loaded with no timeout .
Mar 19 2024
Mar 18 2024
Hi, I have applied a fix to this task and it worked, I have made a push, and the images are below.
Mar 16 2024
core/extensions/PageTriage/modules/ext.pageTriage.newPagesFeed/stores/settings.js (file path)
const initState = () => {
// Named users store params ( user-centric ) in a user option, other users store params in localStorage ( client-centric )
const stored = mw.user.options.get( 'userjs-NewPagesFeedFilterOptions', localStorage.getItem( 'userjs-NewPagesFeedFilterOptions' ) );
return {
immediate: JSON.parse( JSON.stringify( defaultImmediate ) ),
controlMenuOpen: false,
applied: JSON.parse( JSON.stringify( defaultSettings ) ),
unsaved: JSON.parse( JSON.stringify( defaultSettings ) ),
// Load stored API parameters if possible, else defaults
params: JSON.parse( stored ) || defaultParams,
currentFilteredCount: -1,
// this is the fix I have applied
selected: "all",
};
};Ok, thanks.
Mar 15 2024
Hi @Soda, Can I immediately see the changes I make in the PageTriage extension while I apply the fix? I tend to find the termination of the container(docker-compose down) and restarting (docker-compose up) quite redundant. It takes some time before the changes reflect, this makes me feel like the changes are not implemented or are not working. Any help would be appreciated.
Mar 14 2024
Hi @Novem_Linguae , I have set that of 07 to Resolved(closed). Hope this did not course any problem?
Ok, it was a network issue.
Mar 4 2024
Hi @AndrewTavis , I am a python and django developer , this is my current stack in the company I intern at and I am very familiar with python programming , would love to learn more about wikidata while working on this task.
Hi @Yaron_Koren my name is Destiny I would love it if I am added/ allowed to contribute to this please , I have the skill specified above with almost 2 years of working experience in terms of gigs and company wise .







