"Import file" gives "Internal error"
Status: Beta
Brought to you by:
worden
Clicking "Import file" gives the following error:
Call to undefined method SkinMonoBook::tooltipAndAccesskeyBacktrace:#0 /var/www/mw/extensions/WorkingWiki/SpecialCustomUpload.php(267): Skin->__call('tooltipAndAcces...', Array)
#1 /var/www/mw/extensions/WorkingWiki/SpecialCustomUpload.php(267): SkinMonoBook->tooltipAndAccesskey('upload')
#2 /var/www/mw/extensions/WorkingWiki/SpecialImportProjectFiles.php(294): CustomUploadForm->execute()
#3 /var/www/mw/includes/SpecialPageFactory.php(471): SpecialImportProjectFiles->execute(NULL)
#4 /var/www/mw/includes/Wiki.php(222): SpecialPageFactory::executePath(Object(Title), Object(RequestContext))
#5 /var/www/mw/includes/Wiki.php(622): MediaWiki->performRequest()
#6 /var/www/mw/includes/Wiki.php(529): MediaWiki->main()
#7 /var/www/mw/index.php(58): MediaWiki->run()
#8 {main}
Anonymous
This severely affects usability by some.
I guess this is on MW trunk? I can't guarantee compatibility with the trunk code as its authors are continually changing their classes' APIs.
Yes, it is on MW trunk. I will try downgrading. What is the recommended course for using MW trunk? To not use it? Do you, anywhere?
Well, still works on revision 87501, but not much later than that.
MediaWiki doesn't recommend using trunk for any wiki that you rely on, because it can break at any time. So the fact that it can break WorkingWiki at any time is just more of the same. Their recommendation is to use the latest stable release, which is currently 1.17.
That said, they are good about marking function and method calls deprecated one or two releases before they actually remove them, so in theory I should be able to avoid things like this. In practice I haven't had the time to keep up with the deprecations. Also, because lalashan is still running MediaWiki 1.13 I am challenged by trying to support a big range of incompatible versions. I predict that when we get off of 1.13 and onto something more recent (when we migrate our wikis to the yushan cluster, which we are looking forward to) I'll be better able to support the new versions.
I want to support what the actual users want, which is us, you, and Weitz's lab as far as I know. So if you have reason to want to stay on trunk I'll do my best. But are there in fact features on trunk that you need, in contrast to running 1.17?
Er, the way I remembered it was that you recommended moving to trunk. Maybe I made that up.
-p
The new ImportProjectFiles ([#299]) addresses this problem (and it works on MW trunk, at least at the time of this comment).
Related
Bugs:
#299