On 03/07/2016 07:49 PM, Gabriel Wicke wrote:
tl;dr: You are *very* likely not affected.
As a Parsoid-side clarification, data-parsoid is considered private
information. This information is primarily used by Parsoid to minimize
dirty diffs when edited HTML is converted to wikitext. So,
tl;dr: You are *very* likely not affected.
We are planning two changes in the REST API:
1) Remove the experimental /page/html/ and /page/data-parsoid/
listings [1][2]. Our metrics show that these are essentially unused.
The same title listing remains available at /page/title/ [3].
2) Make the
On Mon, Mar 7, 2016 at 10:32 AM, Victor Danilchenko <
vdanilche...@cimpress.com> wrote:
> My simple solution to this is to forcibly invoke OutputPage::Output on the
> spot, right there in the 'BeforeInitialize' hook:
>
> $this->output->redirect($https_url, 301);
> $this->output->output();
>
Setting up a secure VisualEditor for private Wikis seems to have been a glaring
omission, but the Parsoid docs claim Parsoid is always necessarily running over
plaintext. So I added a section on setting up Parsoid over
Greetings Sylvian,
The Discovery department has been talking pretty actively with WMDE
about this very topic. We've already explored WikiData descriptions in
search results, brainstormed about how relevance functions could be
affected by WikiData, seen great community tools like ppp-sparql
Hi all,
I am running MediaWiki 1.26, and trying to force it to be all-SSL, all the
time, excepting a particular Special: page. To that end, I have code which
makes the following method call from a 'BeforeInitialize' hook:
$this->output->redirect($https_url, 301);
However, by the time
