Last modified: 2006-03-11 00:28:22 UTC
This should say all:
Legende: (aktuell) = dies ist das aktuelle Bild, (Löschen) = lösche diese alte
Version, (Zurücksetzen) = verwende wieder diese alte Version.
* (Löschen) (Aktuell) 23:59, 31. Dez 1969 . . ( Byte)
Picture got uploaded August 18th 2004.
Applied patch: Don't show the list of image versions if there are no image
versions in the DB.
Open question: Why is there no DB entry for this image?
Well I do not know "Why is there no DB entry for this image?" I would not have
asked in the first place If I knew that ;-)
Now there is no information at all in the image (meaning time, date and size).
Not even the possibility for a sysop to delete the image exists.
But that is another "bug" which I have not submitted yet. Maybe it is a feature
though which nobody wants. This is not solved yet. The tab "löschen" on top of
the page on the right merely deletes the article but not the picture. I have not
figured the use of that though. Only if one klicks on the "(Löschen)"
underneath the picture the image is really erased.
The delete tab at the top deletes the article, the current revision and all old
Are there any new cases of this? If not, I would like to fix that one page and
close the bug.
Fixed DB. Bug closed since apparently no other cases have been observed.
I've encountered the same bug. The empty link was caused by the creation of a sound file which started with a double-quote character.
I've increased the severity to major, as there could be a security hole here (file access? XSS?).
This bug was encountered on a wiki running Version 1.3.5.
The image file does not exist on the server, but as it is listed in Special:Imagelist, I guess it does exist in the database.
What would I need to do to ensure the database is OK? (I've got shell access on the machine on which this wiki is running).
Deleting from the web interface won't work.
(In reply to comment #7)
> I've encountered the same bug. The empty link was caused by the creation of a sound file which started with a double-
Are you sure this is the same problem? That sounds like an unrelated HTML output issue (please install 1.3.6 and make sure
it's working right now, we've cleaned up a lot of these.)
Oops... I reopened the wrong bug, didn't I? Closing again.
Anyhow, as to your (way) earlier question, the bug does indeed seem to be gone.