Hi and Hello,
may I again ask about this Wingdings.ttf font style. I know that it is
possible to install additional fonts into mediawiki.
So my question is if it isnt also possible for Wingdings.
Itried to alter the WebFonts extension but it seems not to have an effect.
Some Helps and Tipps are highly appreciated.
I am new in this list. I am learning how to install and use a wiki, but I
have this error:
Error al enviar correo: Failed to connect to mailserver at "localhost" port
25, verify your "SMTP" and "smtp_port" setting in php.ini or use ini_set()
I made the changes in php ini as you can see:
; For Win32 only.
SMTP = localhost
smtp_port = 25
but still don't work. I have deactivated the window's firewall but still
What is the problem?
Thank you very much in advance
As a newbie in Gerrit, but developer in wmflabs,
I'm Rical and would change my email but I can't.
in Gerrit > Settings > Contact Information,
I try for 10 days to add an email.
When I clic register in the pop dialog "Register Email Address", I see an error :
Application Error, Server Error, Cannot format velocity template com/google/gerrit/server/mail/RegisterNewEmail.vm
Thanks to help me.
I'm trying to configure madiawiki 1.18.1 for xls upload.
The OS is CentOS 6.2.
I've set wgFileExtension in LocalSettings.php according to manual.
- It's working on a VM I'm hosting on my computer
- It's not working on the provider's hosting solution (1).
I have a MIME detection error while uploading an xls file.
The returned error is :
File extension ".xls" does not match the detected MIME type of the
I've red the differents mediawiki manual pages and FAQ but I don't
unterstand what happens...
Any idea ?
Thank sin advance.
(1) - I only access to the hosted system via ftp so I don't have access to
the system config.
You should consider using the UrlGetParameters extension:
This way, you can have a single wiki page serving as the "wizard" - it
can keep linking to itself, changing the query string every time (the
#fullurl function might be useful there), and then use #if from
ParserFunctions, and #urlget from UrlGetParameters, to set the right
display based on the query string.
WikiWorks · MediaWiki Consulting · http://wikiworks.com
since some days my mediwiki refuses changes:
------------- cite on ----------------
Es ist ein Datenbankfehler aufgetreten. Der Grund kann ein
Programmierfehler sein. Die letzte Datenbankabfrage lautete:
aus der Funktion "CheckUserHooks::updateCheckUserData". Die Datenbank meldete den Fehler "1146: Table 'dbxyz.cu_changes' doesn't exist (dbxy.example.com)".
------------- cite off ----------------
Last successful changes: may 26 and may 15
Should I look into the backups?
I'm running a wiki with MediaWiki 1.20 and both the ToggleDisplay and
MobileFrontend extensions. The ToggleDisplay extension is no longer
supported for MediaWiki 1.20, but it works fine in general for ordinary
desktop viewing (thanks to a fix from Platonides in an earlier mail on this
list). MobileFrontend is a new extension available only from MediaWiki 1.20
onward that allows for mobile-style page displays.
The problem is that the ToggleDisplay extension does not work properly with
the default mobile view provided by MobileFrontend. The links that need to
be clicked to toggle displays simply don't work. For instance, here:
clicking the "SHOW MORE" has no effect. On the other hand, in the desktop
version, it expands just fine:
I'm guessing the problem is because of inteference from the mobile
frontend's own toggle displays of collapsible sections. Is there an easy
tweak to ToggleDisplay that would fix this problem? The problem is not very
pressing, but I'd like to fix it if possible. Any suggestion would be
So I moved a wiki by copying the whole wiki directory and backing up the
database and re-importing the database on to a new server. Everything
is good except the images. Images are not rendering. So I looked in my
error logs and found this:
/var/www/html/mediawiki/images/.htaccess: RewriteEngine not allowed here
I renamed this .htaccess file to something else and the images are now
rendering. But I'm just curious why I had to do this. The .htaccess
file is on the original server - again, I copied the whole wiki
directory so everything is the same from wiki 1 to wiki 2. just trying
to understand more. (http web server has the same config also).
I am trying to design a better method for new users to get information
about getting started with a few libraries I work with. I'm leaning
towards asking them a series of questions, providing the appropriate
information based on their answers. That is, rather than simply having
a huge page with a table of contents something like:
A) Downloading the code
(which quickly gets unwieldy and overwhelming), I was thinking of
doing something more like:
Where the user actually follows some "path" to get started by
answering questions like:
"Which operating system are you using? Windows or Linux"
"Are you familiar with git? no yes"
to bring them directly to the information they need.
As you can see from those mock ups, doing this with normal text and
links is quite "ugly". Has anyone seen a pattern/plugin/etc for
MediaWiki that can accomplish something like this while being
"prettier"? I'd hate to have to reinvent the wheel, or do something
very manual when a better solution already exists.
In the past couple of weeks I've been talking with Sam Reed (WMF's
current MediaWiki release manager) and Rob Laphiner (WMF's Platform
Engineering Director) about the future of MediaWiki tarballs.
I began this discussion after Rob expressed regret about the WMF's
ability to give tarball distribution the attention it deserves. Since
the WMF is focused on maintaining Wikipedia and its sister projects,
tarball distribution often loses among competing priorities.
The Foundation has made MediaWiki available for everyone and that's a
great thing. But Wikimedia's funding comes from donations as a result
of requests on Wikipedia, not from distribution of MediaWiki, so they
are rightly focused on their production cluster.
Other users of the MediaWiki software have different needs. For
instance, Citizendium, and Wikia and have both pegged their MediaWiki
installations at 1.16.5 for stability and made their own modifications
-- essentially forking the code. Forking is not ideal, but it is
understandable because there is no cooperation around individual
MediaWiki releases over the long term. With a third party to manage
MediaWiki releases and maintain long term support for selected releases,
cooperation between non-WMF users would be smoother.
To this start effort, I welcome interested collaborators from the
community of MediaWiki users outside of the WMF. With your help, we
will start making and maintaining MediaWiki releases based on the core
MediaWiki code without forking development.
I've been discussing this with some MediaWiki sites as well as setting
up a separate mailing list for packagers (such as Debian and RedHat
distributors) and discussing it there. So far the response has been
So now I'm asking you guys. Any interest?
Find peace within yourself and there will be peace on heaven and
earth. -- Abba Isaac