Hi all
Quick question, is there any downside to doing this: wfLoadExtension('Foo/Bar'); ? It loads the extension and the extension works as expected.
I wrote an extension for a project which another developer(s) set up with custom extensions outside of the public www directory. They symlinked this custom directory back to the public extension directory but all custom extension are in their own directory. So /extensions has standard MW extensions and /extensions/Foo contains all the custom extensions. All of the custom extensions are called with require_once '$IP/extensions/Foo/Bar01/Bar01.php" and so on. I know you can't do the standard double entry method with a deprecated message unless you use the "Foo/Bar" in the wfLoadExtension statement with the custom ones.
wfLoadExtension('Foo/Bar'); works but going forward I wonder about any long term issues. Wiki is on 1.27 but worry about long term problems as the other custom extensions are improved to use wfLoadExtension. There would be multiple extensions which would require this type of call, Foo/Bar, Foo/Bar1, Foo/Bar2, etc.
Thanks
Tom
Hi!
If I haven't misunderstood you, it's totally fine doing this. In fact, ConfirmEdit uses this similar approach to load different CAPTCHA modules.
Best, Florian
-----Original-Nachricht----- Betreff: [MediaWiki-l] wfLoadExtension Registration Datum: 2017-04-24T14:51:51+0200 Von: "Tom Hutchison" tom@hutch4.us An: "MediaWiki-l" mediawiki-l@lists.wikimedia.org
Hi all
Quick question, is there any downside to doing this: wfLoadExtension('Foo/Bar'); ? It loads the extension and the extension works as expected.
I wrote an extension for a project which another developer(s) set up with custom extensions outside of the public www directory. They symlinked this custom directory back to the public extension directory but all custom extension are in their own directory. So /extensions has standard MW extensions and /extensions/Foo contains all the custom extensions. All of the custom extensions are called with require_once '$IP/extensions/Foo/Bar01/Bar01.php" and so on. I know you can't do the standard double entry method with a deprecated message unless you use the "Foo/Bar" in the wfLoadExtension statement with the custom ones.
wfLoadExtension('Foo/Bar'); works but going forward I wonder about any long term issues. Wiki is on 1.27 but worry about long term problems as the other custom extensions are improved to use wfLoadExtension. There would be multiple extensions which would require this type of call, Foo/Bar, Foo/Bar1, Foo/Bar2, etc.
Thanks
Tom
_______________________________________________ MediaWiki-l mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
Thanks Florian, I'll take a look at ConfirmEdit. Personally, I would have the symlinks put the outside the root custom /extensions into the public www location of /extensions and not have bundled them all together into a custom subdirectory in the /extensions directory. I can't see the benefit because the custom ones are bundled together anyway outside the public root location. I think that's a recommendation I'll make for long term. Tom
-----Original Message----- From: MediaWiki-l [mailto:mediawiki-l-bounces@lists.wikimedia.org] On Behalf Of Florian Schmidt Sent: Monday, April 24, 2017 9:18 AM To: MediaWiki announcements and site admin list mediawiki-l@lists.wikimedia.org Subject: Re: [MediaWiki-l] wfLoadExtension Registration
Hi!
If I haven't misunderstood you, it's totally fine doing this. In fact, ConfirmEdit uses this similar approach to load different CAPTCHA modules.
Best, Florian
mediawiki-l@lists.wikimedia.org