$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
http://bugs.mysql.com/bug.php?id=1341
We're wondering if we should just convert everything to MyISAM. Any
thoughts?
=====================================
Jim Hu
Associate Professor
Dept. of Biochemistry and Biophysics
2128 TAMU
Texas A&M Univ.
College Station, TX 77843-2128
979-862-4054
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi all,
I've created some custom namespaced on one of my wikis, Botwiki
(previously known as pywikipedia).
I've put these lines in my LocalSettings.php file:
- ---
#Custom namespaces
$wgExtraNamespaces =
array(100 => "Manual",
101 => "Manual talk",
102 => "Python",
103 => "Python talk",
104 => "Php",
105 => "Php talk",
106 => "Perl",
107 => "Perl talk",
108 => "AWB",
109 => "AWB talk",
110 => "IRC",
111 => "IRC talk",
112 => "Other",
113 => "Other talk"
);
$wgContentNamespaces[] = 100;
$wgContentNamespaces[] = 102;
$wgContentNamespaces[] = 104;
$wgContentNamespaces[] = 106;
$wgContentNamespaces[] = 108;
$wgContentNamespaces[] = 110;
$wgContentNamespaces[] = 112;
- ---
However, I have a big problem: when I go to a page in one of these new
namespaces (not the discussion, the main ones), for example
http://botwiki.sno.cc/wiki/Perl:Copyright_Violation_Bot , I found the
red link to the discussion page. It's right, as there is no discussion
page for that article. But if you click on it, it brings you to
http://botwiki.sno.cc/w/index.php?title=Perl_talk:Copyright_Violation_Bot&a…
correct, of course. But have a look of the article and discussion tabs:
they are both red! The first, "article", leads to
http://botwiki.sno.cc/w/index.php?title=Perl_talk:Copyright_Violation_Bot&a…
when it should lead to
http://botwiki.sno.cc/wiki/Perl:Copyright_Violation_Bot and the second,
"discussion", leads to
http://botwiki.sno.cc/w/index.php?title=Talk:Perl_talk:Copyright_Violation_…
, when it should lead to
http://botwiki.sno.cc/w/index.php?title=Perl_talk:Copyright_Violation_Bot&a…
.
It's the first time I deal with custom namespaces :-( but I have some
ideas of what it can be. Can the problem be with the
$wgContentNamespaces settings? So it detects everything as ns0? (don't
think so).
Or can it be the fact that I haven't used an underscore in the
$wgExtraNamespaces definition?
Snowolf
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGWhk7sdafW5NQMtERAuX+AKDQ7QLNjXv9cu+ZbSLXidMzgi/vNgCaA7VT
+VTgR3iI/BI7FVDqcyRZVJ0=
=a4yP
-----END PGP SIGNATURE-----
I want to moving all pages in a certain namespace (about 60 pages) into
the the "main" namespace. I couldn't find how to do this, so I tried
exporting the pages and importing them and I ran into all sorts of
problems. Is there a way to do what I want without using the import and
export features (and without having to move each of them manually)?
Thanks.
Hello everybody,
When I search after some terms, which have not been defined yet, or after editing an entry (but not always???), I get the following error message:
Database error
>From MiWiki
For query "sales"
Jump to: navigation, search
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 "". MySQL returned error "1030: Got error 127 from storage engine (localhost)".
Has anybody had this error before? How may I fix it?
Thanks a lot in advance for your help and best regards,
Veronica
P.S: I found a similar message at the The Wikitech-l Archives, but in my case no table name was written, so what shall I do????
--
Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer
Morning!
I am building a web site for a family member who is in the process
of completing a PhD and MediaWiki looks like the ideal CMS to use
as they will be able to update their own web site (delegation is
always important :-)
Two questions:
1) There may be a need to have certain pages in multiple languages.
Is the best way to do this for a small site is to add a language
identifier to the page title eg:
here is the CV in [[CV.en|English]] or in [[CV.nl|Dutch]].
Is there a way to do this and still have a more readable title eg
"English CV" rathern than "CV.en"?
2) I see from the LocalSettings.php that it is possible to prevent
access to certain pages for users who are not logged in. Do I
need to list all the pages I want blocked or is it possible
to do wildcards eg internal*
TIA
James
On Mar 21, 2007, at 10:10 AM, Caitlin Dempsey wrote:
> I've been trying to find a way to create a Google friendly sitemap
> for my wiki. The few solutions I have found that are specific to
> Wikimedia haven't worked on my wiki.
I found this page which has an extension that worked on my wiki:
http://www.mediawiki.org/wiki/Extension:Google_Sitemap
The advice in the subject line is correct. Users should never be
deleted from the table for another reason; you leave a lot of messy
references to them lurking about which really does confuse the hell
out of the software.
MediaWiki does not support the deletion of users, and likely never will.
Rob Church
The topic of corporate intranet wikis seems to come up a lot.
Does anyone know of a wiki about corporate intranet wikis? Both
technical and social aspects.
Of course, Googling "corporate wiki" produces commercial wiki engine
sites and occasional news and blog posts ...
- d.
Does anyone know of a MediaWiki extension to provide revision control
for uploaded images, say, via subversion?
On first thought it seems easy -- just let the /images folder be a
subversion working copy, and run hooks to do "svn add/commit" on upload
or "svn delete/commit" on deletion, providing the user comment as an svn
comment. Maybe the hardest parts would be:
* The necessary "svn add" operations when new subfolders get
created in /images.
* Adding this extension to an existing wiki that hasn't been
running it before (i.e., only some historical images will be in
subversion)
* Doing a "history" command on an image file, as opposed to the
article in the Image: namespace... UI considerations....
A very simple, though incomplete, implementation, would be to run an svn
commit (and associated adds & deletes) every N minutes on /images. That
might yield 80% of the benefits without writing an extension.
Thoughts?
DanB