Not sure whether I should make this task as resolved and public, but it's done on our side now, so moving on the Cosmos workboard.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Oct 17 2020
Change 627977 merged by jenkins-bot:
[mediawiki/extensions/DonationInterface@master] Fix usages of deprecated PHPUnit methods
In T248418#6557816, @Aklapper wrote:@Iniquity: If you run into specific bugs, then please file specific bug reports with clear steps to reproduce (URLs, web browser and version and operating system, etc) as specific bug reports are off-topic here (this task is about deploying a piece of software instead). Thanks.
@Iniquity: If you run into specific bugs, then please file specific bug reports with clear steps to reproduce (URLs, web browser and version and operating system, etc) as specific bug reports are off-topic here (this task is about deploying a piece of software instead). Thanks.
In T258017#6557809, @gerritbot wrote:Change 634755 had a related patch set uploaded (by Catrope; owner: Catrope):
[mediawiki/extensions/GrowthExperiments@master] StartEditingDialog: Make image in difficulty banner top aligned, fix padding
While working on the big 24px->16px change mentioned in T258019#6557184, I noticed that the text in the difficulty banner in the variant C onboarding dialog was vertically centered on desktop, but should instead be top-aligned according to the mocks. The attached patch fixes that in both variant A and variant C.
Patches rolled-out to master, REL1_35, and REL1_34:
Change 634755 had a related patch set uploaded (by Catrope; owner: Catrope):
[mediawiki/extensions/GrowthExperiments@master] StartEditingDialog: Make image in difficulty banner top aligned, fix padding
Change 634755 had a related patch set uploaded (by Catrope; owner: Catrope):
[mediawiki/extensions/GrowthExperiments@master] StartEditingDialog: Make image in difficulty banner top aligned, fix padding
UploadAvatar extends UploadFromFile, which extends UploadBase, which defines the performUpload() function. Since 1.35, it introduces the $watchlistExpiry parameter, so the method signatures don't match now; this causes a PHP exception to throw.
Change 634754 merged by Andrew Bogott:
[operations/puppet@production] wmcs admin scripts: added wmcs-imageusage
Change 634754 had a related patch set uploaded (by Andrew Bogott; owner: Andrew Bogott):
[operations/puppet@production] wmcs admin scripts: added wmcs-imageusage
So this database column was dropped in master branch, but not in the REL1_34 branch, however last time I worked on SocialProfile, the master branch was the branch that users were expected to use and is expected to be stable with the latest stable version of MediaWiki.
Change 634753 had a related patch set uploaded (by He7d3r; owner: He7d3r):
[mediawiki/core@master] Add 'external' class to links generated by jQueryMsg
Looks like this column was dropped in the SQL patch at https://github.com/wikimedia/mediawiki-extensions-SocialProfile/blob/master/UserGifts/sql/patches/actor/drop-gift_creator_user_id.sql but there's still code trying to access this SQL column
Change 634742 merged by jenkins-bot:
[mediawiki/skins/Cosmos@master] README: Explain how to contribute and properly a report a security issue
Hi @Aklapper,
This issue is occurring on mobile, using the safari iOS app, not on the web browser. As I indicated in the steps I laid out, you have to go to https://en.m.wikipedia.org/wiki/Main_Page with Safari for iOS 14.0.1.
In T202989#6557749, @Amorymeltzer wrote:In T202989#6557660, @Thryduulf wrote:There is no justification for preventing administrators viewing or restoring this.
Well, for restoring there is. Undeletion (in particular selective restoration after deletion) is tantamount to editing, which would otherwise be prohibited; depending on the page, that could also mean execution of code by users.
2FA logins are global, so this would mean someone taking over an xywiki bureaucrat account could check which valuable accounts on large wikis are easy targets. Once T150898: Force OATHAuth (2FA) for certain user groups in Wikimedia production gets enforced, that might be an acceptable risk, as account takeover is not terribly damaging for non-sensitive accounts; for now, I'm not sure it is a good idea.
Change 634341 merged by jenkins-bot:
[mediawiki/core@master] Use Title::getArticleID instead of Title::exists for internal check
In T248418#6557761, @kaldari wrote:The UX still works fine for me, including for audio files. I guess we'll have to agree to disagree.
Buttons overlap each other, how can it works? :)
The UX still works fine for me, including for audio files. I guess we'll have to agree to disagree.
Please I don't know what I did wrong.
Hi everyone. I'm Lola, an Outreachy applicant; a little late to the party I'm afraid. But I'd really love to contribute to this interesting project.
In T225897#6557227, @MGA73 wrote:It seems that structured data breaks old revisions. Not just for random files but for ALL files. So soon we have 60 million files on Commons where the old revisions are broken.
In T248418#6549116, @kaldari wrote:I am not sure that T258622: Poor display of media on Special:NewFiles is personal opinion :)
Regardless of whether its an opinion or not, it's purely a cosmetic issue. I don't think that should block deployment, personally.
In T245349#6550112, @matthiasmullie wrote:This (finally - thanks @Tgr!) got merged.
@Jarekt or @Multichill, any chance either of you could verify that this got fixed? (happy to wait if it's too much hassle to try to reproduce!)
Change 634748 had a related patch set uploaded (by Ammarpad; owner: Ammarpad):
[mediawiki/core@master] Expand DoctrineSchemaBuilderTest
@Amamgbu that is correct and @Vanevela pointed to the appropriate prior discussion about this. More details: the restrictiontypes field is just what restrictions could be applied to the page, not which ones are applied -- a fuller description of what you could find in that field can be found here. For most pages, you'll see edit and move and can verify this by choosing a random page without restrictions and querying the API. I'd suggest ignoring the field as it won't tell you much.
In T202989#6557660, @Thryduulf wrote:There is no justification for preventing administrators viewing or restoring this.
(Removing Design Research tools and infrastructure as per its description. Also removing task subscribers added without an obvious reason (please avoid).)
SVG language name handling is a mess on many levels.
For WMF wikis, we should probably expand the suppression policy to specifically allow for this type of removal. Feedback is welcome at https://meta.wikimedia.org/wiki/Talk:Oversight_policy#Expand_for_malicious_code_removal
Note that smssolidale.wikimedia.it is a redirect to a domain that is not handled by this server. So, replaced:
I think it's quite confusing that the Docker-Hub-MediaWiki repository is at https://github.com/wikimedia/mediawiki-docker. This suggest that it is related to MediaWiki-Docker.
Note that monzaebrianza.wikilovesmonuments.it is a redirect to a domain that is not handled by this server. So, replaced:
Nobody can answer this anymore, I guess, and no links either.
$ sudo certbot certonly --webroot --webroot-path=/var/www/wmw/worddona -d dona.wikimedia.it Saving debug log to /var/log/letsencrypt/letsencrypt.log Plugins selected: Authenticator webroot, Installer None Starting new HTTPS connection (1): acme-v02.api.letsencrypt.org Obtaining a new certificate
Note that valledaosta.wikilovesmonuments.it is a redirect to a domain that is not handled by this server. So, replaced:
Not as high of a priority now, since most are done. (not all are done yet, just two left)
Wikimedia-India mailing list: https://lists.wikimedia.org/pipermail/wikimediaindia-l/2020-October/014767.html
MediaWiki-India mailing list: https://lists.wikimedia.org/pipermail/mediawiki-india/2020-October/000105.html
Change 634742 had a related patch set uploaded (by SamanthaNguyen; owner: SamanthaNguyen):
[mediawiki/skins/Cosmos@master] README: Explain how to contribute and properly a report a security issue
Thanks. Closing as resolved via the Add Action... → Change Status dropdown.