Thanks for this thread, Please do commit fixes for 1.17, If not obvious already I have really only been targeting trunk. While the extension has been around since before 1.16, it would be very complicated to restore the custom resource loader it was using before there was a resource loader in core.
In terms of Superpurge, that is essentially what we do with the "transcode status table" on the image page that lets users with the given permission purge the transcodes. We did not want to make it too too easy to purge transcodes cuz once purged a video could be inaccessible for devices / browsers that only had webm or only had ogg support, until the file was retranscoded. --michael On 07/11/2011 04:48 AM, Dmitriy Sintsov wrote: > Yes, locally patched both issues, now runs fine. > $wgExcludeFromThumbnailPurge is not defined in 1.17, made a check. BTW, > it is a bit evil to exclude some extensions from Purge. Maybe there > should be another action "Superpurge"? > > Linker::link() was called statically in TranscodeStatusTable class. > Created new Linker() and now it works. I haven't committed into svn, > don't know if anyone cares of backcompatibility. > > BTW, if I'd was an leading developer (who makes decisions), I'd probably > make MW 1.16 an LTS (long time support) version for legacy setups and > extensions.. Though maybe that is unneeded (too much of burden for > non-profit organization). > > Dmitriy > > _______________________________________________ > Wikitech-l mailing list > Wikitech-l@lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/wikitech-l _______________________________________________ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
