Hello!
I wanted to try AJAX, so i switched it on in my MW 1.9.0:
$wgUseAjax = true;
$wgAjaxSearch = true;
$wgAjaxWatch = true;
Now, when I try to type the name of an article in the searchbox of my wiki, i
get an error-message-popup:
Error: 500 Internal Server Error
Parser::replaceInternalLinks: $this->mTitle is null
Whats wrong?
Regards,
Jan
Hi,
I tried to upload my site to free.fr, but I got the message
PHP 5.0.x is buggy on your 64-bit system; you must upgrade to PHP 5.1.x or
higher. ABORTING. (http://bugs.php.net/bug.php?id=34879 for details)
Where can I find a provider using "PHP 5.1.x or higher" ? I live in France
near Paris.
cheers
Klaus
Having spent a day re-reading TFM and Googling, I am getting
no closer to solving a problem with parser functions not working.
Something complicated like DPL works like a charm, but not something
basic like {{#if: {{{x|}}}|yes|no}} which renders as {{#if: |yes|no}}.
Obviously I am missing something /really/ fundamental! I believe it
is installed correctly:
Special pages Special:Version:
* MediaWiki: 1.10.1
* PHP: 5.2.0 (cgi-fcgi)
* MySQL: 4.1.21-standard
Parser hooks
DynamicPageList2 (version 1.3.1)
ParserFunctions
Extension functions
wfSetupParserFunctions, wf_include, wfDynamicPageList3 and wfDynamicPageList2
Parser function hooks
#expr, #if, #ifeq, #ifexpr, #switch, #ifexist, #time, dpl, int, ns, urlencode, lcfirst, ucfirst, lc, uc, localurl, localurle, fullurl, fullurle, formatnum, grammar, plural, numberofpages, numberofusers, numberofarticles, numberoffiles, numberofadmins, numberofedits, language, padleft, padright, anchorencode, special and defaultsort
$ grep ParserFunctions LocalSettings.php
require_once( "$IP/extensions/ParserFunctions/ParserFunctions.php" );
$ ls extensions/ParserFunctions/ParserFunctions.php
extensions/ParserFunctions/ParserFunctions.php
ls extensions/ExtensionFunctions.php
extensions/ExtensionFunctions.php
Any hints on how to fix this would be much appreciated!
Thanks -- Frank
Dear list,
a quick search through the list archives didn't bring up a result so
please excuse me if this issue has been solved already.
I am currently using Mediawiki 1.9.2. and experienced problems uploading
PNG images.
Although my test image shows an 'image/png'-mimetype with 'file -i',
Mediawiki keeps saying the file was corrupted.
Monitoring /tmp/php* while uploading the image again shows the uploaded
file to be image/png, too:
while(usleep 1); do file -i /tmp/php*|grep -v "ERROR"; done
/tmp/phpksjpPO: image/png
Mediawiki debug says
MimeMagic::detectMimeType: magic mime type of /tmp/phpcDoKKE:
text/plain
amongst other things, so I guess MimeMagic isn't working correctly..
Searching the meta wiki gives me the hint to add
$wgMimeDetectorCommand = "/usr/bin/file -bi";
to LocalSettings.php as a workaround, which actually does the trick.
But still I wonder: What's the problem with MimeMagic?
Thanks,
Sebastian
Hi,
is there a way to integrate an additional js-file without editing the
header.
A look at for example the category-extension a special js-file is stored
in the extension folder. But how is this integrated in the wiki?
regards
mic
I've some sort of problem with the glossary extension.
The following lines should read the glossary page and they simply do in a
normal case.
$title = Title::makeTitle( null , 'Glossary' );
$emoticonListArticle = new Article( $title );
$content = $emoticonListArticle->getContent();
But if an oldid is set (permanent link on article), they aren't reading the
glossary, but the text of the actual article.
Is this a normal behaviour of mediawiki? Can anyone tell my why this
happens?
Hi,
I would like to build an extension for MediaWiki (MW) to make citing
scientific publications easier / more 'natural'. This extension will
be used for my private 'literature wiki', and so requires features
that are not strictly generally useful for MW. However, I think that a
lot of general principles should apply to this project that could
carry over to MW in general.
Below I will outline my thinking. I would like to get feedback on
these ideas, because basically I am very new at MW. Additionally, I
want to organize a list of resources related to this project, and
hopefully this will help me do that.
== First, why not just use an existing extension? ==
* http://en.wikipedia.org/wiki/WP:Citing_Sources#How_to_cite_sources
* http://en.wikipedia.org/wiki/Wikipedia:Citation_templates
* http://en.wikipedia.org/wiki/Wikipedia:Footnotes
In short, I find these methods clunky. Although these tools go a long
way towards providing proper citation support to MW, I think they fall
short in several respects;
* They are somewhat tricky to learn and implement.
* The specific citation data for a given source cannot be
automatically generated (AFAIK).
* Sources are not reusable across pages (sources are not independent 'objects').
* The format of the citation is not user configurable (there no scope
for setting format preferences).
The above list of missing features comes from my perspective as a
scientific student. I write papers citing articles that are mostly
from PubMed using tools like BibTeX, TexMed and Endnote. Typically the
'citation process' has a simple 'pipeline'.
1. Click 'insert citation' or type a citation keyword.
2. A) Select an existing citation from a personal collection or B)
perform a database search to download the citation data into a
collection.
3. Later - configure the citation style and print.
Of course things can differ from the above pattern, such as
occasionally having to manually type the citation details, however, in
general this is the pattern used by most scientists (I think).
I would like to build a system to allow this kind of pattern to be
implemented in MediaWiki.
Some of these issues are addressed by the following extensions;
And;
* http://www.mediawiki.org/wiki/Extension:PagesOnDemand (and PMID_OnDemand)
* http://www.mediawiki.org/wiki/Extension:ProcessCite
* http://www.mediawiki.org/wiki/Extension:Biblio
== Second, describing the system I have in mind. ==
Right! I am getting quite bogged down with the following description,
so lets keep it simple to begin with.
Lets assume that you want to insert a citation from an article listed
in PubMed. This 'source' is found by searching PubMed and has PMID =
1234567. Associated with this PMID is the citation data; title, year,
journal and abstract.
Every cited source will have its own page in the Wiki, called a
'source page'. Each source page will be an instance of a standard
'source template'. Particular source pages can then be dropped into a
regular page as needed.
Making a separate page for each source already provides advantages.
However, two 'magic' steps are still missing and need to be described;
1. Automatically 'instantiating' the source template in the source
page with data from PubMed.
2. Formatting the references in pages using citations.
These steps are described (in outline) in more detail below.
== Third, detailed use case. ==
While writing a scientific article the user types "bla bla
bla{{cite:myKey}}", where myKey is a personal citation keyword that
can be anything at all but will probably be a mnemonic for the desired
source. Lets assume that 'myKey' refers to a new 'source' that has not
been cited before. After saving the page {{cite:myKey}} shows up in
the text as a red link ("Template:Cite:myKey").
Clicking the red link will trigger some 'magic' (using the
PagesOnDemand extension). The 'magic' presents a user with the
"Template:Cite:myKey" page preloaded with a special 'PubMed search'
template.
The PubMed search template allows the user to (surprisingly) search
PubMed. For example of the PHP code required see 'Librarian';
http://bioinformatics.org/project/?group_id=131
>From here it gets a bit tricky... The PubMed search template is
obviously special, and needs to do a lot of things;
1. Lets say after performing a search, a particular 'source' article
is selected from PubMed (lets say with PubMed Unique Identifier
PMID:1234567).
2) The citation data returned from PubMed is used to automatically
instantiate a "PubMed source" template, automatically passing data to
the various fields of the template.
3) This 'instance' is saved into a 'standard' source template page,
something like "Template:PubMed source:PMID:1234567".
4) Finally the 'standard' template is automatically embedded
(transcluded) into the "Template:Cite:myKey" page.
5) The user is left viewing the saved "Template:Cite:myKey" page,
which contains only "{{PubMed source:PMID:1234567}}".
So... (at least) two things have now happened. 1) A "PubMed source"
template has been automatically instantiated with data from PubMed and
saved as a 'standard source'. ii) A layer of abstraction has been put
between the standard source and the mnemonic via template
transclusion. Viewing "Template:Cite:myKey" or "Template:PubMed
source:PMID:1234567" presents all the citation details (including the
abstract).
Viewing a page which calls {{Cite:myKey}} requires more magic ...
The citation should appear as a number in the text and automatically
add itself to a reference listing with a fixed style at the bottom of
the page (like Categories do). This should not require the user to
call a specific <references/> tag, but should happen automatically.
The format of the citation needs to be controlled by CSS.
== Sooo... ==
I now see that almost all of the above is done by PagesOnDemand and
ProcessCite as demonstrated on EcoliWiki. What is missing is the AJAX
search box and the automatic formatting (via CSS). I think that using
the above as a starting point, I can code the AJAX search box, first
presenting the user with a search interface, allowing a selection to
be made, filling in the template and showing the resulting page.
However, I am not sure how to begin to make the references appear
automatically in the way categories do, and I don't know how to set up
the layout to work in conjunction with CSS ...
Any feedback on any of the above (polite or otherwise) is most welcome!
Cheers,
Dan.
P.S.
The following list of extensions look relevant for this project;
* Bibtex
* Cite
* ProcessCite
* DynamicPageList
* CreateArticle
* CreateBox
* PagesOnDemand
* PMID_OnDemand
* Biblio
Also;
http://www.mediawiki.org/wiki/Markup_spec/BNF/Magic_links
I am about to move our wiki to a new server, and I think I've got the
whole moving the database part down, but is there a way to redirect all
pages (links) to the new server? I know I can redirect index.php with
just a normal redirect...so no worries there....but that will just
bounce them to the main page. What about if they are coming straight to
an article they have bookmarked or linked to?
Example...say a page link was:
http://originalserver/gecwiki/index.php/Acronyms
but will now be:
http://newserver/gecwiki/index.php/Acronyms
Thanks,
Dave