In my opinion, parsing .js and .css as wikitext is a borken idea.
Add some kind of pragmas to the page and strip them off in the ResourceLoader.
John
On Fri, Oct 19, 2012 at 12:44 AM, MZMcBride wrote:
> Krinkle wrote:
>> On Oct 18, 2012, at 5:04 AM, Daniel Kinzler wrote:
>>> When designing the C
Chad wrote:
> I rather prefer this format, to be honest. And actually, Gerrit
> has a feature (we're not making use of, but we easily could
> if people are interested) where you can track those bug footer
> notes. We could easily add regexes for Bugzilla and RT (gerrit
> calls them "tracking ids")
Hey,
> Then unset it at the point when you collect it, just before it is saved.
It'd be great if we could do that, since it's both simple and does not
raise compat concerns. However, we are collecting it after it is saved as
far as I can tell, in which case this is not going to work.
The propert
On 20/10/12 09:12, Jeroen De Dauw wrote:
> Hey,
>
> Is there currently a way for extensions to register additional info they
> gather during the parsing process to the parser output? Right now Semantic
> MediaWiki is doing this by assigning to the non-defined field $mSMWData
> which causes notices
I think an rc2 is a good idea. The "Known Issues" section of the
RELEASE-NOTES-1.20 has shrunk and I've used Platonides comments to
update that section so that people can see whether or not they are
affected. In any case here is what it looks like (with some editing of
my own for this email:
* (
Hey Tim,
The notice is
Notice: Undefined property: ParserOutput::$mSMWData in
/home/j/www/phase3/extensions/SemanticMediaWiki/includes/SMW_ParseData.php
on line 170
Looking at this again I figure it might indeed not be set and that I
accidentally fixed this while updating the code to use the mod
On 22/10/12 11:26, Jeroen De Dauw wrote:
> In any case, do you think it's fine for extensions to set such non-defined
> fields, or would it be better to go in the direction of the patch that's on
> gerrit? https://gerrit.wikimedia.org/r/#/c/28767/
I think it's fine for extensions to continue to se
MediaWiki Bugzilla Report for October 15, 2012 - October 22, 2012
Status changes this week
Bugs NEW : 338
Bugs ASSIGNED : 76
Bugs REOPENED : 42
Bugs RESOLVED
