Magnus Manske wrote:
Maybe Tims recent file managing upgrade already has a solution for this, but if not, here's my 2 pennies (I'm in the UK now, after all:-)
- Make image pages movable (with the appropriate changes to the image table).
- Replace the "404 error: File not found" error message for
non-existant images with a script that checks if there's a REDIRECT page under that name in the database.
- Return the new image if this is the case, and return 404 if not.
This would be an improvement to the manual steps described above:
- MUCH easier and faster to do
- Preserves original upload/edit history
- Direct links to the image keep working
- No space waste due to deleted image
- Cost : an additional redirect page, and an SQL query for requests of
non-existing images
To turn off this behaviour for an image, simply delete the REDIRECT page.
(Seems so easy, I'm afraid I missed someting obvious at this point:-)
Magnus
I have also thought on this before. Some changes are that redirects are in page table, not on the image one. So the commons page table would need to be shared, too.
Then, our files are stored based on their filename, so either each page renaming means rename a lot of files, or we store in the image table the filename.