Dec 12 2019
@Jdrewniak it appears there is confusion regarding this bug ticket by QA/web reading team. I have a wikifarm set up consisting of 9 wikis, the issue is occurring on 4 wikis which is ~45%. I followed installation steps for MinervaNeue skin and Extension:MobileFrontEnd, this should not be occurring on latest mediawiki stable - 1.33.1 (a security release for 1.33)
wait, you want me to modify mediawiki core files?
Dec 11 2019
skinStyles/mediawiki.ui.icon does not exist, I am still confused what is causing the drop down button to remain hidden for 1.33.1 (security release) on Google Chrome 78. Is it possible that Google made a breaking change regarding MinervaNeue?
Dec 7 2019
Checked the submitted patch with a +2 in code review yet unable to locate the file referenced by patch....skinStyles/mediawiki.ui.icon/mediawiki.ui.icon.less
I would like to have a working mobile skin for current stable release instead of waiting 2 releases
Dec 3 2019
This is occurring on Google Chrome 78 on Windows 10. No impact in Mozilla Firefox, button displays.
Nov 27 2019
@Masumrezarock100 no notification icons are showing up despite Echo installed
Nov 23 2019
It appears after running update.php multiple times, the tables are now created...not sure what happened
It appears after running update.php multiple times, the tables are now created...not sure what happened - resolved issues for both Abusefilter and Checkuser
though this doesn't explain why when running update.php that the required tables are not being created. whether I have a single wiki or a group of wikis shouldn't make an impact...
Nov 22 2019
Nov 20 2019
Is it possible that update.php is forgetting about the actor table migration?
I can always just directly run the sql commands to create the tables required.
@Daimona I tried alternative 1, it sort of worked - its showing up in special:version. database errors remain...I removed all of the abusefilter tables from all the wikis installed and ran update.php again. I am trying to install on my own wikifarm, doubt that would complicate things. using alternative equivalent to MySQL.
@Nux Wouldn't a simply way to utilize another namespace where the script or gadget is copied too and anyone that is authorized to make changes only touch that copied version? This way there wouldn't be any merge conflicts when merging back upon reviewer approval and the scripts/gadgets in MediaWiki namespace would be locked as production - live for viewers/users.
Nov 19 2019
Nov 17 2019
If we allow forking these to user css/json/js pages, when merging back there could be edit conflicts considering another edit could have been merged and the user didn't pull. How would you suggest keeping a fork to user namespace be kept up to date, might need to keep track of diff changes - this gets complicated? Sending the fork to another namespace and keeping it in one location is much better. I am suggesting a simpler system due to these projects not being finished ie partial blocks was meant to become multi-blocks.
Nov 16 2019
@JEumerus clarified my side note, yeah it was confusing. I was meaning to refer to how js, json, css pages under MediaWiki were split out, did not mean to suggest that EditInterface was a new permission.
Nov 15 2019
@DannyS712 isn't that the current system that Wikipedia already uses?
Oct 27 2019
Oct 21 2018
Oct 6 2018
Oct 3 2018
thanks for letting me know about T205482. Given that Flagged Revs gave me an internal error (VM1844:1 Uncaught TypeError: Cannot read property 'addPortletLink' of undefined) for trying to add in MediaWiki namespace, I do not think that placing effort and time into solving T205482 is worth it.
Sep 11 2018
Aug 26 2018
"enforcement of abusefilters", I mean to actually filter new threads/replies to WikiForum or new comments in MediaWikiChat.
Aug 25 2018
Apr 29 2018
Apr 28 2018
Dec 24 2017
Now under MediaWiki 1.29.2, FireFox console tells me
Exception in module-execute in module ext.onlineStatus: ReferenceError: hookEvent is not defined ReferenceError: hookEvent is not defined
If I disable Extension:OnlineStatus, it goes away
Dec 18 2017
Yes, this is a feature request for a button that allows quick reactivation of a disabled filter due to safeguards being exceeded.
Dec 17 2017
Dec 11 2017
updating to mediawiki 1.29.2 and PHP 7.0 resolved all issues, including Extension:WikiForums also causing similar internal error upon upgrading mediawiki from mediawiki 1.29.1.
Dec 3 2017
Ok i'll look into getting cache set up properly
I disabled extensions MassMessage, VoteNY, Comments, BlogPage and now the internal server error went away...any idea why this came to be? Everything is fine now.
Dec 2 2017
The 500 internal server error occurs if I simply try to visit the wiki website, it just instantly crashes. Disabling a few other extensions didn't help. Didn't install that many extensions
I ran a strace command, It appears that the application crashes while trying to do a number of sequential INSERTs into the database. I have attached the output file.
Nov 30 2017
Its being converted to extension registration per T152865. The segfault/internal 500 error happens upon enabling the two extensions in question, are you running master branch of AbuseFilter and SocialProfile? Keeping either AbuseFilter or SocialProfile enabled is ok, but not both. This is for mediawiki 1.29.1.
64 bit Debian Linux running Apache 2.4.10
PHP 5.6.32 (cgi-fcgi)
SocialProfile version 1.13 (ede9c86) 02:46, 4 November 2017
Nov 29 2017
The exact error after enabling the extension is that the PHP interpreter crashes (segmentation fault).
Nov 22 2017
Nov 19 2017
This is an interesting idea and I support this since currently the method of delete is nuking from the SQL database resulting in complete loss. In order to restore, this requires to first store deleted items in a temporary SQL table for later restore.
Oct 17 2017
Oct 7 2017
apparently not using mw.load.loader() to execute scripts via index.php and just simply hosting all the code inside mediawiki:common.js apparently doesn't throw the above errors even when denied writeapi & Extension:Lockdown is used.
Oct 6 2017
Sep 20 2017
Splitting this into two tasks is a good idea as they are different enough. Allowing admins to remove offensive content, vandalism and leave talk page message by default is expected. yes, for now admin request would have to do until this is built.
Sep 19 2017
another possibility outside of Gadget 2 is a test wiki where any JS, CSS or Lua is tested and then moved over to the main WMF wikis after having a +2 code reviewer approve merging it over. The MediaWiki namespace is mostly interface messages, restricting JS & CSS editing to new permissions might make this safer as well; editusercssJS was split into separate permissions though seems to be limited use cases (someone breaking personal js/css).
Sep 16 2017
There also is Extension:CodeReview but status is historical reference, perhaps reopening that for development would be a potential solution?
Jul 18 2017
Jul 16 2017
Since you mentioned that uploads are "edits" rather than uploads, you can target file uploads using the following
Jun 3 2017
Jun 2 2017
May 22 2017
The error was in relation to a rewrite rule in .htaccess
May 20 2017
While a private blacklist under user preferences would be ideal, upon leaving a message the user would find out either by checking if message was left or a warning. Now it could be implemented as a fake edit but...any determined user would just start abusing account creation making this useless along with the worst case scenario of a proxy being involved.
running MediaWiki 1.28.2, I can still reproduce the problems as further detailed below.
Link to wiki: http://www.hypoverse.com/wiki/Main_Page I have reopened creating accounts, let me know so i can grant access to creating public test filters.
I have tried to create a test filter with conditions
May 19 2017
May 17 2017
@matmarex @Aklapper The same warning appears throughout the wiki (http://www.hypoverse.com). Removing everything from MediaWiki:Common.js, resulted in same above error message. I already checked if there was something missing from load.php, there was none compared to MediaWiki 1.28.2. Is it possible that something is corrupted, the domain was canceled and later reactivated a few weeks later?
Apr 22 2017
Apr 5 2017
Apr 4 2017
Apr 3 2017
tried both git format-patch -M origin/master, git format-patch -1 --stdout HEAD
I just updated my draft with a direct link to my GitHub solution and claimed the task for now.
Its in my GitHub for now, honestly thinking this is technical issue unless there is a hidden step missing from the documentation pages.
Ok so I generated my SSH keys and linked gerrit and wikitech, do i need to be added to the developer's group?
every time i run git clone ssh://<username>@gerrit.wikimedia.org:29418/mediawiki/core.git it tells me
if there a way to push a code commit without using git?
Apr 2 2017
I got the following error after running vagrant up in git
would that be problematic?