Fork me on GitHub

Postnuke API Development  Bottom

  • I was wondering if anyone has had any thoughts regarding further developments of the PN API, such as methods for registering/remving users, adding groups, creating permissions, adding/removing blocks and modules, etc.

    I would be happy to develop these myself, as they are much needed for the project I am working on, and would make my module installations (which are quite complex applications) simpler.

    I think these are much needed additions. Has anyone done any work in this direction, or had any thoughts about these issues? How can I contribute *core* PN code which extends the API?

    Jon Acker.
  • Don't cross post, a topic need only be handled in one place. If your initial post is in the wrong place, we will move it to the right one.

    These functions do not need to be part of the API, they are part of their own modules, and can be called by any other module by using the pnModLoad (i think it is) and pnModLoadAPI or soemthing like that.

    --
    Home Page | Find on Facebook | Follow on Twitter
  • Any API functions you do write may be incorporated into the core - if you think it is appropriate, you can always submit patches to the NOC and they will be reviewed by developers

    --
    itbegins.co.uk - Zikula Consulting

    birtwistle.me.uk - Personal Blog


    Please read the Support Guide
  • I don't these these kind of things are warrented as core apis. As Michael has said the API's from modules can be called directly using pnModAPIFunc. The blocks, permissions and modules modules are already API based so can be called from other modules. Groups and users aren't as yet but will be for .8x.

    -Mark

    --
    Visit My homepage and Zikula themes.
  • Sort of related: With the core finally being stripped down to the bare essentials (Just what it takes to run the API and interface with the DB) and so many important functions being contained in modules, has there been any considerations to a dependency system? It wouldn't have to be anything huge, just each version.php file or whatever could contain module depdendencies (would just be the neccesary module's name and minimum version number) and perhaps a mandatory flag for dependencies that are absolutely needed (lack of others would just make warnings).
  • <shameless plug="plug">pnGroups is API based

    --
    Home Page | Find on Facebook | Follow on Twitter
    </shameless>

This list is based on users active over the last 60 minutes.