------------ Původní zpráva ------------
Od: <mediawiki-l-request(a)lists.wikimedia.org>
Předmět: MediaWiki-l Digest, Vol 88, Issue 37
Datum: 27.1.2011 13:01:32
----------------------------------------
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: Hiding "subst:" syntax inside a template possible? (nakohdo)
2. Re: Re moving a custom namespace? (nakohdo)
3. My MediaWiki questions (Santosh Krishnan)
4. Re: Undefined index complaints by PHP 5.3.5 (Dan Nessett)
5. Support the new MediaWiki question and answer website
(Jeremy Rudd)
6. Re: One software for multiple websites (Gordon Joly)
7. Re: My MediaWiki questions (Platonides)
8. Re: External Link Opening in New Tab or Window (Charlie Markwick)
9. Dablink (Ekompute .info)
----------------------------------------------------------------------
Message: 1
Date: Wed, 26 Jan 2011 06:31:52 -0800 (PST)
From: nakohdo <Frank.Ralf(a)gmx.net>
Subject: Re: [Mediawiki-l] Hiding "subst:" syntax inside a template
possible?
To: mediawiki-l(a)lists.wikimedia.org
Message-ID: <30765853.post(a)talk.nabble.com>
Content-Type: text/plain; charset=us-ascii
Platonides wrote:
Technically speaking "subst:" is a
parser function, isn't it?
Not exactly a parser function. I would call it a /modifier/ for
templates/parser functions.
Could I a
least create an alias for it (by modifying magic words?) which is more
meaningful for non English speakers?
You are not expected to translate it. You would need to modify
includes/MagicWord.php *and* the literal comparison in
includes/parser/Parser.php at braceSubstitution()
Thanks, Platonides, for those glimpses into the inner workings of MediaWiki.
I have opted for your suggested solution of adding respective buttons to the
WYSIWYG editor which IMO is better than tampering with core files ;-)
--
View this message in context:
http://old.nabble.com/Hiding-%22subst%3A%22-syntax-inside-a-template-possib…
Sent from the WikiMedia General mailing list archive at
Nabble.com.
------------------------------
Message: 2
Date: Wed, 26 Jan 2011 06:45:01 -0800 (PST)
From: nakohdo <Frank.Ralf(a)gmx.net>
Subject: Re: [Mediawiki-l] Re moving a custom namespace?
To: mediawiki-l(a)lists.wikimedia.org
Message-ID: <30765856.post(a)talk.nabble.com>
Content-Type: text/plain; charset=us-ascii
Daniel Barrett-3 wrote:
What is the safest way to remove a custom namespace after all its articles
have been deleted? If we just remove it from $wgExtraNamespaces, there
will still be database entries (e.g., in the archive table) that reference
the old namespace number, and I don't know if this will cause problems or
not.
Hi Dan,
I've been tinkering with changing namespaces lately, changing the numerical
index for an existing namespace for avoiding conflict with namespaces used
by certain extensions
(
http://www.mediawiki.org/wiki/Extension_namespace_registration ). I found
the namespace implementation quite robust and haven't encountered any
problems yet after the changes.
AFAIK the only place in the database where references to the namespace of a
given page are stored is the respective field in the "page" table which you
might even change directly.
hth
Frank
--
View this message in context:
http://old.nabble.com/Removing-a-custom-namespace--tp30762329p30765856.html
Sent from the WikiMedia General mailing list archive at
Nabble.com.
------------------------------
Message: 3
Date: Wed, 26 Jan 2011 11:07:24 -0500
From: Santosh Krishnan <santosh(a)vividconsulting.info>
Subject: [Mediawiki-l] My MediaWiki questions
To: mediawiki-l(a)lists.wikimedia.org
Message-ID:
<AANLkTi=p7PGvXUEqJ4i3NxVc_858C3Audp2_OyhxhWHg(a)mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Hi Everyone,
I've used an older version of MediaWiki and I've seen how powerful it can
be. I have a few questions, which I've been unable to answer and am hoping
that you can do so.
My concerns are chiefly around security and user access.
Since I'm not trying to use it to create a user editable Wiki, I would want
to disallow the general user to be able to create any content within the
deployed implementation. I would want only my designated personnel to
create and maintain documents within it. I don't know if it's possible to
restrict it on this level.
Second, I wouldn't want it to look like Wikipedia, and specifically, I would
want it to have a visual look and feel in line with the remainder of my
website. I know that we can implement skins on MediaWiki, but I don't know
how versatile it is.
Third, I would want to be able to restrict certain pages from being viewed
without someone having logged in (and I would want those user IDs to be
controlled by my personnel so that only if one of my guys provides a user ID
will that page be accessible - meaning that perhaps we have private
information and we must first validate that the person who wishes to view it
is first vetted by my team and then my team member will create a user ID for
that person). Is this possible?
Please let me know your thoughts on this.
Thanks,
--
Santosh Krishnan
------------------------------
Message: 4
Date: Wed, 26 Jan 2011 17:16:05 +0000 (UTC)
From: Dan Nessett <dnessett(a)yahoo.com>
Subject: Re: [Mediawiki-l] Undefined index complaints by PHP 5.3.5
To: mediawiki-l(a)lists.wikimedia.org
Message-ID: <ihpksl$afh$1(a)dough.gmane.org>
Content-Type: text/plain; charset=UTF-8
On Tue, 25 Jan 2011 19:16:57 -0500, Chad wrote:
On Tue, Jan 25, 2011 at 6:36 PM, Dan Nessett
<dnessett(a)yahoo.com> wrote:
After some research these seem to occur because
the default value of
$wgLocalFileRepo set in Settings.php includes the array element:
'deletedHashLevels' => $wgFileStore['deleted']['hash']
Well the default configuration of $wgFileStore['deleted'] should be an
array and 'hash' should be one of its keys. This is true in 1.13.x thru
1.16.x. It sounds like you're overwriting the $wgFileStore defaults
(either in your LocalSettings or in an extension)
Anyone here have ideas how to eliminate these?
Upgrade to the 1.17 branch ;-) $wgFileStore has been removed from core,
the only useful thing it contained was
$wgFileStore['deleted']['directory'] which has been turned into
$wgDeletedDirectory.
Otherwise, I'd check your LocalSettings and any extensions that might
have messed with the default $wgFileStore configuration.
-Chad
Thanks. I found the problem (DefaultSettings was corrupt).
--
-- Dan Nessett
------------------------------
Message: 5
Date: Thu, 27 Jan 2011 01:40:25 +0530
From: Jeremy Rudd <jrudd.developer(a)gmail.com>
Subject: [Mediawiki-l] Support the new MediaWiki question and answer
website
To: mediawiki-l(a)lists.wikimedia.org
Message-ID: <4D407FB1.1060907(a)gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Hi,
MediaWiki has a great support system and a simplistic forum. But
newcomers and old hands alike would have lots of similar questions about
the system, installation issues, or other questions that could be
answered quickly if there was a better system for it.
We all know the concept of forums, but StackExchange (remember
StackOverflow? or MathOverflow?) have started a new system where
questions can be asked, found, answered and sorted very effectively, and
its even better than Yahoo Answers.
The results are fast and accurate. Great users get reputation, and hence
more rights. The system has really been a success and with a little bit
of YOUR help, we could have a StackExchange dedicated to MediaWiki and
your wiki questions!
1. Visit the Wikipedia and Wikis
<http://area51.stackexchange.com/proposals/13716> proposal
2. Login
3. Click the "Follow" button
Thank you for supporting this venture!
Jeremy Rudd
------------------------------
Message: 6
Date: Wed, 26 Jan 2011 22:40:28 +0000
From: Gordon Joly <gordon.joly(a)pobox.com>
Subject: Re: [Mediawiki-l] One software for multiple websites
To: mediawiki-l(a)lists.wikimedia.org
Message-ID: <4D40A2DC.8010406(a)pobox.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
On 21/01/2011 21:16, Daniel Barrett wrote:
Instead of inventing your own method, you can see
how other people have done
this:
I can see how that would work.... unless you change files and settings
outside LocalSettings.php (or not??)
Gordo
--
Gordon Joly
gordon.joly(a)pobox.com
http://www.joly.org.uk/
Don't Leave Space To The Professionals!
------------------------------
Message: 7
Date: Thu, 27 Jan 2011 00:20:57 +0100
From: Platonides <Platonides(a)gmail.com>
Subject: Re: [Mediawiki-l] My MediaWiki questions
To: mediawiki-l(a)lists.wikimedia.org
Message-ID: <ihqa3q$3i3$1(a)dough.gmane.org>
Content-Type: text/plain; charset=ISO-8859-1
Santosh Krishnan wrote:
Hi Everyone,
I've used an older version of MediaWiki and I've seen how powerful it can
be. I have a few questions, which I've been unable to answer and am hoping
that you can do so.
My concerns are chiefly around security and user access.
Since I'm not trying to use it to create a user editable Wiki, I would want
to disallow the general user to be able to create any content within the
deployed implementation. I would want only my designated personnel to
create and maintain documents within it. I don't know if it's possible to
restrict it on this level.
It's quite easy if done in an all-of-nothing fashion. You could for
instance forbid anoynmous users to edit or create accounts.
Or in your case, allow editing just for those in a given group.
Second, I wouldn't want it to look like
Wikipedia, and specifically, I would
want it to have a visual look and feel in line with the remainder of my
website. I know that we can implement skins on MediaWiki, but I don't know
how versatile it is.
It can be done. It mosly depends on how versatile is the guy you have
creating your skin.
Third, I would want to be able to restrict
certain pages from being viewed
without someone having logged in (and I would want those user IDs to be
controlled by my personnel so that only if one of my guys provides a user ID
will that page be accessible - meaning that perhaps we have private
information and we must first validate that the person who wishes to view it
is first vetted by my team and then my team member will create a user ID for
that person). Is this possible?
It's easy to only let your team to create accounts. It's also easy to
restrict the whole wiki so that it is only viewable for registered users
(with the ability to except a handful of pages).
If you want to make it so that some pages can only be viewed by some
users, and several of them they unable to view each others private
pages, then MediaWiki has no support for that. You need to enter into
the world of security extensions. Doesn't look hard, but there's always
the case that it doesn't take into account some loophole through which
it's possible to access that kind of page which you were not supposed to.
------------------------------
Message: 8
Date: Thu, 27 Jan 2011 09:38:00 -0000
From: "Charlie Markwick" <charlie-markwick(a)southcot.com>
Subject: Re: [Mediawiki-l] External Link Opening in New Tab or Window
To: "MediaWiki announcements and site admin list"
<mediawiki-l(a)lists.wikimedia.org>
Message-ID:
<CB70B5CCE4319D4ABEA54BB12D3117CF01487D90(a)southcotpdc.southcot.org>
Content-Type: text/plain; charset="us-ascii"
-----Original Message-----
From: Charlie Markwick
Sent: 24 January 2011 16:25
To: 'MediaWiki announcements and site admin list'
Subject: RE: [Mediawiki-l] External Link Opening in New Tab or Window
I've added this to MediaWiki:Common.js but it changes nothing. I have
tried clearing the cache and also accessing the URL using another
browser that hasn't accessed the wiki before. No difference.
-------------------------------
/* Any JavaScript here will be loaded for all users on every page load.
*/
// Anything in this function wrapper will be executed when the page is
ready for action
( function( $ ) {
$( document ).ready( function() {
// Open external links in the sidebar in a new window
$( '#mw-panel, #panel' ) // #panel is for pre-1.17 compatibility
.find( 'li a' )
.filter( '[href^=http://], [href^=https://]' )
.attr( 'target' , '_blank' );
} );
} )( jQuery );
Charlie
------------------------------
Message: 9
Date: Thu, 27 Jan 2011 18:26:26 +0800
From: "Ekompute .info" <ekompute(a)gmail.com>
Subject: [Mediawiki-l] Dablink
To: MediaWiki announcements and site admin list
<mediawiki-l(a)lists.wikimedia.org>
Message-ID:
<AANLkTi=8NysAWCXj72sFhW7k1esr4W7t4mcHWbsxzF3N(a)mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Hi, I just upgraded to Mediawiki 1.16.1 but I found that the dablink is not
working. It is not italicized, nor is it indented. What could be the
possible reason? It happens to both my Mediawiki 1.16.0 and Mediawiki 1.16.1
installations, but not my 1.14.0.
--
PM Poon
------------------------------
_______________________________________________
MediaWiki-l mailing list
MediaWiki-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
End of MediaWiki-l Digest, Vol 88, Issue 37
*******************************************