Support Forum

Hey all I am working on a new module and I wanted to know if I really have to have the adminapi fucntions, the reason I ask is that the module will have no configuration and the administration will be handled on a user by user basis through the permissions system so do I have to have this is it maditory??



Thanks
-SUNADMN

Sounds to me like you don't need it. I have it so that I have the link in the admin menu, so that I can get to it there if I want to, and so that, if I add stuff later configuration-wise I can get to it. However, if you change the variable in the version file saying it's got an admin option, then you're fine, I would think.

Groovy jedi that's what I thought but wanted to make sure before I messed things up.



Thanks
-SUNADMN

Worst case scenario is you have to go back in and write the admin stuff after the fact, not likely to hurt anything.. I do like jedi on PrayerPost, pretty much the only thing in the Admin functions is to let me see it. I think I ended up with the remove function being the only admin power.

For consistencies sake it may be worth keeping the modifyconfig/updateconfig functions. If your working from .750 example module then there's no point. But in the .760 version some new hook types have been added. These are modifyconfig/updateconfig hooks. These hooks allow additional options to be added to the modifyconfig page of a module by other modules.

Also where possible key the user API's consistently named; get to get an item, getall to get a set of items etc.

-Mark

Great guys thanks so much for the answers I will keep to the naming conventions in my development for sure, it seems to help with confucion on what does what.



Thanks
-SUNADMN