Hi,
I am working on a phabricator task and I need to use OOjs
UI/Windows/Message Dialogs (
https://www.mediawiki.org/wiki/OOjs_UI/Windows/Message_Dialogs) for a user
warning.
But
TypeError: OO.ui.MessageDialog is not a constructor
error occurs when I use:
var messageDialog = new OO.ui.MessageDialog();TypeError:
OO.ui.MessageDialog is not a constructor
What might be the problem?
Best Regards,
Shanika Ediriweera
Undergraduate
Dept. of Computer Science & Eng.
University of Moratuwa
Thanks to a couple of members of this list I was able to get Visual Editor working on my WikiMedia install.
Now I would like to run the wiki under SSL. Of course, as soon as I do, my browser complains of mixed content from the RESTbase server and won't load VE at all.
I am running MediaWiki 1.28 on a shared host, which means no access to node.js. So in order to run Parsoid and RESTbase I have installed both on my home server. As such, I have no way of getting a trusted SSL certificate for it; the most I could do is a self-signed certificate, which I am sure will cause as many browser complaints as the current mixed-content does.
My question is, what is the likelihood of getting this configuration to work under SSL?
John
Hello,
There was a severe bug with the page www.wikipedia.org for about an hour
today. Starting at about 6pm UTC and ending at 7:20 UTC, the text on that
page was invisible. This was due to an improperly cached javascript file
(which pointed to a 404). The URL of the file was purged and the page was
fixed, but some steps will be taken to prevent this in the future.
Full report is available at
https://wikitech.wikimedia.org/wiki/Incident_documentation/20170222-www-por…
but I'll paste it below anyway:
========
Summary
-------------
At about 5pm UTC Feb. 22 the www.wikipedia.org page was severely broken for
about an hour.
The text on the page was invisible. This bug was caused by a javascript
file being improperly cached and returning a 404.
Timeline
-----------
- A bug was filed at around 5:09pm UTC Feb.22 noting that the text on
www.wikipedia.org is invisible. T158782
- We were made aware of this bug at about 5:40pm UTC
- at 6:15pm UTC an attempt was made to rollback to the previous deploy. The
deploy was visible on mwdebug1002 without error, but the error persisted in
production.
- at 6:20pm UTC we purged the URL of the specific javascript file, fixing
the issue.
Conclusions
-----------------
- The wikipedia.org portal depends on a specific order of syncing followed
by purging urls, which is fragile and needs some rethinking.
- Errors in javascipt should not make the page unusable.
Actionables
---------------
Adding an entire list of asset URLs to purge (Task T158810)
Preventing javascript from hiding page content indefinitetly (Task T158809)
Use query params for cache-busting (Task T158808)
========
Jan Drewniak
UX Engineer, Discovery
Wikimedia Foundation
https://www.mediawiki.org/wiki/Scrum_of_scrums/2017-02-22
== Call outs ==
*Community Tech: Need feedback on proposed table for range contributions
https://phabricator.wikimedia.org/T156318
* Community Tech: Collation version numbering patch needs review
https://gerrit.wikimedia.org/r/#/c/272419/ (blocks
https://phabricator.wikimedia.org/T47611 )
* Services: RFC Discussion *REST API language variant support - *
https://phabricator.wikimedia.org/T154190
* Language: Blocked on mysterious Qunit test failures:
https://phabricator.wikimedia.org/T153038 (RelEng/Wikidata?)and schema
changes review from DBA: https://phabricator.wikimedia.org/T146450
= 2017-02-22 =
== Product ==
=== Reading ===
====Android====
* Last week:
** 2.5.189 beta released; production release is pending community feedback
on Wikidata description editing
** Mapbox library upgrade in review
** Android Support Library upgraded
* Next week (https://phabricator.wikimedia.org/project/view/2352/ ):
** Continue improving the offline experience
==== Web ====
* Current sprint:
https://phabricator.wikimedia.org/tag/reading-web-sprint-92-%F0%9F%8D%9C/
* Last week:
** Page Previews: Use bundler to generate Page Previews JavaScript code -
T156333
** Create reading depth schema - T155639
* This week:
** Update related pages schema to allow for current A/B test - T157375
** Page previews: use RESTBase in stage 0 wikis (italian, russian, greek,
catalan, hebrew) - T158221
** Deploy new mobile header to Catalan and Italian wikipedias - T156794
** [Spike] Propose solutions for the issues identified with developing on
MobileFrontend - T156263
==== iOS native app ====
* Last Week
** Continued work on 5.4
https://phabricator.wikimedia.org/project/view/2326/
*** Location permission changes (friendlier prompt, users to opt-in instead
of an intrusive pop-up)
*** Closer evaluation of Mapbox & maps.wikimedia.org as tileserver
*** Other bug fixes and enhancements
* This week
** Continue work on 5.4
*** Finish location permission changes, add links to places map from
Articles, Accessibility audit
*** Other bug fixes and enhancements
====Reading Infrastructure====
* Mobile Content Service: Kanban Board:
https://phabricator.wikimedia.org/project/view/2445/
** Adding more tests for OnThisDay; removing French from it since not all
dates produce a result
** Next: expanding TFA (today's featured article) to more languages using
FeaturedFeed extension
* working on TemplateStyles, ORES, MediaWiki logging
** TemplateStyles RfC: https://phabricator.wikimedia.org/T155813 -
performance questions still open + waiting for community consultation to
wrap up
==== Analytics ====
* Vetting wmf_last_access_global (project-wide unique devices) metric
* Applying feedback received from community to Wikistats2.0 and finalizing
visuals
* Upgrade to CDH 5.10 to labs, went well, real production deploy scheduled
for next tuesday 28th Feb
* In progress: fixing a bug in AQS (Pageview API) related to the way dates
are represented in the results
==== Community Tech =====
* Cookie blocks should go out this week
https://phabricator.wikimedia.org/T158129
* Investigating global gadgets https://phabricator.wikimedia.org/T153332
* Some improvements to PageAssessments
https://phabricator.wikimedia.org/T158245https://phabricator.wikimedia.org/T154216
* Need feedback on proposed table for range contributions
https://phabricator.wikimedia.org/T156318
=== Discovery ===
* No blockers
* A/B test for for sister wiki results finished, processing the results.
* Working on ES5 upgrade & wikidata search
* Working on annual plan & Collab Jam slides
=== Security===
Reviews:
- 3D extension
- Internal File Server
- CollaborationKit
- StopForumSpam
=== Services ===
* Blockers: None
* Updates:
** DNS caching in service-runner by default
*** https://phabricator.wikimedia.org/T158338
** REST API 1.0
*** https://github.com/wikimedia/restbase/pull/764
** *Language variant RFC* wrapping up right after this meeting
*** https://phabricator.wikimedia.org/T122942
=== Editing ===
==== Language ====
* Current Sprint:
https://phabricator.wikimedia.org/tag/language-2017_sprint_3/
* Compact Language Links deployed in 'svwiki'.
* CX migration to OOJS continue.
==== Collaboration ====
* Blocked
* Blocking
* Updates
** New RecentChanges page - Bug fixes and refactoring
** Flow - Minor technical debt and upgrading pimple (should have no user
impact)
** Will deploy an update ot the Flow export/import scripts that allow
transwiki within the farm. We'll use this shortly (probably today) to
transwiki a board fromMeta to MediaWiki.org
== German Technical Wishlist ==
* TwoColConflict is officially in Beta, watching for feedback.
* Working on FileImporter/Exporter to transfer files to Commons
https://gerrit.wikimedia.org/r/#/projects/mediawiki/extensions/FileImporter…
== Wikidata ==
* Same as last week, making good progress on Lexeme datatype for
Wiktionary, as well as federation for Commons.
* Will check if https://phabricator.wikimedia.org/T153038 is Wikidata
related.
==== UI Standardization ====
* This week
** Work on the technical fundament of style guide (responsive layout, grid,
navigation)
* Updates
** General
*** ContentTranslation: Сontribution's dropdown menu features non-standard
layout. https://phabricator.wikimedia.org/T157217
*** Further work on: Replace abandoned colors in current WMF/Wikimedia
products with WikimediaUI palette colors
https://phabricator.wikimedia.org/T148708
** OOjs UI:
*** Figure out which parts of OOjs UI documentation should be improved, and
where they should live - https://phabricator.wikimedia.org/T158494
*** Further improvements on form layouts in OOUI MW core forms for better
user experience – https://phabricator.wikimedia.org/T136790
*** Align SelectfileInputWidget to color palette
=== Technical Operations ===
* '''Blocked''':
** None
* '''Blocking''':
** None
* Updates:
** Work continues on Ubuntu Precise deprecation, production and labs
** Budgeting Capex / Opex and annual plan
** Datacenter switchover
** Asia datacenter preparation
=== Release Engineering ===
* '''Blocked''':
** None
* '''Blocking''':
** https://phabricator.wikimedia.org/T153038
=== Fundraising Tech ===
* Hiring replacement for Casey, who's turning devops
* More work on new PayPal integration:
https://phabricator.wikimedia.org/T107372,
https://phabricator.wikimedia.org/T153720
* Method to purge CentralNotice banners from caches:
https://phabricator.wikimedia.org/T154954
* Investigating slow banner saves: https://phabricator.wikimedia.org/T158084
** Andrew Green may ask ops for some help with both of the above ^^^
* More work resolving contact de-duplication conflicts in CiviCRM
Hi, here is a brief summary from last week's ArchCom meeting. Apologies for
the delay.
Internal discussions
-
Internal plans for cleaning up a provisional ArchCom charter.
-
How we manage the RfC board.
RFC activity
-
Entering Final Comment Period: T122942: Support language variants in the
REST API <https://phabricator.wikimedia.org/T122942>
-
Consensus has formed around using Accept-Language headers for now,
leaving path prefixes as a future addition.
-
Based on the discussion on the task, the ArchCom will either make a
decision or allow for more discussion in its meeting on
Wednesday, February
22nd.
-
T66214: Define an official thumb API
<https://phabricator.wikimedia.org/T66214>: Needs an update to the
summary to reflect the recent discussion, should be ready for last call
then.
--
Gabriel Wicke
Principal Engineer, Wikimedia Foundation
I've set up MW 1.28 with VE/parsoid and everything is working well
However, when I edit in (any) wikitext editor and try to switch to VE, I am presented with a dialog with only 2 choices: "Cancel" or "Discard my changes and switch". Diving into the code I found I could change ve.init.MWVESwitchConfirmDialog.js (line 58) from
modes: [ 'restbase' ]
to
modes: [ 'restbase', 'simple' ]
that adds "Switch" to the dialog box, but when this option is chosen, any changes made in the wikitext editor are lost.
Is this a mis-configuration on my part or is switching from edited wikitext to VE not supported? Do I need a RESTbase server to implement this functionality?
Hi,
I am working on the task "When moving, warn if people try to move to
Foo:Foo:Bar (repeated namespace)" - https://phabricator.wikimedia.org/T62399
.
What would be a good alert message for the users when there is repeated
namespace in title?
Thank you.
Best Regards,
Shanika Ediriweera
Undergraduate
Dept. of Computer Science & Eng.
University of Moratuwa
Hi folks,
Just letting you know that wm-bot logs will not be available for a day
or two, reason is required migration to different OS as current OS is
no longer accepted on wikimedia labs and all instances that are
running it have to be terminated.
If you want to track progress see https://phabricator.wikimedia.org/T157838
Bot is already up and running on new Debian instance and new logs are
being collected, but the web server and web scripts are still not
fully operational, we need to migrate about 3GB of text log files from
IRC channels and also postgre DB which has similar size (not sure how
to do that on-line, probably not even possible).
Having say that, there may be some more outages because of postgre
server switch, but they shouldn't be so much visible.
Sorry for turbulences and thank you for your patience
Hello Wikimedia technical contributors & developers:
Just sending one last reminder. The Wikimedia Foundation is asking for
your feedback
in a survey.
***The survey will close on February 15, 2017.***
We want to know how well we are supporting your contributions on and off
wiki, and how we can change or improve things in the future.[1] The
opinions you share will directly affect the current and future work of the
Wikimedia Foundation.
To say thank you for your time, we are giving away 10 Wikimedia T-shirts to
randomly selected people who take the survey.[2] The survey is available in
various languages and will take between 20 and 40 minutes.
Use this link to take the survey now:
https://wikimedia.qualtrics.com/SE/?SID=SV_6mTVlPf6O06r3mt&Aud=DEV&Src=DEV
You can find more information about this project here[3]. This survey is
hosted by a third-party service and governed by this privacy statement[4].
Please visit our frequently asked questions page to find more information
about this survey[5]. If you need additional help or have questions about
this survey, send an email to surveys(a)wikimedia.org.
Thank you!
Edward Galvez
Community Engagement
Wikimedia Foundation
[1] This survey is primarily meant to get feedback on the Wikimedia
Foundation's current work, not long-term strategy.
[2]Legal information we have to share: No purchase necessary. Must be the
age of majority to participate. Sponsored by the Wikimedia Foundation
located at 149 New Montgomery, San Francisco, CA, USA, 94105. Ends February
16, 2017. Void where prohibited. Follow this link for the contest rules:
https://meta.wikimedia.org/wiki/Community_Engagement_
Insights/2017_second_contest_rules
[3] About this survey:
https://meta.wikimedia.org/wiki/Community_Engagement_Insight
s/About_CE_Insights
[4] Privacy statement: https://wikimediafoundation.org/wiki/
Community_Engagement_Insights_2016_Survey_Privacy_Statement
[5] FAQ:
https://meta.wikimedia.org/wiki/Community_Engagement_Insight
s/Frequently_asked_questions
--
Edward Galvez
Evaluation Strategist (Survey Specialist), and
Affiliations Committee Liaison
Learning & Evaluation
Community Engagement
Wikimedia Foundation