I just wanted to ask if there is some way to include a PRINT button (with
function) on each page. For now I was just able to use it per Javascript on
each page individually., yet I really would like to know if I could somehow
include this button into the template, so that IŽ(and others) donŽt need to
add it manually each time a page is created. (IŽm using Monobook on
MediaWiki 1.4)
I donŽt know nothing about computers, nor less php or Java...
maybe it might just be possible somwhere where the login/logout.. links are
located...but I really donŽt know..
But I really would appreciate your help.
Thank you everyone.
Add me to the list of folks pulling their hair out trying to get
prettier urls to work with mediawiki.
After upgrading to 1.4.0 I decided to try to prettify my urls. I
hadn't tried actually rewriting the incoming urls using mod_rewrite
under my previous 1.3.x installation, but I swear that manually
entering a url of .../wiki/index.php/Title used to work.
I've set up rewrite rules for the wiki directory, and It looks like
the rewriting of a url like
http://www.mydomainname/wiki/Frodo
to
http://www.mydomainname/wiki/index.php/Frodo
is working but then the url itself isn't being properly processed. As
I say, before I upgraded to 1.4.0 manual use of the resulting url used
to work.
Yesterday, I couldn't get the alternative of rewriting to
http://www.mydomainname/wiki/index.php?Frodo
to work either, but today, for some mysterious reason it seems to work.
I hate it when things don't work and I don't understand why, but I
hate it even more when they start to work and I still don't understand
why, since it's not good for the confidence in things not breaking in
the future.
Anyway, any ideas why the index.php/articlename form used to work in
1.3 and doesn't in 1.4?
Problems: The frequently-changing database schema in which the wiki
information is stored makes it difficult to maintain data across
upgrades (requiring conversion scripts), offers no easy backup
functionality, makes it difficult to access the data with other tools,
and is generally fragile.
Proposed solution: Let's create a standardized file format (probably
something XML-ish) for storing the information contained in a wiki.
All the text, revisions, meta-data, and so on would be stored in a
well-defined format, so that, for example, upgrading the wiki software
(from any version to any other--no need to do one at a time!) could
be done by exporting the wiki into this format and then importing it
into the new installation. The export format would be publishable
and easier to use for other applications, would be a simple file
system for which commonly-available backup tools could be used. A
periodic export/import would serve to clean the database of any
reference errors and fragmentation. Tools could be created to work
with the new format to create subsets, mirrors, and so on.
I already have some idea of what is needed, but I solicit input.
--
Lee Daniel Crocker <lee(a)piclab.com> <http://www.piclab.com/lee/>
<http://creativecommons.org/licenses/publicdomain/>
Folks, Is there a way, either native or via some extension, that I can configure my wiki such that: Most pages are publicly (anonymously) viewable but not editable, and only hold back pages from public view that I want to block? Right now, as best I can see, I would need to manually update LocalSettings.php, the array that lists which whitelist pages are viewable, and that those pages must be explicitly enumerated, making it rather impractical once a wiki gets past a certain number of pages. In my case, I believe it will be easier to cordon off items I would not want publicly available, but only visible to my developers. So is there an opposite of this function available? I would of course prefer to be able to do something natively within MW, but if that's not possible, and if anyone knows of an extension that might do the trick, I'd appreciate it. Thanks. Ed Greaves
_______________________________________________
Join Excite! - http://www.excite.com
The most personalized portal on the Web!
Hello,
I'm new to MediaWiki. I'd like users to be able to Import/export
Word/.pdf/.xml files to/from MediaWiki pages. Is this feasible?
If not MediaWiki, would other Wikis be able to do this?
=========
More details:
=========
I'm leading a small software-development team as part of a private,
startup-business effort. I am attracted to Wiki mechanisms for their
apparent collaborative-documentation capability. I want to load a Wiki on
my private, collaboration-development server (I have many other server apps
already like phpBB, Subversion/CVS, Apache, etc).
Imports
----------
In order to make new-user adoption and general use much easier, it would be
fantastic if authors can write in a known, understood format (namely
Microsoft Word) and then import the created file into the Wiki page.
The following thread suggests that this import capability is not yet available:
http://mail.wikipedia.org/pipermail/mediawiki-l/2005-March/003978.html
Am I reading things correctly?
Here's a tool that may or may not help:
These (google cached) links point towards a small tool to convert Word to a
MediaWiki format:
http://64.233.167.104/search?q=cache:4F7DBOsC9LQJ:infpro.com/projekte/wordw…http://64.233.167.104/search?q=cache:g1yitISrOTMJ:infpro.com/projekte/wordw…
I've also attached the tool and description in a .zip file attached to this
email...but I'm not sure if MediaWiki-l supports file attachments. I have
tried neither this tool nor MediaWiki...so take this for what it's worth.
Exports
---------
As for the exports, the above email thread suggests that this capability
(I'm presuming output to all of Word, .pdf, and .xml?) is mature? Exports
are important for document-snapshot archiving and for content distribution
to readers (like an external review board, our target customers, etc) who
do not have access to my collaboration site.
I'd to confirm all these things before I go through and install the software.
-Matt
ps:
The page:
http://en.wikipedia.org/wiki/Wiki_software
When choosing a wiki engine, criteria to consider might include:
"Be able to import external files (HTML, Word document), export to external
files (Word document, PDF)"
I was hoping that MediaWiki could do all of this, particularly it light of
its glowing review at:
http://www.onlamp.com/pub/a/onlamp/2004/11/04/which_wiki.html
-Matt
Hello,
how to edit the search result page into the same one like the org.
wiki search result page
(http://en.wikipedia.org/wiki/Special:Search?search=search&go=Go)
with google search and especially create an article with this title or ..... ?
thank you,
happy eastern,
adam
Hi,
I want to add extra functionality to the standard editpage, namely
a popup Google search function for lyrics. In 1.3.10 I did this by
adding extra <input> tags and javascript to one of the system messages,
but this doesn't work in the new 1.4.0 (and rightfully so!).
How do I go about adding a textbox, a button and some popup
javascript to every editpage?
Thanks!
Greetings,
Patrick
--
_______________________________________________________________
Patrick Atoon ___________________ mailto:patricka@rapdict.org
_____________________________________ http://www.rapdict.org/
Brion,
I get the impression that this page is only available for "new-school" skins
(i.e. those that use PHPTal). Anyway, I bit the bullet and downgraded to
PHP4, so now we can use the Monobook skin.
Thanks for your help,
Matt
> -----Original Message-----
> From: mediawiki-l-bounces(a)Wikimedia.org [mailto:mediawiki-l-
> bounces(a)Wikimedia.org] On Behalf Of Brion Vibber
> Sent: Saturday, March 26, 2005 4:00 AM
> To: MediaWiki announcements and site admin list
> Subject: Re: [Mediawiki-l] Sitewide css
>
> Matthew Gertner wrote:
> > Thanks for your response. I do seem to have a page called
> > MediaWiki:Monobook.css, but I'm not using the monobook skin. When I
> tried
> > the names of other skins (e.g. Nostalgia.css) no page was found (we're
> > using the standard skin). Is this something specific to monobook? How do
> I
> > create a page for a different skin?
>
> [[MediaWiki:<skinname>.css]]
>
> It's possible that Nostalgia doesn't include one. Check the source.
>
> > Isn't there a way to add styles that
> > apply to *all* skins without changing the common.css file directly? What
> > am I missing?
>
> No, you'd have to change the centrally-included CSS files.
>
> -- brion vibber (brion @ pobox.com)
I noticed that the 'othercontribs' info isn't showing up in v1.4.0. In
v1.3.11, setting,
$wgMaxCredits = 2;
$wgShowCreditsIfMax = false;
in LocalSettings.php would produce a message like,
"This page was last modified <time>, <date> by <site> user
<user_name>. Based on work by others."
where 'others' is a link to the Credits page for that page. And, all of
the contributors would be listed on the Credits page.
In v1.4.0, the "Based on work by others." text doesn't show up, nor
does the Credits page list any contributors other than the last. I've
also tried other settings for $wgMaxCredits, like -1, but none of these
seem to cause any variation in behavior.
Is this a known issue? If so, is there a known fix or workaround to get
this working again?
John Blumel
Hello,
the last section on http://meta.wikimedia.org/wiki/Help:EasyTimeline_syntax
is : EasyTimeline code with a template parameter is not allowed
so we can't do something like {{etl | a }} and {{etl | b }}
to make multiple timeline and only one sabloon to change the look of all the
timelines.
also
{{ etl_begin }}
bar:firstbar
from:15 till:80
bar:secondbar
from:20 till:50
{{ etl_end }}
do not the job because if you put in
the etl_begin sjabloon <timeline>
and </timeline> in the etl_end sjabloon
the editor put a </timeline> in the etl_begin session at saving time so making
errors for the timeline generations
how to fix or work around this problem so it is for the enduser simple to make
timelines and for me simple to change te look of all the timelines at ones ?
kris Coryn