Last modified: 2009-09-19 20:52:16 UTC
BUG MIGRATED FROM SOURCEFORGE http://sourceforge.net/tracker/index.php?func=detail&aid=989761&group_id=34373&atid=411192 Originally submitted by Matthew Brown (morven) 2004-07-12 23:39 If you enter text in an image description when uploading an image, and one puts links in that text, the links do not update 'what links here' on the target pages. The Image: page thus created is not placed on the user's watchlist even if they have 'watch pages I edit' checked in preferences. ------------------------- Additional comments ------------------------ Date: 2004-07-28 17:33 Sender: nobody Logged In: NO related to this i expect is the fact external Links entered in an image description are not flagged as such with the ususal logo indicating they are external links.
*** Bug 92 has been marked as a duplicate of this bug. ***
*** Bug 297 has been marked as a duplicate of this bug. ***
*** Bug 771 has been marked as a duplicate of this bug. ***
From bug 771: When a new image or other file is uploaded, the image description page is not put in the search database, causing the image to be unfindable for search unless it is uploaded.
That comment on 771 is from me, and I made an error in it. The last word should be "edited" rather than "uploaded".
*** Bug 1048 has been marked as a duplicate of this bug. ***
*** Bug 1508 has been marked as a duplicate of this bug. ***
*** Bug 1595 has been marked as a duplicate of this bug. ***
To make sure that people who search for it find this bug: This bug affects links to categories (as well as other things). If you use the category tag in the upload summary to describe a file, or a template that has a category tag, then although it appears to be placed in the appropriate category, it is not.
It nearly works - only the sorting isn't done properly, see eg. [[:commons:Category:Maps of Chiang Rai]]. The new images without manual edit show up at the end of the category, and only get sorted to their place after the dummy edit. But definitely an improvement already.
This should now be fixed in HEAD and REL1_4 (applied on the live site).
*** Bug 2258 has been marked as a duplicate of this bug. ***
