Nodequeue

In your hook_install() and/or hook_update_N() implementation, this sort of code will create a new nodequeue (if it already exists, you'll only get database errors, though this could be worked around with a bit more code if for some reason you couldn't rely on what the site you are updating has or not).

Putting some configuration in code: creating subqueues for nodequeues in code.

rather than forcing our client to create a new nodequeue for each competition (which are nodes themselves) we'd have a single queue with subqueues for each competition. This approach, using subqueues, has several advantages, among which is that it makes it stupidly easy to build a single view that takes a competition node id as an argument for which subqueue to show.

Search

Search this site:

Agaric?

Agaric makes powerful web sites for people who do things. As a collective of skilled workers, Agaric collaborates with you and open source free software communities to develop tools and build platforms that meet your needs.
How we can help you? Please ask Agaric!