Last modified: 2013-02-03 11:01:09 UTC
The extension defined a new module geopagesincategory, but that is not listed on the api auto doc and does not exist. Instead of duplicate the existing api module, the extension should hook into the existing module and add it parameters. * APIGetAllowedParams * APIGetParamDescription * APIGetResultProperties At the begin, you have to use the following, if not, you will modify all modules: if ( !$module instanceof ApiCategoryMembers ) { return true; }
geopages and geopagesincategory are currently intentionally disabled on WMF sites due to product goal changes. Extending the existing modules via hooks is indeed a more sane way, however in this particular case it's impossible because it requires access to some protected ApiQueryBase functions.
Overridding the select method looks not like the best way to implement a (new) module, there are other ways to reach this. Have a look at other extensions with api modules. Yes, that would result in a extra query from this module, but having the same modules for a little benefit is bad style. Maybe ask some of the api developer.
