Is there any difference in following the download directions under "Usage" vs just download the extension from the distributor? The article talked about how the command line steps will prevent git metadata from downloading, but I see the same .git files in both.
Honestly I'm not too familiar with git and overwhelmed with how many files are inside the BoilerPlate extension.
No, I don't think there is. You just have to delete the `.git` directory, and re-init it as a new repository.
By the way, have you seen mwstew? It's pretty cool way to start a new extension.
Hello
I deployed the last version of BoilerPlate in Mediawiki 1.30.
https://github.com/wikimedia/mediawiki-extensions-BoilerPlate
I tested before to change your code... I have this error (the file exists on the disk)
| ( ! ) Fatal error: Uncaught Exception: /var/www/mediawiki/extensions/BoilerPlate/extension.json does not exist! in /var/www/mediawiki/includes/registration/ExtensionRegistry.php on line 99 | ||||
|---|---|---|---|---|
| ( ! ) Exception: /var/www/mediawiki/extensions/BoilerPlate/extension.json does not exist! in /var/www/mediawiki/includes/registration/ExtensionRegistry.php on line 99 | ||||
| Call Stack | ||||
| # | Time | Memory | Function | Location |
| 1 | 0.2007 | 360696 | {main}( ) | .../index.php:0 |
| 2 | 0.2009 | 361864 | require( '/var/www/mediawiki/includes/WebStart.php' ) | .../index.php:40 |
| 3 | 0.2045 | 748400 | require_once( '/var/www/mediawiki/LocalSettings.php' ) | .../WebStart.php:102 |
| 4 | 0.2051 | 875696 | wfLoadExtension( ) | .../LocalSettings.php:167 |
| 5 | 0.2051 | 875792 | ExtensionRegistry->queue( ) | .../GlobalFunctions.php:120 |
An idea ?
The Boilerplate extension is not meant to be installed, but rather to be copied as a starting point for the development of a new extension.
That said, there is an extension.json file in it, so perhaps you've got an older version of the extension?
I used cookiecutter https://github.com/JonasGroeger/cookiecutter-mediawiki-extension.git
With this version, it works.
Hello!
I'm the author of cookiecutter-mediawiki-extension and would like to merge this extension with my one, since my generator can generate this extension.
See Extension:Cookiecutter-mediawiki-extension
Then, further development could take place in one spot.
I've noticed various issues with the Boilerplate. For instance, ideally it should come packaged with a Gruntfile and PHPUnit/QUnit testing framework in place to make development easier. Keen to work on this but would like to manage these sort of tasks in Phabricator.
The tasks and bugs for this and Extension:Example are in Phabricator, project/tag #MediaWiki-extensions-Examples.
BoilerPlate now comes with a Gruntfile.js and has the standard npm test and composer test Continuous integration/Entry points. No actual PHPUnit, QUnit, or browser tests (phab:T108108) yet, patches welcome.