Hello, does anyone here know why the parser insists on adding p tags
to HTML results returned by parser functions?
I'm trying to upgrade the TreeAndMenu extension to work with MediaWiki
1.19 and I can't get the parser to stop adding p tags throughout the
result returned by the parser-function
Hello
Toolserver is not responding on GU:WP.. So that members of Gujarati Wikipedia
cannot see the stats of Gu:Wp..
See this link is not opening
http://toolserver.org/~tparis/pcount/index.php?name=Harsh4101991lang=guwiki=wikipedia
So Kindly do something to resolve this problem.
Thanks
Harsh
On Sep 27, 2012 12:19 PM, Harsh Kothari harshkothari...@gmail.com wrote:
Toolserver is not responding on GU:WP.. So that members of Gujarati
Wikipedia cannot see the stats of Gu:Wp..
See this link is not opening
On Sep 25, 2012 12:15 PM, IAlex ialex.w...@gmail.com wrote:
Would it be possible to have the whole changes as an changeset on Gerrit?
This would make review and comments much easier than having to do this on
this list.
Yes and no. The person that merges the branch can create a merge commit and
ccing both lists, dab just rebooted s3 which is probably the cause
On Thu, Sep 27, 2012 at 12:28 PM, Jeremy Baron jer...@tuxmachine.com wrote:
On Sep 27, 2012 12:19 PM, Harsh Kothari harshkothari...@gmail.com wrote:
Toolserver is not responding on GU:WP.. So that members of Gujarati
Wikipedia
On Thu, Sep 27, 2012 at 10:54 AM, Roan Kattouw roan.katt...@gmail.com wrote:
Yes and no. The person that merges the branch can create a merge commit and
submit that for review (git checkout -b mergewikidata master git merge
wikidata git review) but Gerrit will not show the diff properly:
On 27/09/2012 07:56, Aran Dunkley wrote:
Hello, does anyone here know why the parser insists on adding p tags
to HTML results returned by parser functions?
I'm trying to upgrade the TreeAndMenu extension to work with MediaWiki
1.19 and I can't get the parser to stop adding p tags throughout the
I removed all line breaks from the code being text being returned - but
the confusing thing is that the content being returned is marked as
isHTML (not wikitext) so the parser should be leaving it alone
completely and not checking for line breaks.
On 27/09/12 16:39, Isarra Yos wrote:
On
Daniel Kinzler dan...@brightbyte.de wrote:
So, my current proposal is a more expressive high-level api for transaction
control consisting of start/finish/flush (and perhaps abort) on top of the low
level interface consisting of begin/commit/rollback. Documentation needs to be
very clear on
On Fri, 21 Sep 2012 10:04:50 -0700, Gabriel Wicke gwi...@wikimedia.org
wrote:
On 09/20/2012 07:40 PM, MZMcBride wrote:
Scanning dumps (or really dealing with them in any form) is pretty
awful.
There's been some brainstorming in the past for how to set up a system
where
users (or
A bit of a side topic. But could someone point out some urls where the
deprecated/removed align attribute is used along with block elements that
are supposed to be centered too.
I've seen a lot of WikiText. But frankly, I have never seen any article or
template that even tried to use align
Sumana Harihareswara suma...@wikimedia.org wrote:
Git, Gerrit, and You! A Tutorial
Where:IRC/SIP/SSH
We want all our developers to feel comfortable with Git, git-review, and
Gerrit. So saper is leading a hands-on online training:
On Sun, Sep 23, 2012 at 7:59 PM, Brion Vibber br...@pobox.com wrote:
I've updated the patch to use the 'srcset' attribute as defined in the
current HTML 5 working group version, only using the density options and
not the width/height options:
Marcin Cieslak sa...@saper.info writes:
From the PostgreSQL side I see one problem with nesting - we are already
using savepoints to emulate MySQL's INSERT IGNORE and friends.\
It might be difficult to abuse that feature for something more than this.
There is a class SavepointPostgres which is
Am 27.09.2012 22:23, schrieb Aran Dunkley:
I removed all line breaks from the code being text being returned - but
the confusing thing is that the content being returned is marked as
isHTML (not wikitext) so the parser should be leaving it alone
completely and not checking for line breaks.
On 09/26/2012 03:24 PM, Sam Reed wrote:
Branching
a REL1_20 branch from say the point that 1.20wmf12 branched, and then also
backporting any relevant fixes from master makes sense. Pretty much how we
did
it for SVN, hopefully without the months and months of merging hell.
Sam emailed me
On Thu, Sep 27, 2012 at 08:40:13PM +, Marcin Cieslak wrote:
From the PostgreSQL side I see one problem with nesting - we are already
using savepoints to emulate MySQL's INSERT IGNORE and friends.\
It might be difficult to abuse that feature for something more than this.
There is a class
On 09/26/2012 01:54 PM, Krinkle wrote:
We're going towards a flexible modular system, which
means components have dependencies and build on each other - as opposed to
just
being there.
This sounds great, but I do see an important missing piece of
infrastructure.
First, I am absolutely in
Sounds somewhat viable. I know a number of other projects who use composer.
It would be interesting to try it out.
*--*
*Tyler Romeo*
Stevens Institute of Technology, Class of 2015
Major in Computer Science
www.whizkidztech.com | tylerro...@gmail.com
On Thu, Sep 27, 2012 at 9:47 PM, Mark A.
On Thu, 27 Sep 2012 18:47:41 -0700, Mark A. Hershberger
m...@everybody.org wrote:
On 09/26/2012 01:54 PM, Krinkle wrote:
We're going towards a flexible modular system, which
means components have dependencies and build on each other - as opposed
to just
being there.
This sounds great,
Daniel makes some good points. However, we still do need some sort of
better extension installation system besides our current clone and
require. So here's some things we might want to consider:
- Should this be a web-based system or something done with maintenance
scripts?
- Extensions
On Thu, 27 Sep 2012 21:10:40 -0700, Tyler Romeo tylerro...@gmail.com
wrote:
Daniel makes some good points. However, we still do need some sort of
better extension installation system besides our current clone and
require. So here's some things we might want to consider:
- Should this be a
22 matches
Mail list logo
