Re: [Wikitech-l] Error when using OOjs UI/Windows/Message Dialogs

[Shanika Ediriweera]

I found the resource loader file.

What should I add here?

// Windows and dialogs module.
$modules['oojs-ui-windows'] = [
'scripts' => 'resources/lib/oojs-ui/oojs-ui-windows.js',
'skinStyles' => $getSkinSpecific( 'windows' ),
'dependencies' => 'oojs-ui-core',
'messages' => [
'ooui-dialog-message-accept',
'ooui-dialog-message-reject',
'ooui-dialog-process-continue',
'ooui-dialog-process-dismiss',
'ooui-dialog-process-error',
'ooui-dialog-process-retry',
],
'targets' => [ 'desktop', 'mobile' ],
];

Best Regards,

Shanika Ediriweera
Undergraduate
Dept. of Computer Science & Eng.
University of Moratuwa

On 23 February 2017 at 05:40, Shanika Ediriweera 
wrote:

> Yes. I am working on a special page in the mediawiki core.
>
> Could you please tell me where is the resource loader modue located?
>
> Best Regards,
>
> Shanika Ediriweera
> Undergraduate
> Dept. of Computer Science & Eng.
> University of Moratuwa
>
> On 23 February 2017 at 02:15, Bartosz Dziewoński 
> wrote:
>
>> Looks like you're not loading the OOjs UI code you're trying to use.
>> Assuming that you're writing this as part of MediaWiki (or an extension),
>> you need to add a dependency on the 'oojs-ui' ResourceLoader module.
>>
>> --
>> Bartosz Dziewoński
>>
>> ___
>> Wikitech-l mailing list
>> Wikitech-l@lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>
>
>
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Error when using OOjs UI/Windows/Message Dialogs

[Shanika Ediriweera]

Yes. I am working on a special page in the mediawiki core.

Could you please tell me where is the resource loader modue located?

Best Regards,

Shanika Ediriweera
Undergraduate
Dept. of Computer Science & Eng.
University of Moratuwa

On 23 February 2017 at 02:15, Bartosz Dziewoński 
wrote:

> Looks like you're not loading the OOjs UI code you're trying to use.
> Assuming that you're writing this as part of MediaWiki (or an extension),
> you need to add a dependency on the 'oojs-ui' ResourceLoader module.
>
> --
> Bartosz Dziewoński
>
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Integrating Parsoid & RESTbase into a secure MediaWiki Install

[John P. New]

To wrap this up, I managed to get SSL to RESTbase working, but using CPanel 
AutoSSL instead of LetsEncrypt. AutoSSL and LetsEncrypt are similar services 
but I used AutoSSL because my main mediawiki install is served on CPanel.

In a nutshell, I
) Created a sub-domain, mw.mywikidomain.com. The associated SSL certificate was 
automatically created.
) Pointed the DNS entry for mw.mywikidomain.com to my home server IP address
) Exported the certificate and key entries into an stunnel install running on 
my home server and listening on port 7232.
) Changed the $wgVisualEditorRestbaseURL and $wgVisualEditorFullRestbaseURL to 
point to https://mw.mydomain.com:7232/mywikidomain.com/v1/page/html/ and 
https://mw.mydomain.com:7232/mywikidomain.com/, respectively.

Thanks for the help.

John

On February 22, 2017 10:14:54 AM John P. New wrote:
> 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


___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] www.wikipedia.org portal incident report 2017-02-22

[Jan Drewniak]

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-portals

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
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] 2017-02-22 Scrum of Scrums meeting notes

[Grace Gellerman]

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/T158245
https://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,dashboards/default

== Wikidata ==
* Same as last week, making good progress on Lexeme datatype for
Wiktionary, as well 

Re: [Wikitech-l] Error when using OOjs UI/Windows/Message Dialogs

[Bartosz Dziewoński]

Looks like you're not loading the OOjs UI code you're trying to use. 
Assuming that you're writing this as part of MediaWiki (or an 
extension), you need to add a dependency on the 'oojs-ui' ResourceLoader 
module.


--
Bartosz Dziewoński

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Integrating Parsoid & RESTbase into a secure MediaWiki Install

[Gergo Tisza]

On Wed, Feb 22, 2017 at 7:14 AM, John P. New  wrote:

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

VE calls are proxied through the wiki; you can serve them in SSL but make
the wiki -> Parsoid server calls in plaintext.
That said, you should definitely use Let's Encrypt; it's very easy to set
up and you have one less script injection / cookie stealing vulnerability.
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Integrating Parsoid & RESTbase into a secure MediaWiki Install

[John P. New]

I had thought of LetsEncrypt, but I was under the (mistaken) impression that 
SSL certificates are bound to the IP address as well as the hostname of the 
server. Upon further investigation, I see that SSL certificates are not IP 
address dependent.

I'll give it a try, thanks.

On February 22, 2017 04:57:30 PM Alex Monk wrote:
> You can get a trusted cert for your home server. Look into LetsEncrypt.
> 
> On 22 Feb 2017 3:15 pm, "John P. New"  wrote:
> 
> > 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


___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Integrating Parsoid & RESTbase into a secure MediaWiki Install

[Alex Monk]

You can get a trusted cert for your home server. Look into LetsEncrypt.

On 22 Feb 2017 3:15 pm, "John P. New"  wrote:

> 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
>
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Integrating Parsoid & RESTbase into a secure MediaWiki Install

[John P. New]

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

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l