Is it possible using API.php to search for page titles in a specified
namespace that have been last modified between two dates? I know I can use
rvprop to get revision history of pages but it requires one to specify which
pages. I kinda want to reverse that, specify the dates and return the page
names. I am guessing this can be done by using a generator to list all pages
and send it to prop?
Our wiki just has many old and outdated pages created over the past few
years and we want to remove these page. I am hoping to find a way to help
automate this process rather then going page by page ><
If it's not possible doing it via the API, is there some other alternative
method for doing this?
Walter Mazza
Hi,
What suggestions do you have for someone who has to set up a Wiki using
Mediawiki. It has been installed by a tech guy but now I, as a
programmer, have to set it up, get it functioning and get data into it.
That is my assignment at work.
(Suggestions to find another job will not work!!!)
I have gotten permissions set up so I can edit LocalSettings.php (and I
don't know php either).
I know nothing about Wiki except looking stuff up in Wikipedia!!!
Thanks
>Platonides wrote:
>
>Bill Egnatoff wrote:
> > After an upgrade (to 1.13.4), attempting to edit any page gives the
> > Database error
> >
> > A database query syntax error has occurred. This may indicate a bug
> > in the software. The last attempted database query was:
> > (SQL query hidden)
> > from within function "Article:getHiddenCategories". MySQL returned
> > error "1146: Table 'wiki_foci202.foci202page_props' doesn't exist
> (localhost)".
> >
> > Some pages will display, but attempting to display other pages gives
> > a similar error:
> >
> > A database query syntax error has occurred. This may indicate a bug
> > in the software. The last attempted database query was:
> > (SQL query hidden)
> > from within function "OutputPage::addCategoryLinks". MySQL returned
> > error "1146: Table 'wiki_foci202.foci202page_props' doesn't exist
> > (localhost)".
> >
> > Please suggest a reason and remedy.
> >
> > Thank you.
> >
> > Sincerely,
> >
> > Bill Egnatoff
>
>Did you run update.php ? Updating is a bit more than just overwriting
>the files.
I don't have full shell access so can't run the update script
directly. I used the alternative procedure of re-running the
installer. I have done this successfully on several upgrades with
several wikis. I don't know what I did differently in the case in
question. The display after running the installer indicated that the
installation was successful. The wiki is small (a couple dozen
pages), so if, alternatively, I could recover the content of the
pages, I could rebuild the wiki from scratch, but I'd like to know
what went wrong. I do have access to the database PHPMyAdmin.
We're a (small) software development shop that would like to use
MediaWiki as our main internal website.
We have both MediaWiki and non-MediaWiki documentation such as perl-pod
and javadoc stored in our version control system and a bugzilla
installation. What we'd like is to be able to enter "foo" in the
MediaWiki search field, and find MediaWiki pages with "foo" (like now),
but *also* find "foo" in e.g the javadoc, perldoc, source code and
present a potentially external link such as:
http://server/javadoc.cgi?src=SomeClass.java .
I've been searching for a solution looking all over for this, and I
can't believe we're the first people interested in this.
http://thread.gmane.org/gmane.org.wikimedia.mediawiki/14457 shows no
replies but is basically the same question.
I see three different approaches:
1) Pre-parse the perldoc, javadoc etc. and keep some internal MediaWiki
pages up-to-date with the parsed external sources. Then MediaWiki's
existing search will be able to index and find data in them. But the
syncing is messy and we don't need to edit java code from inside
MediaWiki anyway. Also, original formatting may get lost.
2) Modify MediaWiki's internal search e.g. like Extension:Lucene-search
and somehow squeeze in a link to
http://server/javadoc.cgi?src=SomeClass.java
3) Create a meta search thingy, so when searched for "foo", it calls the
unmodified MediaWiki search and presents *these* results, then presents
results for searching of javadoc etc.
At this point we don't care much about performance. The internal server
is basically unloaded and we expect 10 searches a day tops. But we
insist on the functionality. So e.g. "grep -r 'foo' java" is a viable
option for us to produce the java search results. So for the sake of
argument lets leave performance aside.
But how do we get these external search results integrated into our
MediaWiki "frontend"?
More detail on what we're trying to do here:
http://www.morch.com/2009/02/10/documentation-git-and-mediawiki/
Peter
--
Peter Valdemar Mørch
http://www.morch.com
I made a proposal for a project about geocoded audio files with dialect
words/fragments.
Here I put some links to the tools which I would like to combine:
http://www.creativetranslations.eu/DialectWiki
I'm a newbie and don't understand how to include templates or iframes for
maps or audio modules. The syntax is still a riddle to me although I checked
the help files about templates.
If you have any hints for me where to look, where to go and what to do would
be very appreciated.
Many thanks in advance
Achim
--
View this message in context: http://www.nabble.com/Including-audio-geo-templates-iFrames-API-tp21868688p…
Sent from the WikiMedia General mailing list archive at Nabble.com.
ACHTUNG: Diese Mailbox wird nicht persönlich gelesen und dient nur zur elektronischen automatischen Weiterverarbeitung. Sie werden auf diese E-Mail KEINE Antwort von uns erhalten.
Bitte antworten Sie NICHT auf diese E-Mailadresse. Unser Service-Team steht Ihnen über support(a)iserve4u.ch gerne zur Verfügung.
Ihr iserve4u-Team
Hi, I am confused as to choosing which options:
- InnoDB OR MyISAM
- MySQL 4.1/5.0 binary OR MySQL 4.1/5.0 UTF-8 OR MySQL 4.0
backwards-compatible UTF-8
I am hosting it in Hostgator, a public web installation. Mediawiki says in
the installation:
InnoDB is best for public web installations, since it has good concurrency
support. MyISAM may be faster in single-user installations. MyISAM databases
tend to get corrupted more often than InnoDB databases.
However, my previous webhost proposed MyISAM. Also Mediawiki says:
In *binary mode*, MediaWiki stores UTF-8 text to the database in binary
fields. This is more efficient than MySQL's UTF-8 mode, and allows you to
use the full range of Unicode characters. In *UTF-8 mode*, MySQL will know
what character set your data is in, and can present and convert it
appropriately, but it won't let you store characters above the Basic
Multilingual Plane<http://en.wikipedia.org/wiki/Mapping_of_Unicode_character_planes>.
but my previous webhost proposed MySQL 4.0 backwards-compatible UTF-8.
I plan to use InnoDB and MySQL 4.1/5.0 binary. Is this a wise decision?
Regards,
PM Poon
Hi, my box surrounding the categories at the bottom of each article page
miraculously disappeared! I have another wiki and I copied the Monobook.php
to it but the box still refuses to appear. I then tried to copy both my
Common.css and Monobook.css over and still nothing happens. Seems to work in
one website but not in the other. What else can I try? This is the trouble
of being half past six, doing by trial and error, LOL.
PM Poon
Hi,
is there a function/extension to have one page per topic?
1. blabla
1.1 more text
1.2 even more
2. New caption
2.1. much more text
I would like the user to be able to view e.g. 1. on one page and 2. on
another (without tearing apart the whole article).
Thanks, Helmut
--
No Swen today, my love has gone away
My mailbox stands for lorn, a symbol of the dawn
After an upgrade (to 1.13.4), attempting to edit any page gives the
Database error
A database query syntax error has occurred. This may indicate a bug
in the software. The last attempted database query was:
(SQL query hidden)
from within function "Article:getHiddenCategories". MySQL returned
error "1146: Table 'wiki_foci202.foci202page_props' doesn't exist (localhost)".
Some pages will display, but attempting to display other pages gives
a similar error:
A database query syntax error has occurred. This may indicate a bug
in the software. The last attempted database query was:
(SQL query hidden)
from within function "OutputPage::addCategoryLinks". MySQL returned
error "1146: Table 'wiki_foci202.foci202page_props' doesn't exist
(localhost)".
Please suggest a reason and remedy.
Thank you.
Sincerely,
Bill Egnatoff