Within Google Analytics, I set up "Goals" for article edits, new account
creation, and user login. This tells me the % of visits that result in an
action being taken rather than just passive reading. In addition, it tells
me the referrer information (site, search engine, keyword, etc) as well as
other visitor data for each goal so I can tell where my most "likely to
contribute" visitors are coming from.
Good luck!
andrew(a)richmondwiki.org
On Sun, Oct 26, 2008 at 8:00 AM, <mediawiki-l-request(a)lists.wikimedia.org>wrote;wrote:
Send MediaWiki-l mailing list submissions to
mediawiki-l(a)lists.wikimedia.org
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
or, via email, send a message with subject or body 'help' to
mediawiki-l-request(a)lists.wikimedia.org
You can reach the person managing the list at
mediawiki-l-owner(a)lists.wikimedia.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of MediaWiki-l digest..."
Today's Topics:
1. Re: Using export/import instead of upgrading (Brion Vibber)
2. Re: Using export/import instead of upgrading (Tim Starling)
3. Re: Using export/import instead of upgrading (Tim Starling)
4. Upgrading to current release (Skins question) (K. Peachey)
5. Re: Meaningful stats for MediaWiki (Matthias Korn)
----------------------------------------------------------------------
Message: 1
Date: Sat, 25 Oct 2008 19:04:59 -0700
From: Brion Vibber <brion(a)wikimedia.org>
Subject: Re: [Mediawiki-l] Using export/import instead of upgrading
To: MediaWiki announcements and site admin list
<mediawiki-l(a)lists.wikimedia.org>
Message-ID: <4903D04B.1050001(a)wikimedia.org>
Content-Type: text/plain; charset=ISO-8859-1
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Jan Steinman wrote:
Anyone have any good strategies going from 1.3 to
current? I'm
planning on making a complete copy, accessed from a new URL, and
trying the upgrade on that. But I'm doubtful that such an upgrade will
be fruitful.
1) Back up your database
2) Grab the current code and put it in place of your old code
3) Follow the upgrade instructions.
The updater should update the database automatically from any MediaWiki
installation version 1.2 or later. The one serious exception to this is
that installations from prior to 1.5 which used Latin-1 encoding instead
of UTF-8 may require a separate character set conversion first. (To add
a little to the confusion, this issue is dependent on the $wgUseLatin1
config variable in your LocalSettings.php, _not_ the "character set"
setting on MySQL.)
Otherwise, there are no *known* problems that should prevent you from
upgrading directly from 1.3 to 1.13, as long as your PHP, MySQL etc are
current.
If you actually do encounter an error while following the standard
upgrade procedure, we want to find out about it so we can fix it! Please
save the *exact output* from the updater *at the time you first ran it*,
which should show any error conditions encountered during the update.
And don't forget to back everything up first. ;)
- -- brion vibber (brion @
wikimedia.org)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
Comment: Using GnuPG with Mozilla -
http://enigmail.mozdev.org
iEYEARECAAYFAkkD0EoACgkQwRnhpk1wk46tuwCdFsTHSAXulgaIYX9MmI612muG
NqUAnRhbSW/3BFsgV9vkXvfVw3hhnMRZ
=opHP
-----END PGP SIGNATURE-----
------------------------------
Message: 2
Date: Sun, 26 Oct 2008 13:06:16 +1100
From: Tim Starling <tstarling(a)wikimedia.org>
Subject: Re: [Mediawiki-l] Using export/import instead of upgrading
To: mediawiki-l(a)lists.wikimedia.org
Message-ID: <ge0jap$7hg$1(a)ger.gmane.org>
Content-Type: text/plain; charset=ISO-8859-1
Jan Steinman wrote:
> I believe the OP suggested export/import because they had fallen way
> behind, and lacked confidence in an upgrade process that is generally
> designed for Wikipedia's needs of strictly sequential incremental
> upgrades.
> I am in the same situation, running
1.3. Short of upgrading to 1.4,
> then 1.5, then 1.6... I don't believe this posting really addresses
> strategies for someone who is way behind to "catch up." The further
> you are behind, the more likely something will break, no matter how
> carefully one follows the instructions for upgrading from 1.13.1 to
> 1.13.2.
Anyone have any good strategies going from 1.3 to current? I'm
planning on making a complete copy, accessed from a new URL, and
trying the upgrade on that. But I'm doubtful that such an upgrade will
be fruitful.
I put the answer to this question in the upgrade FAQ, and since then I've
answered it about another 5 times on mediawiki-l.
http://www.mediawiki.org/wiki/Manual:FAQ#Upgrading
I don't know how many more times I'm going to have to say it.
Upgrades for 1.3 to 1.13 were tested automatically prior to the release of
1.13 using an automated upgrade test:
<
http://svn.wikimedia.org/viewvc/mediawiki/trunk/release-tools/upgradeTest.p…
There are no open bug reports regarding upgrading from 1.3 to 1.13. The
vast majority of reports indicate that it works just fine.
Upgrading may take a long time. Back up your wiki in case the upgrade
script is aborted halfway through and leaves your wiki in an intermediate
state.
The upgrade script is inherently incremental. The updaters.inc file has a
large list of database operations which have been steadily accumulating
since the first MediaWiki release. They are run in the order in which they
were added. Occasionally obsolete or redundant upgrades are removed. So
running each upgrader in turn is effectively equivalent to running the
most recent one.
Some of the old upgraders had bugs. We fixed them in later major releases.
If you run the old upgraders, you risk encountering unfixed bugs in them.
Old upgraders are not supported and we will ignore bug reports against
them. If you encounter a bug when upgrading directly from 1.3 to 1.13, we
will fix it. If you encounter a bug when upgrading from 1.3 to 1.4, we
will ignore you.
-- Tim Starling
------------------------------
Message: 3
Date: Sun, 26 Oct 2008 13:29:21 +1100
From: Tim Starling <tstarling(a)wikimedia.org>
Subject: Re: [Mediawiki-l] Using export/import instead of upgrading
To: mediawiki-l(a)lists.wikimedia.org
Message-ID: <ge0km2$9up$1(a)ger.gmane.org>
Content-Type: text/plain; charset=ISO-8859-1
Jan Steinman wrote:
>> From: Daniel Friesen <dan_the_man(a)telus.net>
>>
>> People complain about issues cause they don't follow instructions...
> (Much good advice about how to do
incremental upgrades clipped...)
>> Remember Wikipedia? Wikimedia
runs off MediaWiki and is being
>> constantly
>> upgraded. If the upgrade process wasn't handled right then you'd see
>> Wikipedia broken all the time.
> I believe the OP suggested
export/import because they had fallen way
> behind, and lacked confidence in an upgrade process that is generally
> designed for Wikipedia's needs of strictly sequential incremental
> upgrades.
One more thing: the upgrader is NOT used by Wikimedia and is not designed
for it. We've never run the upgrader on Wikimedia while I've been around.
The upgrader is designed for small wikis and is aimed at a general
non-technical user audience.
To upgrade Wikimedia wikis, we run the SQL patch files directly, or write
special replication-friendly scripts. We aim for at most a few minutes of
read-only time even for a huge wiki like the English Wikipedia, and that
goal sometimes requires quite a bit of planning and effort to achieve.
-- Tim Starling
------------------------------
Message: 4
Date: Sun, 26 Oct 2008 13:10:45 +1000
From: "K. Peachey" <p858snake(a)yahoo.com.au>
Subject: [Mediawiki-l] Upgrading to current release (Skins question)
To: "---, Mailing List: MediaWiki announcements and site admin list"
<mediawiki-l(a)lists.wikimedia.org>
Message-ID:
<4c103ee70810252010l4a3b8a1p9dde87d6a407a952(a)mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
I'm planning on upgrading from a fairly old install (pre 1.11.0) and
we have a skin coded/based on the default monobook, will we need
anything to make this compatible with the latest install?
-Peachey
------------------------------
Message: 5
Date: Sun, 26 Oct 2008 11:59:52 +0100
From: Matthias Korn <matsch(a)rockinchina.com>
Subject: Re: [Mediawiki-l] Meaningful stats for MediaWiki
To: mediawiki-l(a)lists.wikimedia.org
Message-ID: <20081026115952.72f42046(a)ThinkOfMe.binaervarianz.de>
Content-Type: text/plain; charset=US-ASCII
Well, I tried FireStats now. It doesn't really provide anything I
didn't already know.
What is everyone using for their statistic needs?
Maybe their is a possibility to exploit the Extra Section feature of
AWStats!?
Regards,
matsch
Am Sat, 25 Oct 2008 16:02:12 +0200
schrieb Matthias Korn <matsch(a)rockinchina.com>om>:
> Hi all,
> what is a good approach for
meaningful MediaWiki statistics?
> They should show which pages are accessed frequently and over time,
> maybe also edits and everything else relevant to a MediaWiki
> installation.
> Normal log file analysers don't
cope with particularities of
> MediaWiki.
> I saw this extension, but from the
demo it doesn't look very
> promising:
http://www.mediawiki.org/wiki/Extension_talk:FireStats
> Thanks,
> matsch
--
Rock in China
http://wiki.rockinchina.com/
http://www.rockinchina.com/
------------------------------
_______________________________________________
MediaWiki-l mailing list
MediaWiki-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
End of MediaWiki-l Digest, Vol 61, Issue 46
*******************************************