Hi,
I would have to add in the "Main Page", of my wiki page, a box with the last 5 guides and a second box with the last 5 help create. The pages begin with guides Guide:guide_name and help those with just with Help:help_name. Is there a way to get there you should appear automatically or modify the "Home" manually?
thanks
Matteo
---------------------------------
Scopri la community di Io fotografo e video
Il nuovo corso di Gazzetta dello sport per diventare veri fotografi!
> Date: Mon, 27 Oct 2008 15:10:39 +0100 (CET)
> From: Matteo Manzinello <mmanzinello(a)yahoo.it>
> Subject: [Mediawiki-l] Generare lista con ultime guide:* create
> To: mediawiki-l(a)lists.wikimedia.org
> Message-ID: <802375.96331.qm(a)web25005.mail.ukl.yahoo.com>
> Content-Type: text/plain; charset=iso-8859-1
>
> Salve,
> avrei la necessit? di aggiungere nella "pagina principale", del
> wiki che st? creando, un riquadro con le ultime 5 guide e un
> secondo riquadro con gli ultimi 5 help creati. Le pagine di guide
> iniziano con Guide:nome_guida e quelle con help appunto con Help:aiuto.
> C'? un modo per far si ch? appaiano automaticamente o devo modifcare
> la "Pagina principale" manualmente?
> grazie
> Matteo
Ciao Matteo, prima di tutto un consiglio: la lista è in inglese, se vuoi
che tutti comprendano la tua domanda, ti conviene scrivere in inglese.
Per quanto riguarda il tuo problema, potresti creare un template che
selezioni le ultime pagine modificate. Per fare la selezione ti conviene
ricorrere ad una estensione: molto utile è la DPL (Dynamic Page List)
che consente di ottenere moltissimi tipi di report sulle pagine e di
fare poi inclusioni del risultato.
Ciao
G.
--
Giuseppe Briotti
g.briotti(a)mclink.it
"Alme Sol, curru nitido diem qui
promis et celas aliusque et idem
nasceris, possis nihil urbe Roma
visere maius."
(Orazio)
Regarding the statistics for MW, I use Google Analytics via this extension:
http://www.mediawiki.org/wiki/Extension:Google_Analytics_Integration
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:
> 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>:
>
> > 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
> *******************************************
>
>
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/
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
I have a dedicated server, and I am trying to set up multiple accounts
(multiple domains and Mediawiki installations) with short URLs. If I
follow the alias instructions by putting this in the httpd.conf file:
Alias /wiki /home/firstdomainname/www/w/index.php
It basically overrides this for any other domain I set up. Are there
instructions on how to do this for multiple domains on a single
server?
Thanks,
Bobby
Hello
I would like to know why, instead of upgrading from a very old Mediawiki
version the following procedure is not possible :
1. save all pages + histories on disk using something like export
2. install a fresh uptodate Mediawiki
3. import all pages + histories from disk
4. remove the old mediawiki version
Best
Francois Colonna
I'm wondering what the best approach is for me to set up a shared user table
between my wikis.
Each wiki is sharing the same code (via symlinks) but a different databases.
Do I:
a. Merge all the wikis into one database using prefixes, then setup the
shared user table (straightfoward)
b. Some how connect the seperate databases together. Can MySQL Alias/Symlink
a table to another database?
Thanks,
Samuel Richardson
Freelance Web Developer
www.richardson.co.nz | 0405 472 748
Have you added your business to the Melpedia yet? http://www.melpedia.com.au
On my MediaWiki site I'm about to set
$wgRawHtml = true;
in order to allow YouTube and other embedded content. However, the
manual says (http://www.mediawiki.org/wiki/Manual:$wgRawHtml):
Warning: This is very dangerous on a publicly editable site, so you
shouldn't enable it unless you've restricted editing to trusted users
only
When it says "very dangerous", what does this mean? Does it for
example enable an exploit that would let someone hack into the
MediaWiki site? Or does it merely allow Javascript that would allow a
malicious person to harm a user's computer if they view the page?
(I'm aware I could use an extension such as
http://www.mediawiki.org/wiki/Extension:VideoFlash but that would
limit me to embedding stuff from just thoase sites it allows.)
--
Philip Hunt, <cabalamat(a)googlemail.com>
Please avoid sending me Word or PowerPoint attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html
I am getting the following error on a 1.13.0 mediawiki install. It started
last night. Any help on how to resolve this would be appreciated.
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 "MediaWikiBagOStuff::_doinsert". MySQL returned
error "1213:
Deadlock found when trying to get lock; try restarting transaction
(localhost)".
Lennie
--
Office: 847-548-4562
Mobile: 847-302-3985
Twitter: http://twitter.com/ljarratt
Facebook: http://www.facebook.com/people/Lennie_Jarratt/1182350486
Plurk: http://www.plurk.com/user/ljarratt
"The necessity of the times, more than ever, calls for our utmost
circumspection, deliberation, fortitude, and perseverance." - Samuel Adams