Hi,
I'm currently fiddling with the importUseMod-script for migrating a wiki and have implemented a functionality for replacing CamelCase notation with "correct fluent text". Along this I also took the opportunity to insert appropriate [[Category:...]] and {{...}} lines into the respective SQL statements in varying numbers. After running the import SQL those insertions are available in the plain article text and displayed/executed correctly, but they are not subject to search and "Specialpages:Category" links.
Example: The lines [[Category:Glossary]] and {{revise}} are part of a large number of articles. The category list at the bottom of the page is displayed correctly and if the Article "Template:revise" exists, its content is included correctly. But when clicking the category name or performing a text search on "revise", there is nothing returned. This changes when a respective article is once opened for edit and saved immediately after (or doing actual changes). Then this article is availabe in the category listing and comes up as a search result.
Of course I can see that this is due to the missing information in the categorylinks and searchindex tables which is obviously created/updated when saving an article.
Now for the question after all: Opening and just saving ~1000 articles for the sake of indexing categories and search may be an honourable task, but an eternal one as well -
Is there a function/script/trick to run once and after that the categories and searchindexes would be up to date? No problem if this takes a while.
Greetings Philipp
On Dec 22, 2004, at 2:07 AM, Philipp wrote:
Is there a function/script/trick to run once and after that the categories and searchindexes would be up to date? No problem if this takes a while.
rebuildall.php
-- brion vibber (brion @ pobox.com)
Brion Vibber <brion <at> pobox.com> writes:
rebuildall.php
Thank you so far (could have looked there for myself ...), but I'm still running into problems. I apologize for maybe being a blockhead here, I did the following: being in Mediawiki-homedir (...../mediawiki/):
Add/Edit lines in AdminSettings.php:
$wgDBadminuser = "root"; $wgDBadminpassword = "XXXXX"; $wgDBname = "wikidb";
(BTW, I'm not mixing up system and DB accounts here, the DB admin user account *is* named "root", its password is not "XXXXX" but the correct one and the DB is called "wikidb". Giving a ... mysql -uroot -pXXXXX wikidb ... brings me perfectly to the DB commandline.)
Change to maintenance/ and running the script ...
php -f ./rebuildall.php
... gives me:
"Konnte keine Verbindung zur Datenbank auf Access denied for user: 'root@localhost' (Using password: YES) herstellen."
[part German for "Couldn't connect to database at Access denied for user: 'root@localhost' (Using password: YES)."]
which is obviously the concat of two error messages ("Couldn't connect to database at ..." coming from some PHP DB library(?) and "Access denied ... (YES)." coming from mysql which is the usual error message when the PW doesn't match the username).
Maybe I'm a bit blockheaded here, but what's the mistake?
Hello, Philipp! You wrote on Wed, 22 Dec 2004 14:47:02 +0000 (UTC):
P> Change to maintenance/ and running the script ...
P> php -f ./rebuildall.php
P> ... gives me:
P> "Konnte keine Verbindung zur Datenbank auf Access denied for user: P> 'root@localhost' (Using password: YES) herstellen."
P> [part German for "Couldn't connect to database at Access denied for user: P> 'root@localhost' (Using password: YES)."]
P> which is obviously the concat of two error messages ("Couldn't connect to P> database at ..." coming from some PHP DB library(?) and "Access denied ... P> (YES)." coming from mysql which is the usual error message when the PW doesn't P> match the username).
Which version of mediawiki you are using?
-- God speed
On Dec 22, 2004, at 11:47 PM, Philipp wrote:
SpeedyGonsales <stemd <at> gmx.net> writes:
Which version of mediawiki you are using?
1.3.3
Please upgrade to 1.3.9 immediately; there are a number of important security fixes in the versions since 1.3.3.
-- brion vibber (brion @ pobox.com)
Hi,
Brion Vibber <brion <at> pobox.com> writes:
Please upgrade to 1.3.9 immediately; there are a number of important security fixes in the versions since 1.3.3.
I know, but since this is an entirely nonpublic, strongly firewalled intranet wiki used only by trustable personnel, that would be secondary concern. Surely to be done soon anyway but currently the tasks and problems mentioned above are on top of the list. Does 1.3.9 do improvements and solutions in that regard?
Greetings Philipp
"Philipp" wikilist-1@e-something.de wrote in message news:loom.20041223T090724-902@post.gmane.org...
Hi,
Brion Vibber <brion <at> pobox.com> writes:
Please upgrade to 1.3.9 immediately; there are a number of important security fixes in the versions since 1.3.3.
I know, but since this is an entirely nonpublic, strongly firewalled intranet wiki used only by trustable personnel, that would be secondary concern. Surely to be done soon anyway but currently the tasks and problems mentioned above are on top of the list. Does 1.3.9 do improvements and solutions in that regard?
I installed 1.4beta3 because of its support for Special:Allmessages listing by namespaces, and only thing required to do php rebuildall.php was to set user, pass and dbname in AdminSettings.php, and everything worked without problem.
If you don't have time to upgrade, I would suggest that you debug php connection to db, like using:
error_log( "Is it working" , 0 );
in adequate places and such, besause you wrote that connection to db from prompt is working, maybe something is broken with php....
HTH
-- God speed
wikitech-l@lists.wikimedia.org