Last modified: 2010-05-15 15:38:16 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T4483, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 2483 - Special:Import needs to run link updates on created pages
Special:Import needs to run link updates on created pages
Product: MediaWiki
Classification: Unclassified
Special pages (Other open bugs)
All All
: Normal normal with 4 votes (vote)
: ---
Assigned To: Nobody - You can work on this!
: 3078 3320 4049 5769 (view as bug list)
Depends on:
Blocks: 606
  Show dependency treegraph
Reported: 2005-06-22 08:49 UTC by Brion Vibber
Modified: 2010-05-15 15:38 UTC (History)
4 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Description Brion Vibber 2005-06-22 08:49:30 UTC
Link table updates should be run on pages created via Special:Import.

Comment 1 Zigger 2005-08-08 22:55:29 UTC
*** Bug 3078 has been marked as a duplicate of this bug. ***
Comment 2 Marc Meurrens (be) 2005-08-09 06:22:12 UTC
// !FILE : SpecialImport.php
function importOldRevision() 
just before returning true, add :

  $article->editUpdates($article->preSaveTransform($this->getText())) ;
Comment 3 Marc Meurrens (be) 2005-08-09 06:25:01 UTC
I am not really sure the above 'preSaveTransform' stuff is really needed in this
but, it will not harm...
Comment 4 Marc Meurrens (be) 2005-08-10 13:25:31 UTC
In fact, my solution (above) solves the problem that imported articles were non
'searchable' but, until now, I did not find the way to automatically update 
a so-called 'indexing' within categories.

So, my solution is probably worth to be implemented as it solves half of the

But there is still job to realize the other steps :
- update categories
- and, but this is much less important, updating the list of recent changes, etc.

This is a really serious problem because, if we want to massively import data,
we need to make them available thru categories.

(In my case, I convinced ex-Windows victims to provide me with a stupid MS
Access file
including a few thousands of books descriptions, as to put them on a wiki, with
categories, keywords, images, comments, etc... 
it works really fine...
but they would also like to retrieve their books without the need to edit each
article manually :-) ...).
Comment 5 Rowan Collins [IMSoP] 2005-08-10 14:05:47 UTC
I once suggested, in a different context (bug 939, comment 3) adding a flag in
the database that causes a page's links to be re-processed the next time it was
rendered - in other words, next time it was viewed, since the cache would also
be purged at the same time. For Special:Import would probably make more sense to
just run an "updateLinks()" function (which we don't really have yet, AFAIK) at
the time of import, but I just thought I'd connect the thoughts.
Comment 6 Marc Meurrens (be) 2005-08-17 09:12:27 UTC
I solved my personal problem :

1) by patching SpecialImport.php as explained in comment 2
   (this immediately solves the 'search' part of the problem,
    so that we can see if and what was really uploaded)
2) by running the 'touch' (also named sometimes 'touchall') standard bot.
   (this solves the remainder parts of the problem)) 

However, it would be nice not to suggest the use of bot's.
a) because not everybody is able to run a bot
b) because, if everybody will start using bots, this can be very dangerous
   (for the contents and for the resources).

Comment 7 Brion Vibber 2005-08-31 01:20:21 UTC
*** Bug 3320 has been marked as a duplicate of this bug. ***
Comment 8 Zigger 2005-11-29 12:15:48 UTC
*** Bug 4049 has been marked as a duplicate of this bug. ***
Comment 9 Brion Vibber 2006-05-01 06:40:45 UTC
*** Bug 5769 has been marked as a duplicate of this bug. ***
Comment 10 Brion Vibber 2006-06-27 19:07:43 UTC
Fixed in r15096.

Note You need to log in before you can comment on or make changes to this bug.