There may be something in there I didn't account for - I haven't tested any
of this (just looked at the code).
In general, it's not a good idea to hack the core code unless you have a
good reason to do so. Are you trying to limit the namespaces for your
personal use, or for everybody?
If you're trying to keep everyone from seeing changes in other namespaces,
the "proper" place to hack the code would be later on in that method -
during the SQL query generation step. My suggestion was just to alter the
defaults - not limit functionality.
-- Jim
On 3/19/07, Frederik Dohr <fdg001(a)gmx.net> wrote:
I've tried this today - unsuccessfully:
In SpecialRecentchanges.php, I've changed the code as you've described:
'namespace' => null
to either one of the following:
'namespace' => '2',
'namespace' => 2, /* not sure if that makes a difference in PHP */
'namespace' => NS_USER, /* probably the best solution */
(as well as changing "invert" to true)
However, nothing has changed whatsoever; the RecentChanges list is still
the same (I've also tried it with the URL parameter "action=purge", but
to no avail).
Even if I do not invert the results (i.e. only want to display results
from the USER namespace), the RecentChanges list does not change one bit.
This is very puzzling to me - though I assume there's a very simple
explanation for it... !?
-- F.
_______________________________________________
MediaWiki-l mailing list
MediaWiki-l(a)lists.wikimedia.org
http://lists.wikimedia.org/mailman/listinfo/mediawiki-l