But some changes were hard to adapt, for example at some point the definition
of SpecialPage::userCanExecute() changed from
public function userCanExecute( $user )
to
public function userCanExecute( User $user )
with typecheck. Then extension's special pages that inherited from SpecialPage
an
9 Январь 2013 г. 4:09:21 пользователь James Forrester
(jforres...@wikimedia.org) написал:
On 4 January 2013 09:02, Mark A. Hershberger wrote:
> Would it be possible to adapt the Visual Editor to run under 1.19?
Possible? Yes. However, it would involve back-porting a number of
changes that hav
On 01/08/2013 07:08 PM, James Forrester wrote:
> On 4 January 2013 09:02, Mark A. Hershberger wrote:
>> Would it be possible to adapt the Visual Editor to run under 1.19?
>
> Possible? Yes. However, it would involve back-porting a number of
> changes that have been made to core since then
Oh, so
On 9 January 2013 00:08, James Forrester wrote:
> Understood (though I didn't know about 1.19 being an LTS release; who
> is doing the supporting, exactly, and what does 'support' entail here?
> [*] is unclear…).
Tarball version is "supported" (security fixes, etc) for the purpose
of not having
On 4 January 2013 09:02, Mark A. Hershberger wrote:
> Would it be possible to adapt the Visual Editor to run under 1.19?
Possible? Yes. However, it would involve back-porting a number of
changes that have been made to core since then (and will no-doubt
continue to be added as we discover new ways
Am 04.01.2013 19:57, schrieb Mark A. Hershberger:
> Even more reason for us to get VE working against 1.19. I saw that
> some people have added instructions for FCKeditor on 1.19, but VE
> would be much more compelling if we can get it working.
Yes!
Switching between MediaWiki Wiki syntax and th
On 01/04/2013 01:26 PM, Thomas Gries wrote:
> I must warn users, because the FCKeditor as such has known security issues.
Even more reason for us to get VE working against 1.19. I saw that some
people have added instructions for FCKeditor on 1.19, but VE would be
much more compelling if we can ge
Am 04.01.2013 18:02, schrieb Mark A. Hershberger:
>
> * FCKeditor is no longer supported for MediaWiki, but people are still
> using it and, for some reason, like what it provides. If we can make
> the Visual Editor available to them, I'm hoping the need for FCKeditor
> will disappear.
Hi Mark,
an
On 01/04/2013 09:02 AM, Mark A. Hershberger wrote:
> There is a dependency on Parsoid and node.js, of course, that a
> FCKeditor doesn't need, but I'm assuming right now that if MediaWiki
> works with the extension, then the Parsoid instance will just run.
This should be the case. Parsoid only int
On Fri, Jan 4, 2013 at 10:04 AM, David Gerard wrote:
> On 4 January 2013 17:02, Mark A. Hershberger wrote:
>
> > Is anyone else interested in helping to make this happen?
>
>
> I have no coding ability but would LOVE this for our work 1.19
> instances, and would be most pleased to test.
>
>
I th
On 4 January 2013 17:02, Mark A. Hershberger wrote:
> Is anyone else interested in helping to make this happen?
I have no coding ability but would LOVE this for our work 1.19
instances, and would be most pleased to test.
- d.
___
Wikitech-l mailing
Would it be possible to adapt the Visual Editor to run under 1.19?
I have a couple of reasons for wanting that:
* 1.19 is our LTS release. Visual Editor looks awesome and I'd like to
provide people who are stuck on older versions of MediaWiki with a
persuasive reason to upgrade to 1.19 at least.
12 matches
Mail list logo
