Jason: The SQL for updating the cache is
UPDATE cur SET cur_cache="",cur_timestamp=cur_timestamp
as Brion mailed earlier. Please run that one.
Jimbo: The scipt that rebuilds the links is in the CVS. You probably checked it out already. I think it is called "rebuildLinks.php" or something similar... This will run several minutes! *Maybe* you should take the site offline for that, so the database doesn't get cunfused between user edits and that script.
What I said baout the Recent Changes is about the header ("Track the most recent changes..."), *not* the list of recent changes! It is a brief text, but it is loaded quite often, and each time, the database is checked for all those links in that text.
That's it for now, Magnus
On dim, 2002-05-12 at 12:09, Magnus Manske wrote:
Jimbo: The scipt that rebuilds the links is in the CVS. You probably checked it out already. I think it is called "rebuildLinks.php" or something similar... This will run several minutes! *Maybe* you should take the site offline for that, so the database doesn't get cunfused between user edits and that script.
Note also that it probably will fail, since there seems to be some actual trouble accessing the "unlinked" table in the database, so the script will just be pumping links into a black hole. :(
Unfortunately, I don't know what's really wrong there or how to fix it; the most descriptive error message I've managed to get claims "cannot open file: 'unlinked.MYD'"; Jason says the file does in fact exist, which implies that it is likely corrupted. Error logs on the server may be more helpful in diagnosing the problemo; also try "myisamchk" or other tools for possible recovery.
However, the data in the "linked" and "unlinked" tables can, if need be, be tossed away and regenerated via the script if the tables are recreated successfully. (See the table setup commands in wikipedia.sql.)
-- brion vibber (brion @ pobox.com)
Done.
mysql> UPDATE cur SET cur_cache="",cur_timestamp=cur_timestamp; Query OK, 50142 rows affected (44.27 sec) Rows matched: 50759 Changed: 50142 Warnings: 0
Jason
Magnus Manske wrote:
Jason: The SQL for updating the cache is
UPDATE cur SET cur_cache="",cur_timestamp=cur_timestamp
On lun, 2002-05-13 at 10:00, Jason Richey wrote:
Done.
mysql> UPDATE cur SET cur_cache="",cur_timestamp=cur_timestamp; Query OK, 50142 rows affected (44.27 sec) Rows matched: 50759 Changed: 50142 Warnings: 0
Huge thanks, Jason!
If at some point we can get the software upgraded to the CVS version, we can also fix these problems:
(Major problems fixed in CVS) * old page versions overwrite the cache when viewed * no Talk page links * special:Watchlist grinds the database to unusable levels * (possibly) pages spontaneously appearing empty
(Less severe, but darned annoying problems fixed in CVS) * some inter-language links broken * recent changes only bolds certain watchlist items * wrong link colors and other style issues * buggy experimental auto-wikification feature too "in-your-face" others ?
(Assuming the code is otherwise in a usable state. It hasn't exploded on me recently.)
-- brion vibber (brion @ pobox.com)
Done. Yikes.
Fatal error: Cannot instantiate non-existent class: skinstandard in /home/wiki-newest/work-http/wikiPage.php on line 1131
Site down for the moment, probably I can fix it in moments.
Brion L. VIBBER wrote:
On lun, 2002-05-13 at 10:00, Jason Richey wrote:
Done.
mysql> UPDATE cur SET cur_cache="",cur_timestamp=cur_timestamp; Query OK, 50142 rows affected (44.27 sec) Rows matched: 50759 Changed: 50142 Warnings: 0
Huge thanks, Jason!
If at some point we can get the software upgraded to the CVS version, we can also fix these problems:
(Major problems fixed in CVS)
- old page versions overwrite the cache when viewed
- no Talk page links
- special:Watchlist grinds the database to unusable levels
- (possibly) pages spontaneously appearing empty
(Less severe, but darned annoying problems fixed in CVS)
- some inter-language links broken
- recent changes only bolds certain watchlist items
- wrong link colors and other style issues
- buggy experimental auto-wikification feature too "in-your-face"
others ?
(Assuming the code is otherwise in a usable state. It hasn't exploded on me recently.)
-- brion vibber (brion @ pobox.com)
Wikitech-l mailing list Wikitech-l@ross.bomis.com http://ross.bomis.com/mailman/listinfo/wikitech-l
wikitech-l@lists.wikimedia.org