$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.
Hey, all,
Some of my colleagues are objecting to my desire to minimize uploading of Word documents to our new intranet wiki. My main objection to it is that we ought to be entering information into wiki pages so that we can take full advantage of document versioning, talk pages, watching, etc.-y'know, the stuff that makes it a wiki...
I've been called "silly" and "arbitrary" regarding this. :) I'm not outright forbidding posting Word documents; I'm just trying to get people to use the wiki the way it's mean to be used. Am I being unreasonable? I even stated that it's acceptable to load the final version of a 20-page report, or a form that's meant to be printed out and filled out by hand-i.e., things in a final state that do not need further editing.
Has anyone else encountered this resistance? I was most surprised that it came from someone who uses/edits Wikipedia, which, as far as I can tell, does not support uploading of Word docs.
Nina
Nina McHale, MA/MSLS
Assistant Professor, Web Librarian
Auraria Library
http://library.auraria.edu/~nmchale/
Facebook<http://www.facebook.com/profile.php?id=672599042> | MySpace<http://www.myspace.com/ninermac>
Serving the University of Colorado Denver,
Metropolitan State College of Denver,
and the Community College of Denver
1100 Lawrence Street
Denver, CO 80204
303-556-4729
Hey, all,
Thanks for your quick and fantastic responses! I am loving this list. :)
I take the excellent point about looking at whether this is the right tool for the job. However, the decision to use a wiki comes out of two consultant recommendations to use a wiki and reactions to a failed Sharepoint intranet installation (dating to around 2000) that people hated because it required use of proprietary software, in that case, Microsoft FrontPage. Moreover, the specific decision to use MediaWiki was vetted through all of the proper channels, and no one raised any objections.
Thanks again, everyone!
Nina
Nina McHale, MA/MSLS
Assistant Professor, Web Librarian
Auraria Library
http://library.auraria.edu/~nmchale/
Facebook<http://www.facebook.com/profile.php?id=672599042>
Twitter: ninermac
Serving the University of Colorado Denver,
Metropolitan State College of Denver,
and the Community College of Denver
1100 Lawrence Street
Denver, CO 80204
303-556-4729
I originally posted the following on www.mwusers.com and couldn't get a
solution. Can I please get some assistance?
-------
I am trying to embed the following into a mediawiki page, and it works in
the preview but not when saved. It keeps saying "Screen Creation Failed.
File May Be Corrupted." The RawHTML setting is properly set to 'true' in
LocalSettings.php. Obviously the filename and location are okay if mediawiki
can render it in preview, but something is off if it can't do it after
clicking Save Page. This, btw, is an embedded object using Right Hemisphere
Deep View (3D image viewer), which is properly installed on my computer. Any
ideas?
<HTML>
<HEAD>
<TITLE></TITLE>
</HEAD>
<BODY bgcolor="#FFFFFF">
<H2 align="center"></H2>
<P align="center">
<OBJECT ID="Right Hemisphere_obj"
TYPE="application/x-oleobject"
CLASSID="CLSID:1110E0D7-D33E-438C-88A4-1FA6A88F9A6B"
CODEBASE="
http://www.deep3d.com/downloads/products/deepview/install/deep.cab#version=…
"
width="100%"
height="100%">
<PARAM NAME="FileName" VALUE="images/b/b2/XYZ.rh">
<PARAM NAME="LicFile" VALUE="/license.rhl">
<PARAM NAME="RenderMode" VALUE="8">
<PARAM NAME="AnimationMode" Value="2">
<PARAM NAME="ShowTextures" VALUE="1">
<PARAM NAME="RenderAPI" VALUE="1">
<PARAM NAME="SelectedMode" VALUE="2441">
<PARAM NAME="ShowGUIShowToolbar" VALUE="0">
<PARAM NAME="ShowHiddenGeometry" VALUE="0">
<embed src="images/b/b2/XYZ.rh" quality=high pluginspage="
http://www.deep3d.com/downloads/products/deepview/install/deep.cab#version=…"
type="application/x-oleobject" height="100%" width="100%"></embed>
</OBJECT>
</P>
</BODY>
</HTML>
Como faço para criá-las?
Achei que bastava usar:
[[:Categorias:Nome_da_categoria]] mas não funcionou.
dipi evil danger
"Gott weiß ich will kein Engel sein"
http://meadiciona.com/dipi
DIPI EVIL PRODUÇÕES
http://productions.dipi.eti.br/
I am running mediawiki 1.14.0 on CentOS 5 apache 2.2.3
I use to have my documentroot set to /var/ww/site
but changed it to
/var/www/differentsite
Mediawiki is looking for images in /var/www/site/images instead of looking at the /var/www/differentsite/images
New uploads work as expected, but all of the old images are broken since the documentroot change.
Is there some type of data in the DB that holds this information? Because I need to fix this, but I am definitely not a DB so I do not know how to do that.
But if I can get information on where in the DB the upload location is stored I can likely modify the entries there...
Can anyone help me with this?
Thanks
Welcome to mediawiki-l. This mailing list exists for discussion and questions
about the MediaWiki software[0]. Important MediaWiki-related announcements
(such as new versions) are also posted to this list.
Other resources.
If you only wish to receive announcements, you should subscribe to
mediawiki-announce[1] instead.
MediaWiki development discussion, and all Wikimedia technical questions, should
be directed to the wikitech-l[2] mailing list.
Several other MediaWiki-related lists exist:
- mediawiki-api[5] for API discussions,
- mediawiki-enterprise[6] for discussion of MediaWiki in the enterprise,
- mediawiki-cvs[7] for notification of commits to the Subversion repository,
- mediawiki-i18n[8] for discussion of MediaWiki internationalisation support,
- wikibugs-l[9] for notification of changes to the bug tracker.
List administrivia (unsubscribing, list archives).
To unsubscribe from this mailing list, visit [12]. Archives of previous postings
can be found at [3].
This list is also gatewayed to the Gmane NNTP server[4], which you can use to
read and post to the list.
Posting to the list.
Before posting to this list, please read the MediaWiki FAQ[10]. Many common
questions are answered here. You may also search the list archives to see if
your question has been asked before.
Please try to ask your question in a way that enables people to answer you.
Provide all relevant details, explain your problem clearly, etc. You may
wish to read [13], which explains how to ask questions well.
To post to the list, send mail to <mediawiki-l(a)lists.wikimedia.org>. This is a
public list, so you should not include confidential information in mails you
send.
When replying to an existing thread, use the "Reply" or "Followup" feature of
your mail client, so that clients that understand threading can sort your
message properly. When quoting other messages, please use the "inline" quoting
style[11], for clarity.
When creating a new thread, do not reply to an existing message and change the
subject. This will confuse peoples' mail readers, and will result in fewer
people reading your mail. Instead, compose a new message for your post.
Messages posted to the list have the "Reply-To" header set to the mailing list,
which means that by default, replies will go to the entire list. If you are
posting a reply which is only interesting to the original poster, and not the
list in general, you should change the reply to only go to that person. This
avoids cluttering the list with irrelevant traffic.
About this message.
This message is posted to the list once per week by <river(a)wikimedia.org>.
Please contact me if you have any questions or concerns about this mailing.
References.
[0] http://www.mediawiki.org/
[1] http://lists.wikimedia.org/mailman/listinfo/mediawiki-announce
[2] http://lists.wikimedia.org/mailman/listinfo/wikitech-l
[3] http://lists.wikimedia.org/pipermail/mediawiki-l/
[4] http://dir.gmane.org/gmane.org.wikimedia.mediawiki
[5] http://lists.wikimedia.org/mailman/listinfo/mediawiki-api
[6] http://lists.wikimedia.org/mailman/listinfo/mediawiki-enterprise
[7] http://lists.wikimedia.org/mailman/listinfo/mediawiki-cvs
[8] http://lists.wikimedia.org/mailman/listinfo/mediawiki-i18n
[9] http://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[10] http://www.mediawiki.org/wiki/FAQ
[11] http://en.wikipedia.org/wiki/Posting_style#Inline_replying
[12] http://lists.wikimedia.org/mailman/listinfo/mediawiki-l
[13] http://www.catb.org/~esr/faqs/smart-questions.html