Hello,
For quite sometime now, we wanted to get PHPUnit code coverage reports
to be generated automatically for us [BUG 31518]. This is now generated
by Jenkins and made available at the following URL:
https://integration.wikimedia.org/cover/mediawiki-core/master/php/
The interface let you browse our code base and find areas of our code
that could use some unit tests :-)
[BUG 31518] https://bugzilla.wikimedia.org/31518
--
Antoine "hashar" Musso
ACTUALLY, I forgot to mention that runjobs does not solve this problem at all. Also, I can't "touch" the page like I was doing because that causes a new edit and my scripts detect it and causes problems... a wordaround would be nasty. I noticed the "Last editor is" special property but it doesn't seem to be sent. <shrug>
________________________________
From: jason zhang <jasonzhang2002(a)gmail.com>
To: Al Johnson <alj62888(a)yahoo.com>
Sent: Monday, March 25, 2013 1:17 PM
Subject: Re: [Semediawiki-user] "Touching" a page to force update
Hi, AI
You can run "php maintainence/runJobsphp" as cron job in a rapid pace
to refresh your page at background.
-jason
On Sun, Mar 24, 2013 at 8:34 PM, Al Johnson <alj62888(a)yahoo.com> wrote:
> Hi all,
>
> I have a page form that includes a template that calls another template that does an #ask query to populate the page with data from another semantic "data" page in another namespace. When data is updated on the data page, the page that uses it can't be updated to reflect the new data because it can't detect the change I guess because it is too far removed. I can "touch" the page via the API with an sfautoedit that does nothing, but I was wondering if there was any other way, such as from the form that updates the data on the data page.
>
> I hope that didn't sound too convoluted, but I'm sure the experts will understand ;-)
>
> Thanks,
> Al
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_d2d_mar
> _______________________________________________
> Semediawiki-user mailing list
> Semediawiki-user(a)lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/semediawiki-user
--
-jiesheng
Just a heads up: we need your MediaWiki expertise to help building a
strong Google Summer of Code proposal. Feedback and mentors welcome at
http://www.mediawiki.org/wiki/Talk:Mentorship_programs/Possible_projects
-------- Original Message --------
Subject: Re: [Wikitech-l] Missing project ideas AND MENTORS for GSOC
Date: Sun, 24 Mar 2013 14:27:43 -0700
From: Quim Gil <qgil(a)wikimedia.org>
Organization: Wikimedia Foundation
To: wikitech-l(a)lists.wikimedia.org
Ok, let's move the discussion to
http://www.mediawiki.org/wiki/Talk:Mentorship_programs/Possible_projects
because this final sprint requires (hopefully!) many posts from many people.
Please go there if you want to help any of these candidates:
* Gadgets: needs at least one project idea and one mentor.
* Write useful Lua modules: needs at least one project idea and one mentor.
* Phase out the Vector extension; merge the good parts into core: needs
maintainers' buy-in, a defined project scope and at least one mentor.
* Work on outstanding Parsoid bugs and/or add features: needs at least
one project idea and one mentor.
* Improve Extension:CSS: needs more feedback from security & MediaWiki
developers. (discussion thread)
* Add support for x3d 3D files to MediaWiki: needs more feedback from 3D
savvy users and developers and at least one mentor.
* Improve the mediawiki-bugzilla extension to a deployable level: needs
Bug Squad buy-in and at least one mentor.
* Work on RefToolbar: needs discussion (work on the extension or on a
VisualEditor module?) and at least one mentor.
* co-ment-like tool for inline comments: needs at least one mentor.
* Build an interwiki notifications framework and implement it for
InstantCommons: needs Commons feedback/buy-in and a second mentor.
* Browser Test Automation: needs at least one project idea.
* System documentation integrated in source code: needs more definition
(a MediaWiki extension to integrate source code docs?), feedback /
buy-in from MediaWiki developers and at least one mentor.
* Extension pages management: needs reasonable project scope,
mediawiki.org community buy-in and at least one mentor.
--
Quim Gil
Technical Contributor Coordinator @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
Hi guys!
Suppose I have the page Těžiště. By default it's URL will be ended on
T%C4%9B%C5%BEi%C5%A1t%C4%9B . If I install Extension:Ascii_Translit
[1] will make transliteration and the end of the URL will be "Teziste"
I would love to have such an extension for other language,
specifically Russian and Ukrainian, so that "Перестройка" will be
transliterated to "Perestroika". Does anyone know something like that?
[1] http://www.mediawiki.org/wiki/Extension:Ascii_Translit -
-----
Yury Katkov, WikiVote
There is now a dictionary of many words found in MediaWiki software in our
core repository at *maintenance/dictionary/mediawiki.dic* If your IDE
supports code/comment spell checking, you can attach it to hide many false
errors.
The file is a one-per-line list of words. Please keep it sorted and without
duplicates.
If you use JetBrains' *PhpStorm*, go to File/Settings/Spelling, and add the
directory (not the file) to the dictionaries tab. Adding new words to
dictionary place them into mediawiki\.idea\dictionaries\User.xml or
sometimes to %userprofile%\.WebIde60\config\options\cachedDictionary.xml,
so you have to manually copy them to the .dic file, unescape xml &xxx;
entries, and sort/remove dupls.
I'm a dev for PracticalPlants.org, a semantic wiki of plant use
information. We've had long running mysterious problems with Cite which
have been difficult to pin down, but since upgrading to MW 1.20.3 and
Cite 1.20, the problem has become much worse.
All our references on plant articles are at least 2 templates deep -
the first template is a template used with semantic forms, the second
is the Ref template we use.
The result is that Cite outputs the following Cite error for every reference:
Cite error: <ref> tag with name "PFAFimport-1" defined in <references>
is not used in prior text.
The ref tag name is most certainly used in the prior text in all cases.
The <references> tag is placed after all <ref> (actually {{#tag:ref}})
calls.
If I place a <ref name="PFAFimport-1"/> or use our ref template {{Ref |
PFAFimport-1}} directly in the wikitext after the semantic forms
template then Cite lists it, so it seems like it's something to do with
it being in a second level template. Again, the ref tag with that name
is certainly being output, and indeed it's rendered inline as a
reference, it just fails to list it in the <references> section.
Has anyone experienced anything similar? Anyone have any ideas?