$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-----
Hi,
I have been trying to create a maintainable way of grouping pages
together and allowing readers to page through them in sequence. Most
samples I've seen use templates that require you to supply the
'previous' and 'next' page. This however results in three page edits
to insert a new page between two existing pages and does not guarantee
that your prev-sequence is identical to the next-sequence...
Being a programmer, that is way too much duplicate and error-prone
work for me ;-) There must be a better way to do this and I was hoping
to solve it with a plain MW installation (with ParserFunctions and
DynamicPageList at the moment).
Given an 'index' page that holds a list of all page titles in the
preferred order, isn't it possible to create a template that selects
the correct previous and next page title given the current page title?
I get stuck in getting the correct lines from the index page. DPL can
select based on section name (= page title), but then the contents of
that index section must be the prev/next links themselves:
=First Page=
Prev [[Second Page|Next]]
=Second Page=
[[First Page|Prev]] [[Third Page|Next]]
=Third Page=
.. etc.
This works, except that it is still a lot of duplication of page names
(but the edits are contained in a single page, big plus).
I hoped to simplify the index page by creating a template that writes
the section header and prev/next links, but then DPL no longer
recognizes the sections :-( Apparently DPL 'sees' the page text before
the templates are called ({{Page|Prev page|Page title|Next page}}:
{{Page||First Page|Second Page}}
{{Page|First Page|Second Page|Third Page}}
{{Page|Second Page|Third Page|Fourth Page}}
Basically my questions are:
1. Am I completely off track here?
2. Can DPL be coerced to evaluate templates before looking at the page
3. Can DPL (or another extension) select the text from a section
before/after a matched section?
4. Is it possible to determine the section sequence number given the
section name (so 'Second Page' results in 2, allowing me to use DPL to
retrieve the name of section 2 -/- 1 and 2 + 1 to create the prev/next
links?
Apologies for the long post, hopefully someone can point me to some
good resources (I've been to Meta, Wikibooks, Medawiki.org but could
very well have overlooked something there as the amount of info is a
bit overwhelming and it is difficult to judge how up to date it is).
--
Regards,
Jean-Marc
I'm seeing this weird anomaly in wiki syntax. Suppose you have this
template, called A:
{{#switch: {{{1}}}
| foo = [[File:foo.png]]
| bar = [[File:bar.png]]
| baz = [[File:baz.png]]
| UNKNOWN
}}
Now, with something like
{{A|foo}} and {{A|bar}}.
I get
<p><img src="foo.png"/>
</p>
<pre>and <img src="bar.png"/>
</pre>
<p>.
</p>
That is, the " and {{A|bar}}" is treated as a new paragraph. However,
if I have
[[File:foo.png]] and [[File:bar.png]].
I get
<p><img src="foo.png"/> and <img src="bar.png"/>.
</p>
So there is something with the newlines that are at the end of each
case, I'd presume. Compacting this all into one line appears not to
help. How can I change Template:A so that I get the more desirable
second outcome?
Hello,
I've enabled uploading, and it works for me (as sysop), but other users
can't upload file. When uploading it gives me the namespaceprotected
error message.
Which namespace is dedicated to the files uploaded?
I've tried setting the $wgGroupPermissions['*']['upload'] = true;
I've tried making a new group
$wgGroupPermissions['uploadaccess']['upload'] = true;
and still it gives me the error message for the namespaceprotected.
André
I'd like to share some exciting news with you all... After four awesome
years working for the Wikimedia Foundation full-time, next month I'm
going to be starting a new position at StatusNet, leading development on
the open-source microblogging system which powers identi.ca and other sites.
I've been contributing to StatusNet (formerly Laconica) as a user, bug
reporter, and patch submitter since 2008, and I'm really excited at the
opportunity to get more involved in the project at this key time as we
gear up for a 1.0 release, hosted services, and support offerings.
StatusNet was born in the same free-culture and free-software community
that brought me to Wikipedia; many of you probably already know founder
Evan Prodromou from his longtime work in the wiki community, launching
the awesome Wikitravel and helping out with MediaWiki development on
various fronts. The "big idea" driving StatusNet is rebalancing power in
the modern social web -- pushing data portability and open protocols to
protect your autonomy from siloed proprietary services... People need
the ability to control their own presence on the web instead of hoping
Facebook or Twitter always treat you the way you want.
This does unfortunately mean that I'll have less time for MediaWiki as
I'll be leaving my position as Wikimedia CTO sooner than originally
anticipated, but that doesn't mean I'm leaving the Wikimedia community
or MediaWiki development!
Just as I was in the MediaWiki development community before Wikimedia
hired me, you'll all see me in the same IRC channels and on the same
mailing lists... I know this is also a busy time with our fundraiser
coming up and lots of cool ongoing developments, so to help ease the
transition I've worked out a commitment to come into the WMF office one
day a week through the end of December to make sure all our tech staff
has a chance to pick my brain as we smooth out the code review processes
and make sure things are as well documented as I like to think they are. ;)
We've got a great tech team here at Wikimedia, and we've done so much
with so little over the last few years. A lot of really good work is
going on now, modernizing both our infrastructure and our user
interface... I have every confidence that Wikipedia and friends will
continue to thrive!
I'll start full-time at StatusNet on October 12. My key priorities until
then are getting some of our key software rollouts going, supporting the
Usability Initiative's next scheduled update and getting a useful but
minimally-disruptive Flagged Revisions configuration going on English
Wikipedia. I'm also hoping to make further improvements to our code
review process, based on my experience with our recent big updates as
well as the git-based workflow we're using at StatusNet -- I've got a
lot of great ideas for improving the CodeReview extension...
Erik Moeller will be the primary point of contact for WMF tech
management issues starting October 12, until the new CTO is hired. I'll
support the hiring process as much as I can, and we're hoping to have a
candidate in the door by the end of the year.
-- brion vibber (brion @ wikimedia.org)
CTO, Wikimedia Foundation
San Francisco
Hi,
I've been reading the docs here:
http://www.mediawiki.org/wiki/Help:FlaggedRevs and I think I get the
concepts. However, I don't understand how all the various settings
should be configured. Could someone with more know-how help me with
the required configuration for the following requirements?
Requirements (the most basic I can think of):
1) I'd like to set exactly two flags in one scale.
2) The scale should be called 'Quality' and the flags should be 'Good' or 'TBD'.
3) There should be exactly two Markers, 'Visible' and 'Review needed'.
4) Any revision with Quality = Good should be Visible.
5) Only the 'Visible' revision should be viewable (by default?) by
anonymous users.
6) Any other user (anyone signed in) should view (by default?) the
latest revision.
7) Only reviewers can review...
To be honest, I don't quite get the distinction between reviewers or
editors, but seeing the config for the first six requirements above
would get me well on the way to a fuller understanding of the system.
The extension seems impressive, but its so powerful, I'm having
difficulty tailoring it to my specific requirements!
Thanks very much on any hints on the above. As I said, I've been
reading http://www.mediawiki.org/wiki/Help:FlaggedRevs and
http://www.mediawiki.org/wiki/Flaggedrevs but I'm still lost. For
example, how is a marker associated with a set of flags in the config?
Cheers,
Dan.
Hello again,
How can I move a namespace to a new index? All I want
is to change the index from 106 to 112, so that articles
in this namespace are still found correctly.
Thanx
Javier
Buenas tardes,
Al intentar subir una imagen desde el formulario "subir archivo" el wiki
que he instalado me da un "Error interno" del tipo "No se pudo renombrar
el archivo desde x a y", siendo x una ruta con un archivo temporal que
el propio sistema crea e y una ruta que desconozco donde intenta guardar
el archivo.
En php.ini he puesto una ruta por defecto para archivos temporales, y nada.
En el wiki, localsettings.php, he puesto una carpera como "por defecto"
para subir archivos, con todos los permisos de r/w. Nada.
Empiezo a sospechar de algún problema de php.
¿Alguien me puede ayudar?
Gracias,
xgrager
Is it possible to import generated mediawiki markup using a script, instead of manually having to cut and paste it?
Perhaps there is a maintenance script that does this, but I couldn't figure out which one. It would help me a lot, since there are hundreds of pages that I would like to update in this way.
Best regards,
Wieger
--
_______________________________________________
Surf the Web in a faster, safer and easier way:
Download Opera 9 at http://www.opera.com
Powered by Outblaze