On 27.03.2012 00:33, Tim Starling wrote:
> For the record: we've discussed this previously and I'm fine with it.
> It's a well thought-out proposal, and the only request I had was to
> ensure that the DB schema supports some similar projects that we have
> in the idea pile, like multiple parser versions.
Thanks Tim! The one important bit I'd like to hear from you is... do you think
it is feasible to get this not only implemented but also reviewed and deployed
by August?... We are on a tight schedule with Wikidata, and this functionality
is a major blocker.
I think implementing ContentHandlers for MediaWiki would have a lot of benefits
for the future, but if it's not feasible to get it in quickly, I have to think
of an alternative way to implement structured data storage.
To answer my own question, the whitespace was being consumed because
of the adjacent <noinclude> and <includeonly> style tags. It appears
that there are two ways you could solve this:
1) use   to get a space that isn't encoded as ' '
2) use <nowiki/> after the space so that the other tags see the
adjacent nowiki tag and not whitespace that they gobble up.
I used #1 and my template expands as expected now.
"The Direct3D Graphics Pipeline" -- DirectX 9 version available for download
Legalize Adulthood! <http://legalizeadulthood.wordpress.com>
On Mon, Mar 26, 2012 at 12:50, Maximilian Doerr <cybernet678(a)yahoo.com> wrote:
> I strongly disagree with removing wiki text. Several thousand bots depend
> on it. Especially Cluebot NG which is a highly sophisticated anti-vandalism
> bot. I recommend going our current route where the visual editor writes the
> Wikimarkup realtime and vice versa.
I suspect maybe you didn't understand Daniel's message? (or didn't
read it?) I imagine most pages will still use the same markup we have
today after his idea is implemented.
For the pages that are different, the bots can and should adapt.
Hi all. I have a bold proposal (read: evil plan).
To put it briefly: I want to remove the assumption that MediaWiki pages contain
always wikitext. Instead, I propose a pluggable handler system for different
types of content, similar to what we have for file uploads. So, I propose to
associate a "content model" identifier with each page, and have handlers for
each model that provide serialization, rendering, an editor, etc.
The background is that the Wikidata project needs a way to store structured data
(JSON) on wiki pages instead of wikitext. Having a pluggable system would solve
that problem along with several others, like doing away with the special cases
for JS/CSS, the ability to maintain categories etc separate from body text,
manage Gadgets sanely on a wiki page, or several other things (see the link below).
I have described my plans in more detail on meta:
A very rough prototype is in a dev branch here:
Please let me know what you think (here on the list, preferably, not on the talk
page there, at least for now).
Note that we *definitely* need this ability for Wikidata. We could do it
differently, but I think this would be the cleanest solution, and would have a
lot of mid- and long term benefits, even if it's a short term pain. I'm
presenting my plan here to find out if I'm on the right track, and whether it is
feasible to put this on the road map for 1.20. It would be my (and the Wikidata
team's) priority to implement this and see it through before Wikimania. I'm
convinced we have the manpower to get it done.
After adding $wgShowExceptionDetails = true; to LocalSettings.php
Non-string key given
#0 $wikipath/includes/GlobalFunctions.php(781): MessageCache->get(NULL,
#1 $wikipath/includes/GlobalFunctions.php(902): wfMsgGetKey(NULL, true,
#2 $wikipath/languages/Language.php(513): wfMsgExt(NULL, Array)
#3 $wikipath/languages/Language.php(525): Language->getMessageFromDB(NULL)
#4 $wikipath/languages/Language.php(799): Language->getMonthName(false)
#5 $wikipath/languages/Language.php(1560): Language->sprintfDate('H:i, j F
#10 [internal function]: wfSpecialUserlogin(NULL, Object(SpecialPage))
call_user_func('wfSpecialUserlo...', NULL, Object(SpecialPage))
#12 $wikipath/includes/SpecialPage.php(578): SpecialPage->execute(NULL)
MediaWiki->performRequestForTitle(Object(Title), NULL, Object(OutputPage),
The actual registration goes through because I can't re-register a nick
after this error. From the stacktrace I'm guessing the problem is sending
No idea how to debug, any pointers would be much appreciated.
Thanks in advance,
I made a small infobox to control the currentness of data. I wonder if
it is possible to declare a categorie out of this infobox?
Instead of filling out the infobox in a firtst step and including the
categorie in an other: just add a line to my infobox where my users can
type in the desired categorie.
|Michael Renner E-mail: michael.renner(a)gmx.de |
|81541 Munich skype: michael.renner.gmx.de |
|Germany Don't drink as root! ESC:wq
Why does the button in MediaWiki say "Save Page"?
I might be editing a section, so it could say "Save Section" or maybe
Don't Leave Space To The Professionals!
Wgen trying to upgrade MediaWiki installation 1.17.0 to 1.18.2, the following happens when running ,aintenance/update.php:
Fatal error: Call to a member function getDbType() on a non-object in maintenance/doMaintenance.php on line 91
(all upgrade steps are made as recommended in the supplied document).
The DB is garbled after that, I had to reverse both files and reload DB dump to have site back in working state.
Is the above a known problem? PHP version is 5.2.17.
I am doing the project voice based home automation. I have tried to convert
the voice into text.But i am not able to code in matlab properly. I saw the
similar project in this link
Please can anyone send me the source code for this project. It ll be
helpful to compare my coding with that.
Thanks & Regards
Final Year Undergraduate Student
SSN College of Engineering