Everyone interested in this, first of all -- sorry. I wasted months trying to fix the old codebase. Now, there is a new approach... from the ground up. The code is blasted apart into small component modules: there is a module which queues the objects, there is an UI module so you can subscribe to things and there is a module which sends mails out of the queue on cron. This way, you can change the UI easily for something that fits your site better or you can use mailman or even SMS as the sender backend.

The subscriptions model is totally new: you can subscribe to a field owned by a module, for example 'type' owned by 'node'. You can restrict a subscription to stuff written by one author. These two together supersedes the old 'node type' and the 'blog' subscriptions. 'tid' (owned by node, of course) subscriptions are a bit more tricky because there is no tid in node table but as you can specify a handler function for your field, this kind is covered, too. Even these default subscriptions might be moved into separate modules. I think I love small modules :)

When an object, for example, a node, gets in the queue, it is represented by its load function and the relevant arguments. For example, node_load and 123 if there is a comment on node 123. There is now an access check but it's untested yet.

Another popular request is adding an option for comments -- ie. if I am subscribed to a term and there is a node under it, and someone comments, do I get a mail or not? I believe that this will be a user level setting, it would terribly complicate things if it would be subscriptions level.

The new stuff is accessible in my SVN repo without a password at https://4si.devguard.com/svn/public/ -- currently it's only useful for developers as it's rather raw, there is no install (but there is a mysql dump). Expect an alpha in weeks not months: Jose Reyero and myself are going to work on this heavily.

Commenting on this Story is closed.