I have been experiencing horrible lags and stalling
on the spanish wikipedia. I have checked the english
and german at the same time to see if there are
problems there too, but they worked fine.
es.wikipedia is a very low traffic wiki, so i don't
understand this.
Are there any server or sql parameters that were
modified on the german and english wikipedias, but not
on the spanish one?
AstroNomer
__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
Ahh, the ever-changing watchlist. :)
I've just checked in changes to switch the watchlist table to use
namespace/title pairs instead of the cur_id numeric key. This may sound
like a dumb idea, but it's actually good:
* Restores ability to watch nonexistent pages that may come into being
(or pages that are deleted and recreated -- with a different cur_id, but
the same title)
* Makes it easier to deal with article/talk pairs; just and/or out the
ones bit of the namespace. Now articles and their talks are considered
identical; if you're watching one, you're watching the other. If you
unwatch one, you unwatch the other.
I also would like it to deal better with renames; it's been suggested
(bug report 654899) that both the old and new titles be included in the
watchlist. The old old behavior was to show only the old title, which
would show up at the time of move as 'moved to XX' (good if you notice
it, but won't show any more edits to the article unless you explicitly
follow the redirect and add it); the current behavior is to show only
the new title, which remains buried at its last edit (but if it's edited
again, you see the current edits).
At the moment the cvs code will dupe the watchlist entry for the new
title too, but only for the user doing the rename. It should do that for
all users, which sounds annoying since you can't do an INSERT INTO ...
SELECT FROM the same table in MySQL. So probably a loop, urgh.
Code is running on test.wikipedia.org; try it out and let me know if
it's horribly broken before I install it around in the morning.
I've added a 'patch-list.txt' in the maintenance directory; the
watchlist fixerupper code is in path-watchlist.sql.
-- brion vibber (brion @ pobox.com)
I followed the instructions in the INSTALL file, and got Wikipedia up
and running.
However, the URL rewriting, cut and pasted from the INSTALL file,
doesn't seem to work at all. This seems to work:
http://reactor-core.org/t/wiki.phtml?title=Main_Page
But this does NOT:
http://reactor-core.org/t/wiki/Main_Page
Any ideas what I am doing wrong?
Here is the relevant section of my httpd.conf:
=== SNIP ===
<Directory /usr/home/djw/src/wikipedia/phpwiki/newcodebase>
php_admin_flag engine on
</Directory>
<VirtualHost ...>
...
Alias /t /usr/home/djw/src/wikipedia/phpwiki/newcodebase/
RewriteEngine On
RewriteRule ^/t/wiki/wiki.phtml(.*) /t/wiki.phtml$1
RewriteRule ^/t/wiki/(.*)$ /t/wiki.phtml?title=$1
RewriteRule ^/movie/(.*) http://us.imdb.com/Title?$1 [R]
RewriteRule ^/isbn/(.*) http://www.amazon.com/exec/obidos/ASIN/$1 [R]
...
</VirtualHost>
=== SNIP ===
Also, I would like to make the direct wiki.phtml URL unaccessable; I
want to force people to use the /t/wiki/* style URL, and not give out
any access at all to the /t/wiki.phtml?* URL's. Ideas?
Jonathan
--
Geek House Productions, Ltd.
Providing Unix & Internet Contracting and Consulting,
QA Testing, Technical Documentation, Systems Design & Implementation,
General Programming, E-commerce, Web & Mail Services since 1998
Phone: 604-435-1205
Email: djw(a)reactor-core.org
Webpage: http://reactor-core.org
Address: 2459 E 41st Ave, Vancouver, BC V5R2W2
I suggest that you add a line to create the wikidb database to the top
of buildusers.sql, like so:
CREATE DATABASE IF NOT EXISTS wikidb;
Just a convenience thing.
Also, could the INSTALL file explicitly say that buildusers.sql should
be run as a mysql user who has the power to create databases and grant
privileges, so typically you would run the script as the mysql (not
necessarily the system user) "root"?
Also, please insert the following in INSTALL file:
mysql -p --user=root < buildusers.sql
Cheers!
Jonathan
--
Geek House Productions, Ltd.
Providing Unix & Internet Contracting and Consulting,
QA Testing, Technical Documentation, Systems Design & Implementation,
General Programming, E-commerce, Web & Mail Services since 1998
Phone: 604-435-1205
Email: djw(a)reactor-core.org
Webpage: http://reactor-core.org
Address: 2459 E 41st Ave, Vancouver, BC V5R2W2
Since I'm not sure that anybody is minding the shop at SourceForge and I'm
certain that developers don't read the wiki-based feature request page, I'm
going to make a feature request here:
As it is, when Rambot is running Recent Changes is nearly useless since human
generated edits are drowned-out by a flood of automatic edits. Worse yet, is
that all these edits are displayed by default. A person has to create a user
account in order to use the 'hide minor edit' feature. I'm worried that when
Rambot is running that potential contributors looking at Recent Changes will
get the wrong idea about our project (and maybe leave before getting that
user account).
To combat this, I would like to suggest the creation of a new type of user
account that would just be used for bots. To have such an account the bot
owner would have to prove that their bot generates good articles, is not
harmful to performance (as Ram-Man has) and promise that the account would
only be used by the bot and would not be used for anything underhanded (like
violating policy by sneaking in POV edits -- I'm sure there will still be
people, like me, to sample bot edits to make sure nothing is going awry).
Then all edits made by the bot under a registered bot account could be marked
with a "B" in Recent Changes and would be not be displayed by default. As it
is, the 'hide minor edits' feature is useless for anybody worried about
vandalism since non-logged-in users can (for some reason that totally escapes
me) mark edits as minor. At the very least I wish 'mark this edit as minor'
would be disabled for non-logged-in users (as it was in a previous version of
the software).
-- Daniel Mayer (aka mav)
Hi,
I have noticed that google also have in his index the "talk:something" namespace and "user:something", "User talk:something" on the English and the Dutch wikipedia. The others i do not know.
And it also haves in his index the MetaWikipedia.
I find that google should not index our internall affairs. Only the aricles, nothing else. And that the MetaWikipedia is not especialy for the general public. I should also not be in the index of google.
Am I alone about this ?
Giskart
On Sunday 15 December 2002 12:00 pm, wikitech-l-request(a)wikipedia.org wrote:
> But before doing that; would it be more worthwhile to use some kind of
> event log table instead, from which the logs could be extracted through
> simple filtering? Or is using wiki pages which sysops can correct,
> rotate, and backup through the regular editing tools better?
>
> -- brion vibber (brion @ pobox.com)
Well it has been nice to be able to edit the logs. Both you and I have made
the logs more useful by adding header information, timestamps and links. I've
also been doing monthly archives of the deletion log and have been tracking
the the number of monthly edits (we are in a downward trend). So I favor the
current way of doing things.
BTW, would it be possible to make logs only appear once in Recent Changes
instead of appearing each and every time a file is uploaded or pages are
deleted? Many sysops often delete pages in chunks and many users upload files
in batches. This leads to the creation of a lot of noise in Recent Changes
(esp. for uploads since each upload generates two entries in RC). No biggie,
but if it can be done easily it would be nice.
--Daniel Mayer (aka mav)
I added a little hack to the Recent Changes page on test.wikipedia.org.
Not the nice one we talked about, but it could be expanded to that.
Please tell me what you think.
Note: I only had to patch Skin.php for that; it should show on all pages
that use the Recent Changes function, though. As a pure display
component, it shouldn't interfere with other new toys like "hide the
bots" ;-)
Magnus