$wgDBtransactions gets set to true if using InnoDB tables. Is there
an advantage to using InnoDB tables?
The disadvantage is that with MySQL there is a file, ibdata1, that
seems to grow endlessly if InnoDB tables are used. See
We're wondering if we should just convert everything to MyISAM. Any
Dept. of Biochemistry and Biophysics
Texas A&M Univ.
College Station, TX 77843-2128
Thanks for the answer.
I just tested, and it only works if I disable the Extension:UsabilityInitiative in $IP/LocalSettings.php
Do you know something about this bug and how to fix it?
I am using Lucene-Search 2.1/MWSearch for my MediaWiki 1.15.1.
It's working fine, but it can't search any Japanese characters.
I have tried (language,ja) in the lsearch-global.conf file, but it doesn't seem to make any difference.
Any idea would be appreciated,
Looking for the perfect gift? Give the gift of Flickr!
I'm working with the new editor from Usability extension. Tough I miss
some extra buttons that insert some code snippets that I'd like to
include. How can I do this?
Is there any documentation about this?
Thank you in advance.
until I made an upgrade from 1.15.1 (applied the 15.2,3 and 4 patches) I
was happily editing my wiki pages with gnu emacs via ee.pl
and a bookmarklet that goes:
Now, external editing is broken I and I suspect that this is related to
Fixed login CSRF vulnerability. Logins now require a token to be
submitted along with the user name and password. Patch by Roan Kattouw.
Any ideas on what I could/should do to get TRUE external editing back ?
I don't mind installing stuff. I am not much of a programmer/sysadmin,
but I can read :)
I don't want to use something like "It's all text" since it's not
practical to edit several wiki pages at the same time and having
to keep several browser tabs open just for saving. (I do this at home
on a windows box and it's a pain).
- thanx for any help / insight ! - Daniel
PS: Of course I am not sure about the cause, but in my case
identification of the problem (upgrading) is really simple. I got two
wikis on the same machine:
The 1.15.4 one (http://edutechwiki.unige.ch/en/) is broken and the
1.15.1 one (http://edutechwiki.unige.ch/fr/) works just fine.
I have tried the methods given in the MediaWiki manuals that are online to do simple, basic editing of the Navigation Panel, only to find it impossible to change anything I try to change. Simple procedures such as changing the titles of the navigation links, which I know is possible because I see the titles changes on other MediaWikis, Wikipedia for example. The same with adding or deleting a link in the Navigation Panel. Nothing seems to work, I just understand it.
Is there an actual manual online that helps an administrator do such simple changes ? I just don't understand why MediaWiki makes things so difficult when they should be pretty straight forward & simple.
Thanks in advance.
at the moment, the search function in my installed mwiki only considered
search requests, if the string have 5 or more characters.
How can I change this to 3 characters?
|Michael Renner E-mail: michael.renner(a)gmx.de |
|D-81541 Munich Germany ICQ: #112280325 |
|Germany Don't drink as root! ESC:wq
a new minor update of Semantic MediaWiki, SMW 1.5.2, is now available
for download . The main user-visible change are some very nice
auto-completion features for Special:Ask . Credit for this goes to
Sanyam Goyal who made this happen as part of his recently completed
Google Summer of Code project (and to Yaron Koren who coordinated this).
As a side effect, SMW now also includes a copy of the relevant
MediaWiki's own copy of the same library is more widespread.
Besides these main changes, a number of smaller bug fixes and
improvements found their way into this version.
Special thanks go to Jeroen De Dauw for taking the lead in preparing
I have two image pages (File:filename1.png, File:filename2.jpg) that, when
opened, show a blank empty page on the server.
It seems to happen when someone uploads images with big resolution (the
images are there correctly uploaded, but their "File:" wiki pages are
On local development server, I can replicate the error, and I can read a
debug message instead of an empty blank page:
"Fatal error: Allowed memory size of 52428800 bytes exhausted (tried to
allocate 12417800 bytes) in path\to\includes\media\Bitmap.php on line 212"
I've tried to raise "memory_limit" to 512MB in php.ini and with ini_set in
LocalSettings.php, but no luck - same error.
Now, I would like at least to be able to delete those two "broken" image
pages, i.e. I don't want them in the wiki.
Any suggestions on how to do it, eventually also acting directly on the
Besides, how to avoid that happening again?