31 Jan
2015
31 Jan
'15
1:54 p.m.
NGIH THOMAS TANSA
SICA
BAMENDA
PHONE,NO.699163636
N,WEST REGION
03-02-15
tansahthoma(a)yahoo.com
thomastansahthomas(a)yahoo.com
kenlilianlilianken(a)yahoo.com
On Sat, 1/31/15, mediawiki-l-request(a)lists.wikimedia.org
<mediawiki-l-request(a)lists.wikimedia.org> wrote:
Subject: MediaWiki-l Digest, Vol 136, Issue 35
To: mediawiki-l(a)lists.wikimedia.org
Date: Saturday, January 31, 2015, 1:00 PM
Send MediaWiki-l mailing list
submissions to
mediawiki-l(a)lists.wikimedia.org
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
or, via email, send a message with subject or body 'help'
to
mediawiki-l-request(a)lists.wikimedia.org
You can reach the person managing the list at
mediawiki-l-owner(a)lists.wikimedia.org
When replying, please edit your Subject line so it is more
specific
than "Re: Contents of MediaWiki-l digest..."
Today's Topics:
1. Re: LiquidThreads backstory? (Max
Semenik)
2. Re: SVG thumbnailing (Brenton Horne)
3. Re: Problems with Special:ActiveUsers
since update from 1.22
to 1.24 (Jakub Klinkovský)
----------------------------------------------------------------------
Message: 1
Date: Fri, 30 Jan 2015 16:40:26 -0800
From: Max Semenik <maxsem.wiki(a)gmail.com>
To: MediaWiki announcements and site admin list
<mediawiki-l(a)lists.wikimedia.org>
Subject: Re: [MediaWiki-l] LiquidThreads backstory?
Message-ID:
<CAGgaK7+F=zdwNrhknzz4=a1Q0MjQ-xgqDvg0D09eiOppg9M8Zg(a)mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
On Fri, Jan 30, 2015 at 10:11 AM, Jason Ji <jason.y.ji(a)gmail.com>
wrote:
The bad part of LQT is not about interaction with watchlist.
It will be
essentially untouched by any trimming short of complete
rewrite.
If you fork something, you will have to maintain it forever
- why not put
the same effort in contributing to mainline instead? And
Flow is quite
complete for most use cases, and its team is mostly working
on adding
support for various crazy workflows user communities have
created in more
than 10 years without a good discussion system. I don't
think you need to
wait for these.
> If you can, try switching the SVG renderer
to rsvg,
which is the tool we
> use on Wikipedia:
> * install 'librsvg' (and if
necessary 'librsvg-bin')
package on the system;
> * in LocalSettings.php set:
> $wgSVGConverter = 'rsvg';
> As for the borders and such, you probably need to copy
some CSS styles from
> the [[MediaWiki:Common.css]] page from Wikipedia.
> -- brion
> On Thu, Jan 29, 2015 at 6:34 PM, Brenton Horne
<brentonhorne77(a)gmail.com>
> wrote:
>> Hi,
>>
>> I've noticed that SVG thumbnailing on my new
locally-hosted Wiki is
------------------------------
Message: 3
Date: Sat, 31 Jan 2015 12:55:22 +0100
From: Jakub Klinkovský <j.l.k(a)gmx.com>
To: MediaWiki announcements and site admin list
<mediawiki-l(a)lists.wikimedia.org>
Cc: aschulz(a)wikimedia.org,
ori(a)wikimedia.org
Subject: Re: [MediaWiki-l] Problems with Special:ActiveUsers
since
update from 1.22 to 1.24
Message-ID: <20150131115522.GG3377(a)jlknb.lan>
Content-Type: text/plain; charset="utf-8"
On 28.01.15 at 13:57, Bartosz Dziewoński wrote:
Thanks for your feedback. To clarify a bit, we're
not
thinking of using
LiquidThreads as it is - we have a different extension
we will be building,
with some different needs than LQT has. For example,
we
may not need any
integration with watchlists. So our thought is that we
might fork LQT and
modify it to suit our needs. We're still very
early in
the design phase.
Max - when you say just use Flow, do you mean we
should
fork the Flow code
base and work from there, or that we should just
install Flow? Flow looks
interesting, but we're not sure it will have the
features we need, and our
timeframe is likely to be shorter than the timeframe
of
Flow development.
Is there somewhere I can go read in detail about the
bugs and unfixable
problems with LQT? We might not fork LQT at all, but
we
were also thinking
of using wiki pages to store comment text. So if that
idea is fundamentally
broken, it would be great to know why.
I already explained why, bugs are here:
https://phabricator.wikimedia.org/search/query/ojED3mdcIKDQ/
--
Best regards,
Max Semenik ([[User:MaxSem]])
------------------------------
Message: 2
Date: Sat, 31 Jan 2015 13:32:39 +1000
From: Brenton Horne <brentonhorne77(a)gmail.com>
To: MediaWiki announcements and site admin list
<mediawiki-l(a)lists.wikimedia.org>
Subject: Re: [MediaWiki-l] SVG thumbnailing
Message-ID: <54CC4CD7.4020008(a)gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
librsvg didn't work. I've installed it via cygwin (I'm
running Windows 7
64 bit). I even directed MediaWiki (via $wgSVGConverterPath
=
'C:\cygwin64\usr\include\librsvg-2.0\librsvg';) towards the
directory
where it is installed. Any other ideas?
On 31/01/2015 5:11 AM, Brion Vibber wrote:
It looks like you're defaulting to converting SVGs
using ImageMagick, which
can be a bit flaky (and there also seems to be a
version mismatch where it
> doesn't like the options being given to it.)
should be available in standard Linux package managers
as it's a library
used by GNOME desktop. Also available through Homebrew
on Macs. Not sure
> about Windows. :)
> thumbnailing svgs incorrectly. This is what it
appears like atm when
> incorporated into an infobox:
http://i.stack.imgur.com/dRWkj.png.
> Likewise I've also noticed there's no
enclosing box
around infoboxes in my
> Wiki, which you can also see in this image. This
is
the sort of infobox
> formatting I'd like
http://i.stack.imgur.com/aI0Tx.png.
Thanks for your time,
Brenton
_______________________________________________
MediaWiki-l mailing list
To unsubscribe, go to:
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
_______________________________________________
MediaWiki-l mailing list
To unsubscribe, go to:
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l The special page was rewritten in MediaWiki 1.23 to
make it usable on wikis
the size of Wikipedia (commit 87be24db /
https://gerrit.wikimedia.org/r/#/c/110299/
and some follow-up changes).
Unfortunately this optimization for massive wikis
seems
to have caused the
performance to suffer on smaller ones a bit.
(I have no answer to your problems, just saying this.
:( Perhaps it helps
someone else help you.)
--
Bartosz Dziewoński
I've also noticed that with each time the
Special:ActiveUsers page is reloaded,
the time value in the message
You are viewing a cached version of this page, which
can be up to ... old.
is decreased by 20 minutes on the "small" wikis, and by 10
minutes on "large"
wikis such as Wikipedia. The message of the above linked
commit is
Made ActiveUsers use querycache and do staggered
updates on view
Is this what "staggered updates" are supposed to do? Does
the cached page age
really depend on how frequently it is loaded by users? This
would explain why
the age is over 29 days for small wikis, while large wikis
serve ~1day old page.
CC'ing the author and committer of the change, so that we
don't have to
speculate anymore... The original post of this thread can be
viewed here:
https://lists.wikimedia.org/pipermail/mediawiki-l/2015-January/043850.html
--
Jakub Klinkovský
3363
days inactive
3363
days old
mediawiki-l@lists.wikimedia.org
0 comments
1 participants
participants (1)
-
kenlilian lilianken