hello everyone,
i'm a new and slightly confused mediawiki user who'd like to put external links on my sidebar that open in new window. is this something that can be done?
thanks!
Hello
how to backup of mediawiki with oracle. i mean which we upload any image it
will create the folder temp in client side.now assume if we published on a
server how that thing import in that server.
thanks
RS
Running MediaWiki 1.16 on a RHEL5.x server (PHP 5.1.x.) and am trying
to find the "best" way to handle .docx and other compressed file
formats.
I can of course use $wgVerifyMimeType = false, but I'd rather find a
way to handle this differently.
Is this something that might be handled better if I updated to PHP 5.3
(RHEL5 provides a supported version)? If it relies on the MIME magic
files from the "file" utility still, I'm guessing it still won't
work...
Debug logs show the following:
MimeMagic::__construct: loading mime types from /srv/syswiki.esri.com/wiki/includes/mime.types
MimeMagic::__construct: loading mime info from /srv/syswiki.esri.com/wiki/includes/mime.info
MimeMagic::doGuessMimeType: ZIP header present at end of /tmp/phpESAce0
MimeMagic::detectZipType: /^mimetype(application\/vnd\.oasis\.opendocument\.(?:chart-template|chart|formula-template|formula|graphics-template|graphics|image-template|image|presentation-template|presentation|spreadsheet-template|spreadsheet|text-template|text-master|text-web|text))/
MimeMagic::detectZipType: unable to identify type of ZIP archive
MimeMagic::guessMimeType: final mime type of /tmp/phpESAce0: application/zip
MediaHandler::getHandler: no handler found for application/zip.
File::getPropsFromPath: /tmp/phpESAce0 loaded, 177153 bytes, application/zip.
MacBinary::loadHeader: header bytes 0 and 74 not null
MimeMagic::doGuessMimeType: ZIP header present at end of /tmp/phpESAce0
MimeMagic::detectZipType: /^mimetype(application\/vnd\.oasis\.opendocument\.(?:chart-template|chart|formula-template|formula|graphics-template|graphics|image-template|image|presentation-template|presentation|spreadsheet-template|spreadsheet|text-template|text-master|text-web|text))/
MimeMagic::detectZipType: unable to identify type of ZIP archive
MimeMagic::guessMimeType: final mime type of /tmp/phpESAce0: application/zip
It's somewhat odd that FileInfo isn't being used (I have the extension
installed, showing up in phpInfo() and also $wgLoadFileinfoExtension =
true is set).
Any thoughts or ideas would be appreciated.
Thanks,
Ray
Hello All,
I have designed a personal website using Mediawiki 1.17. It's very easy
to create a platform like Wikipedia using mediawiki, but one problem is
SKIN of Mediawiki. It's not as attractive as other wiki themes are. I
have google'd for best skins/Themes for mediawiki, and found some themes
but not satisfied with the end results.
Can anyone suggest some good free/premium skins available?
If not using tailor-made skin, another option left with me is create my
own skin from scratch or extend some basic skin(i.e. MonoBook/Vector).
So in this context How should I proceed? Actually, I have not good
experience with CSS Design and etc.
Thanks,
Manish SP
Manish.patil(a)atosorigin.com
Hi,
I just upgraded a wiki from 1.10 to 1.16.5. I was previously running
the news extension and downloaded a version of the news extension for
the 1.16 release.
The following appears in my main page (along with other content):
<news limit="20" nominor unique>
* [[{{{pagename}}}]] ([[User:{{{user}}}]], {{{timeanddate}}})
</news>
Under the old 1.10 release, it would display recent changes to the
wiki. Under the 1.16.5 release, I make updates to the wiki, yet the
news extension displays nothing. When I go to the recent changes page,
it displays the changes. Any ideas how to get this working?
Note, I downloaded this extension from
http://mediawiki.org/wiki/Extension:News There appears to be several
similarly named extensions, but this is the one that was previously
working for me. The other ones didn't seem to do quite what I wanted.
Thank You,
Nataraj
You can wrap things in <div class=noprint>...</div>, or define some custom
classes in your MediaWiki:Print.css page and use those.
http://www.mediawiki.org/wiki/Manual:CSS
-- brion
On Jun 21, 2011 7:30 AM, "van Vliet, M.W." <M.W.vanVliet(a)olvg.nl> wrote:
Dear Heroes of Wiki,
How can I specify parts of a page to be printed? Ideally I would use
<noprint> </noprint> tags or something likewise to sepcify parts I don't
want printed. Is there a way to accomplish this within Wiki?
Thanks in advance
Marcel van Vliet
Disclaimer:
Dit e-mail bericht is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan en gebruik door anderen dan geadresseerden is niet toegestaan. Indien u niet de geadresseerde bent, wordt u verzocht de verzender hiervan op de hoogte te stellen en het bericht te verwijderen.
In verband met electronische verzending kunnen aan dit e-mail bericht geen rechten worden ontleend.
Hi, all!
We recently implemented the LDAP authentication extension: http://www.mediawiki.org/wiki/Extension:LDAP_Authentication
It's working very well, but we now have a couple of folks who work on our campus, but who are not in our group in Active Directory-in fact, two of them are with other schools that share the campus-who would like access to the wiki. Is there a way to mix authentication? We can always make these people sponsored users so that they are added to our group, but I'd prefer a mixed authentication approach.
Thanks in advance!
Nina
Nina McHale, MA/MSLS
Assistant Professor, Web Librarian
University of Colorado Denver, Auraria Library
Facebook & Twitter: ninermac
http://milehighbrarian.net
Im working on the phpbb Single-Signon extension and I wanted to amke it so that users who are moderators are automatically made sysops on the wiki.
Other than modifying the database, is there any way in code to make a user a sysop (without having it done by a bureaucrat)?
Hi!
I am interested in deploying MediaWiki in our environment, with a
preconfigured LocalSettings.php. Is there a way to initialise the database
tables while already having LocalSettings.php?
ie; I want to deploy a wiki preconfigured for our environment, with defaults
appropriate for our environment, yet only initialise the database on
deployment of the wiki into production.
In this way, several places could deploy the same pre-initialised
configuration, to their own local databases - or make minor changes to the
config (such as db prefix, credentials), and set up their own instance of
the wiki, retaining all other custom default settings.
Thanks.
--
Trevor Phillips - T.Phillips(a)murdoch.edu.au
Senior Software Developer, Business Application Services
Information Technology Services, Murdoch University
CRICOS Provider Code 00125J