Special:ImportProjectFiles needs to be updated for MW1.19 and similar.
There may be multiple things to do with it.
One is just to rewrite S:IPF compatible with the current MW, using the current Special:Upload as a basis. If I remember right, the current Special:Upload is actually written as a set of classes designed to be subclassed in just the ways we need to -- which is what was missing from the old Special:Upload that made me need to use a rewritten version of it.
But then there would also be great advantages to using the UploadWizard interface, which is an existing tool that guides you through uploading multiple files, saying what they are, and making sure everything makes sense before committing them to the wiki.
So I should look into both, and probably do them in that order.
Anonymous
Let's do adapting to current Special:Upload at [#242], and open a separate ticket for UploadWizard when the time comes.
Related
Bugs:
#242Last edit: Lee Worden 2013-05-14
There are really two different tasks:
Maybe I should do a customized SpecialUpload that imports a single file to WW, and a customized UploadWizard that imports multiple files to WW.
I should install the UploadWizard extension and look it over.
I'm probably not understanding; and I'm just commenting, not voting. But it looks to me like our main goal should be to work with the latest LTS version.
Depends what you mean by 'work with': if I get the forthcoming
VisualEditor to work with WW, people will want to use it on lalashan,
and that will probably require us to upgrade to 1.21 or whichever. But
I think WW should definitely SUPPORT the LTS version, to be usable by
other people.
On 02/15/2013 11:19 AM, Jonathan Dushoff wrote:
See https://sourceforge.net/p/workingwiki/bugs/268/ - an import page bug. Make sure the new version doesn't inherit it.
just created http://lalashan.mcmaster.ca/theobio/projects/index.php/WorkingWiki/Developer_Documentation/Import_interface to inventory what is going on in SpecialUpload, SpecialCustomUpload, and whatever I will need to use now.
There are several existing IPF bugs to keep track of in this rewrite, including a new report, http://sourceforge.net/p/workingwiki/bugs/269/.
I had written in https://sourceforge.net/p/workingwiki/bugs/180/ that it's not worth troubleshooting the existing code because it's such a mess it's better to replace it. But I'll use the existing code as a model for the new code, which means I'll be reviewing how it's written, which is most of the work of debugging. And it occurs to me that flushing out the known bugs is as good a way of reacquainting myself with the code as any. Which means I don't have an excuse for not fixing the bugs, since fixing them now would be better for usability.
Have been going after some bugs in the old S:IPF, and it's been useful (and hopefully useful for some users as well), but I guess if I'm going to get this done I'd better get back to the rewrite...
Argh this is so painful!!!
I've been working with the MultiUpload extension as a base for our import interface (for anyone who hasn't been following the gory details on the projects wiki - here and here), but now I'm convinced that it doesn't make sense to use MultiUpload because it's too full of bugs, which it would take a lot of work to understand and fix.
Which means I'm back to writing a multiple-upload interface myself, as well as code to upload into WW rather than the standard File: destinations.
Or, as JD suggested, doing a lighter-weight approach, where you enter the data using ManageProject and then do some kind of simple upload step to provide the files.
Created [#299] for creation of a new Special:MultiUpload and Special:ImportProjectFiles derived from it.
Related
Bugs:
#299Closing. The action is in [#299].
Related
Bugs:
#299