Support » Plugin: WordPress Gallery Plugin - NextGEN Gallery » Desparately Needs a well documented and thorough API

  • For me a comprehensive API has to be has to be a top priority and that’s why I’ve marked an otherwise very good plugin down. The Galleries are all fine but you have to be able to customise the look and feel of a site and customising galleries is a key part of that.

    And the API needs good documentation. Hunting around, figuring out how to do stuff took a lot of time that I didn’t really have.

    The other reason I found myself building custom galleries was that they don’t support lazy loading which makes them slooow when you start increasing the image count. Galleries have to be fast.

    Otherwise, great plugin.

    • This topic was modified 3 years, 2 months ago by .
Viewing 4 replies - 1 through 4 (of 4 total)
  • There is API documentation within the plugin itself. So I’m assuming you mean public API documentation on the plugin website?

    There is? I’ve never been able to find it; Nextgen support themselves acknowledge that it’s virtually non-existant. Are we talking about the same thing?

    Plugin Author Imagely


    Hey @kimaldis !

    The documentation we have for our plugins is here:

    It is still a work in progress, but we have sufficient guided instruction on getting started with the plugin, what is possible, and how to create and insert galleries.

    Was there other documentation you were looking for?

    EDIT: I just realized you must have been referring to developer API exclusively. We have it written inline within the plugins code, see these screenshots:

    Our developers are working on building more documentation outside of the plugin that will go in more detail and be more simple to follow. Hopefully we’ll have that available soon. 🙂


    • This reply was modified 3 years, 2 months ago by Imagely.
    • This reply was modified 3 years, 2 months ago by Imagely.

    Yes, I was referring to the plugin code. I appreciate the in code documentation but digging around inside a code tree when you’re not sure where to look or even the precise name of what you’re looking for isn’t a great way of doing things. Basic stuff like getting a gallery, looping through image galleries, adding extra information to gallery displays; these are all tough to get information on.

    Custom galleries through templates; I really hope you’re going to be doing something about this because it seems half done and the end result, especially if you’re passing the result along to a client, seems kludgey and half done. Last time I dipped into this I ditched templates and built something based around an article by one of your guys, Benjamin, at Which now seems to be down, unfortunately. This was a useful article and a lot better but the levels of complication required to do something which ultimately isn’t that complicated – grab a gallery object, loop through its images – seemed excessive. I hope it hasn’t disappeared for good.

    We had a conversation here about custom galleries and documentation a few months ago, fwiw:

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Desparately Needs a well documented and thorough API’ is closed to new replies.