$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
Kind of a newbie question... I'm not even sure of the appropriate
taxonomy for my request, maybe that's why Google didn't help.
Using last stable (1.16.2 I believe), I'm trying to achieve this:
Got a default setup, Mediawiki installed in /w, Apache conf edited with
an Alias. So now my wiki is accessible at http://domain.tld/wiki/
I would like to link a specific namespace (let's say "bar") to its own
URL, outside of /foo/.
Ok, to rephrase, hopefully better:
I would like:
domain.tld/wiki/Bar:SomePage
to be in fact:
domain.tld/Bar/SomePage
And if Apache could rewrite on the client side /wiki/Bar:SomePage into
/Bar/SomePage that would be even better, albeit not a deal breaker.
Without breaking anything in MW of course. And if the Recent or Search
tool return the Bar:SomePage that's not an issue, I don't want to
rewrite the MW core :)
Anyone got an idea?
Salut à Vous !
MediaWiki, pour moi, est une suggestion d'un copain webmestre !
J'ai été Technicien de Maintenance Informatique et Analyste-Programmeur
de 1980 à 1996, mais, depuis, je m'occupe de Science des Systèmes Généraux,
et donc de Systémique, particulièrement en Terminologie et Ontologie !
J'ai suivi de loin les "nouveaux Langages", mais tout bêtement, ayant Téléchargé
XAMPP qui fonctionne, je me demande comment, avec tous les Fichiers en "*.php",
qui s'ouvrent avec le Navigateur, comment dire à Internet Explorer que c'est le
"contenu" du "Folder C:\ProgramFiles\mediawiki" qui est à lire, et précisément où lire !
Merci !
Eric Beaussart,
> Message du 28/07/11 00:30
> De : mediawiki-l-request(a)lists.wikimedia.org
> A : eric.beaussart(a)orange.fr
> Copie à :
> Objet : Welcome to the "MediaWiki-l" mailing list
>
> Bienvenue sur la liste MediaWiki-l(a)lists.wikimedia.org!
>
> Pour écrire à la liste, envoyez votre message à:
>
> mediawiki-l(a)lists.wikimedia.org
>
> Les informations générales concernant cette liste sont à l'adresse :
>
> https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
>
> Si vous souhaitez vous désabonner ou modifier vos options (par exemple
> activer/désactiver l'envoi groupé, changer votre mot de passe, etc.),
> consultez votre page d'abonnement à l'adresse :
>
> https://lists.wikimedia.org/mailman/options/mediawiki-l/eric.beaussart%40or…
>
>
> Vous pouvez également procéder par mail en envoyant un message à:
>
> MediaWiki-l-request(a)lists.wikimedia.org
>
> avec le mot "help" dans le sujet ou le corps du message (sans les
> guillemets), vous recevrez alors un message avec des instructions.
>
> Votre mot de passe est nécessaire pour ces modifications (y compris
> pour changer le mot de passe lui-même) ou pour résilier votre
> abonnement. Votre mot de passe est:
>
> cbf119450251a14
>
> En principe, Mailman vous rappellera mensuellement vos mots de passe
> pour les listes gérées sur lists.wikimedia.org, rappel que vous
> pourrez toutefois désactiver à votre convenance. Cet avis mensuel
> contiendra également des instructions vous permettant de résilier
> votre abonnement si vous le désirez ou de modifier vos options
> d'abonnement. Vous trouverez un bouton dans la page de vos options
> pour vous faire parvenir votre mot de passe par courriel.
>
Hey all,
We're very happy to announce the first release of a new (Semantic) MediaWiki
extension titled Semantic Watchlist.
Semantic Watchlist extends Semantic
MediaWiki<http://semantic-mediawiki.org/>by adding the capability to
watch/follow sets of properties for groups of
pages (that can be specified with categories and namespaces). You can view
changes to these properties via Special:SemanticWatchlist, which works
similar to the regular MediaWiki watchlist. You can also request to be
notified via email when a change is made.
There are already two extensions that notify users about changes to SMW
property values: Semantic Notifications [2] and Semantic NotifyMe [3]. We
decided to create a new extension because we wanted the ability for users to
get notifications in ways other than email: via a watchlist on the page, or
potentially via other ways in the future as well, like Twitter updates.
A writeup of the functionality of this extension, including some screenshots
and download links can be found on Jeroens blog [0]. Documentation for the
extension can be found on MediaWiki.org [1].
[0]
http://blog.bn2vs.com/2011/07/30/new-mediawiki-extension-semantic-watchlist/
[1]
https://secure.wikimedia.org/wikipedia/mediawiki/wiki/Extension:Semantic_Wa…
[2]
http://smwforum.ontoprise.com/smwforum/index.php/Help:Semantic_Notification…
[3]
https://secure.wikimedia.org/wikipedia/mediawiki/wiki/Extension:Semantic_No…
Cheers
Jeroen De Dauw & Yaron Koren
Hey all,
I'm very happy to announce the release of Semantic MediaWiki 1.6.
This release has been in the making over the past four months and includes
contributions by many people. It brings significant improvements to SMWs
architecture and introduces many new features. The most important changes
are listed below:
* Full support added for storing SMW data directly within an RDF
triplestore, and for answering #ask queries based on this data.
* The Type namespace has been abolished. Builtin types now are displayed by
the special page Special:Types, and there are no "custom types" any longer.
* Changed the way in which units of measurement work. Type:Number now does
not accept any units, and a new type "Quantity" is used for numbers with
units.
* The declaration of Type:Record properties has changed. Instead of a list
of datatypes, the declaration now requires a list of properties that are to
be used for the fields of the record.
* Introduced pre-defined builtin properties for every datatype.
* Changed the way parameters in query printers are specified and handled
using the Validator extension.
* Added UNIX-style DSV (Delimiter-separated values) result format.
* Reworked internal data model.
* Fixed PostgreSQL issues with the installation and upgrade code.
* Added #smwdoc parser hook that displays a table with parameter
documentation for a single specified result format.
* Fixed escaping issues in the JSON result format.
For a more comprehensive list of these changes, see the release notes [0]
and blog post I made about this release [1]. As usual, you can also consult
the SMW 1.6 page on the SMW wiki [2] and the installation and upgrade
instructions [3].
To keep up to date with SMW developments, you can follow the SMW Twitter [4]
or Indenti.ca [5].
[0]
http://svn.wikimedia.org/viewvc/mediawiki/tags/extensions/SemanticMediaWiki…
[1] http://blog.bn2vs.com/2011/07/30/semantic-mediawiki-1-6-released/
[2] http://semantic-mediawiki.org/wiki/Semantic_MediaWiki_1.6
[3] http://semantic-mediawiki.org/wiki/Help:Installation_1.6
[4] https://twitter.com/#!/SemanticWiki
[5] https://identi.ca/smw
Cheers
--
Jeroen De Dauw
http://www.bn2vs.com
Don't panic. Don't be evil.
--
Hey all,
I'm happy to announce the release of Semantic Result Formats 1.6 [0]. This
release adds several new features and compatibility with Semantic MediaWiki
1.6.
Changes in this version:
* Added compatibility with SMW 1.6.
* Rewrote math formats for efficiency, correct recursion and handling of
multiple numerical properties.
* Cleaned up the graph format.
* Fixed division by zero issue (oh shii~) in the tagcloud format.
* Added parameter descriptions to the graph and ploticus formats.
* Added support for SMW 1.6 style parameter handling to the tagcloud format.
* Somewhat cleaned up the BibTeX format.
* Fixed double HTML escaping issue in the tagcloud format.
* Added fileextensions parameter to the Gallery format and added missing
parameter description messages.
New result formats in this version are:
* product
* median
You can find download and installation instructions here [1]. This version
of SRF has been included in the Semantic Bundle [2] that was released
yesterday, so can be obtained by downloading SB as well.
Thanks to all people that helped out with this release by finding bugs,
submitting patches, testing, translating, ect.
The Exhbit format is currently broken with MW 1.17 and above, and is in need
of a maintainer. If you are interested in taking care of that format,
definitely poke me.
[0]
https://secure.wikimedia.org/wikipedia/mediawiki/wiki/Extension:Semantic_Re…
[1]
https://secure.wikimedia.org/wikipedia/mediawiki/wiki/Extension:Semantic_Re…
[2] https://secure.wikimedia.org/wikipedia/mediawiki/wiki/Semantic_Bundle
Cheers
--
Jeroen De Dauw
http://www.bn2vs.com
Don't panic. Don't be evil.
--
We just installed version 1.17 on our system. (sun, solaris) and find if
someone goes to log on and enters the wrong password they get a blank
page. If they try to log on and just don't put a password in you get
this page:
http://www.xxx.org/wiki/index.php?title=Special:UserLogin&action=submitlogi…
Is this a bug or do I have something set up wrong? I looked through
the bug tracker but saw no bugs of this.
Jeff
Gentlemen, try it yourself.
In Facebook share a link to a MediaWiki wiki or article.
Is the picture that appears to the right of the link what you expect?
Why can't it offer the site logo as one of the choices?
> Go report it to Facebook, Holmes.
Well Facebook is rather big compared to MediaWiki, they can't hear
little voices like mine, so maybe MediaWiki could make some adjustments
on the MediaWiki side.
The problem is even worse when quoting a MediaWiki URL in a Facebook
comment. In this case one ends up with the wretched "Powered by
MediaWiki" logo as the only choice, despite ones painstaking crafted
site logo.
When quoting Wikipedia in a FB comment one ends up with equivalent gunk
from the bottom of the page.
Try it yourself. FB started putting image "previews" in comments last week.
Looking further into the problem, we see it all stems from MediaWiki
(people, staff, you), non-knowledge of how text browsers or search
engines work.
> We know how they work, but they don't matter because all we know is
> how things look in our browser
Can you believe that text browser users are denied any knowledge of the
site logo either? No blip on the screen like there might be for a normal
image. Nothing.
> Yeah, well there is no reason for anybody to use a text browser, so screw 'em
The most important image on an entire MediaWiki site, and it lays
wrapped up in some <!-- logo --> markup that makes big assumptions <!--/logo -->.
Ha Ha, Ha Ha, told you so *for years*. Now when anybody quotes a
MediaWiki article on Facebook, there is a 95% chance it will look bad...
serves you all right! Plus (Google+? Dare not also test it there to see
what happens), it is NOT a Facebook bug. Ho Ho Ho. Muhahaha.
Ho Ha, Q: what are the goofiest looking links on Facebook? A: MediaWiki links!