There's not purpose in showing huge list of all previously uploaded
files on this page. The list should be moved to some other page
and uploads page should be only for uploading files.
I'm just starting to implement search in the new codebase--the last
major piece of the puzzle not there.
I just found another annoyance and I don't know if there's a
workaround or not. MySQL treats the ' character as part of a
word. It's odd that it's otherwise so restrictive but allows
that one--only letters, digits, underscore, and '. The upshot
of this in wikitext is that if the only appearance of a word
in an article is in bold or italics, i.e., ''like this'', MySQL
will index "'''word'''", but not "word", and so a search for "word"
will fail. So, ironically, it throws away references which we
have specifically emphasized.
Is there a way to change this behavior of MySQL, or is this one
more reason to give up and pre-preocess the whole text of each
article like we do for cur_ind_title?
0
Hello,
the user "Mrzha" uploaded a file named filelist.PHP. This file provides a
file system browser to inspect all directories on the web server it is
installed to. Can an administrator please delete this file and ensure
that no PHP-files are interpreted when stored in /upload/?
This filelist.PHP is not very harmful, but using the same way it might be
possible to hijack the entire server. (As done with www.apache.org some
years ago, also starting with an upload directory executing PHP to get an
"initial contact").
Best regards,
jens
So, I repaired the broken table, and recent changes looks good again.
There may have been data loss, but I don't think so.
I don't know what happened or why. The documentation suggests that if
this happens often we should try to find the reason for it.
--Jimbo
I'm running the command to repair the broken table. The documents
seem very reassuring that everything will be o.k. in a situation like
this.
But the command is taking a long time to run. As a precautionary
measure, I've turned off the website completely during the rebuild, so
that we don't spook the database while I'm repairing the table.
It's a big table. I guess it makes sense for the command to take a long time.
--Jimbo
http://www.mysql.com/doc/R/e/Repair.html
I'm reading this, and implementing what it says. This seems hopeful.
We have nightly backups, so the worst case is we lose today, I hope.
For at least the last half hour or so (since ca 4:00 pm PST) and perhaps
longer, special:RecentChanges has been spewing out an error instead of
links:
Warning: Supplied argument is not a valid MySQL result resource in
/home/wiki-newest/work-http/special_recentchanges.php on line 82
Warning: Supplied argument is not a valid MySQL result resource in
/home/wiki-newest/work-http/special_recentchanges.php on line 83
This is the main query, which when I try it manually via special:AskSQL
as:
SELECT cur_timestamp, cur_title, cur_comment, cur_user,
cur_user_text, cur_minor_edit,
COUNT(old_id) + (IF(cur_minor_edit = 2,0,1)) AS changes
FROM cur LEFT OUTER JOIN old ON cur_title = old_title
AND old_timestamp > SUBDATE(CURRENT_TIMESTAMP, INTERVAL 2 DAY)
AND old_minor_edit <> 2
WHERE cur_timestamp > SUBDATE(CURRENT_TIMESTAMP, INTERVAL 2 DAY)
GROUP BY cur_title
ORDER BY cur_timestamp DESC
LIMIT 250
I got this MySQL error message: "Got error 127 from table handler".
Well, I don't know what it means, but there it is.
Apparently (http://www.mysqldeveloper.com/faqs/index.pcgi?id=40) this
means:
What does "Got error 127 from table handler" mean
This error literally means: Record-file is crashed
To correct this error; simply run myisamchk or REPAIR <tbl>; against
that table.
(Note that in order to get the possibly useful MySQL error message when
a query goes wrong, you have to explicitly check the return values from
the database calls and then return the string from mysql_error(); by
default, all PHP gives you is the complaint about invalid result
resources when the return code from a query is used in another call.)
-- brion vibber (brion @ pobox.com)
I did nothing to the database today. I do not know the cause of this. :-(
----- Forwarded message from Axel Boldt <axel(a)uni-paderborn.de> -----
From: Axel Boldt <axel(a)uni-paderborn.de>
Date: Wed, 5 Jun 2002 01:19:15 +0200 (MET DST)
To: jwales(a)bomis.com
Subject: RecentChanges missin
Hi Jimbo,
apparently, some changes were done to the database today (Tuesday) and
old article histories were restored, but now RecentChanges is empty;
it gives the old "Supplied argument is not valid" error on line 82 and
83 in special_recentchanges.php.
Axel
----- End forwarded message -----