I was updating modules for a site today and noticed that Sections does not have a 4.7 tag and therefore does not appear in the list of 4.7 projects. Since it does work with 4.7 it should be tagged as such.

Comments

Marc Bijl’s picture

It doesn't show up as 4.6 module either. As far as I know, it has always been a cvs version. As the readme.txt file says:

This module is currently under development and I am still figuring out how to make it perform better.
For example, the _init() hook is used, If we can find a method to incorporate this ins the menu, and thus using cahching etc, that would be very nice.
Also, the logic inside sections_in_section($section = NULL) is suboptimal. Anyonw with good pregmatch knowledge is welcome to improve it, so that we can avoid to pull all sections out of the DB every call.
Allthough it is built for 4.5, I will not release this module for 4.5 untill I have enough solid feedback, to call it stable.

Bèr Kessels’s picture

A few things:
* As noted, the code is suboptimal. We need to fix that before releasing.
* The module breaks with a lot of other modules that use a theme function early in the process. Event, tagnodes, etc all use theme(XYZ) functions in the menu or even in _init, this breaks the module.
* The UI is broken ATM, as well as some features that no longer work properly. This is minor, but needs to be fixed first.
* Blocks provide a nasty problem, because our blocks are per-theme.

ONLY if we have a bug-free (bugs issue queue < 1) will I tag this stable. I dont like releasing something that has known and confirmed bugs.

So feel free to assign and test bugs. Make patches, or test them. Together we can finish the module and release it.

Bèr Kessels’s picture

Status: Active » Closed (fixed)

closing this, since it is an too obvious "task". Only after fixing the last critical bugs we can release.