After upgrading to the 5.x-2.x-dev version of Subscriptions I noticed that mail for a particular content type was no longer being sent. I took a look at the Subscriptions tab on my user profile and noticed that there was an interval drop down that wasn't there before so I tried each of the settings. After each submit, the dropdown always reverts back to "Never."

That prompted my to look at the database tables for Subscriptions and here's what I've found. Looks like when you set and submit an interval it is actually is stored in the database but not reflected in the dropdown setting on the page. The other thing I noticed was that sid in the subscriptions table is now defaulting to zero. Old subscriptions from my last install retained a numerical sid but when I tried to update the interval or create a new subscription, it sets the sid to zero.

I can confirm that records are being created in the subscriptions_holding table however even after running cron there are no watchdog notifications that say mail was sent and I haven't received any updates. I tried uninstalling and reinstalling the module with the same results.

I'm running Drupal 5.1 on PHP 4 with mySQL 4.1.2. Please let me know if you have any ideas on how to resolve the issue or if you need more information.

Comments

salvis’s picture

salvis
he/his
commented

You are reporting two separate issues:

  • comboboxes on /subscriptions/type not being initialized
    This is an open TODO item.
  • mail not being sent
    I'm seeing this as well, but I haven't been able to find the cause for it yet — are you by any chance using an access module?
bittindm’s picture

bittindm commented

Thanks for the heads up on the to do item. I does look like it's posting the interval to the database so I'm guessing that's only a UI issue.

Regarding the mail sending issue, the only access control module installed in a home-grown Buddylist / ACL module that doesn't affect the particular content type that I'd like to use with subscriptions.

Are there any values I can check to make sure things are working as expected? After the upgrade, did I need to make any changes to cron or anything like that? It seems like new rows are created in subscriptions_holding for the content type I've subscribed to but the queue is not being checked and sent. Please let me know if you have any ideas about what's going on.

Thanks.

salvis’s picture

salvis
he/his
commented

Thanks for the heads up on the to do item. I does look like it's posting the interval to the database so I'm guessing that's only a UI issue

Right.

Regarding the mail sending issue, the only access control module installed in a home-grown Buddylist / ACL module that doesn't affect the particular content type that I'd like to use with subscriptions.

That's good news, in a way. chx thinks it's working pretty well, and we suspected that my problems might be due to my use of forum_access. If you have these problems without access control, it seems to be a more wide-spread issue.

Are there any values I can check to make sure things are working as expected? After the upgrade, did I need to make any changes to cron or anything like that?

No, I'm not aware of anything you could do.

It seems like new rows are created in subscriptions_holding for the content type I've subscribed to but the queue is not being checked and sent. Please let me know if you have any ideas about what's going on.

There is currently one known issue that could actually result in the opposite effect: records in subscriptions_holding disappearing without notifications being sent. chx will be working on that issue and turn over the cron-based code anyway, so there's not much use in digging deeper at this point.

Please keep in mind that -dev snapshots are not stable releases. They typically get better over time, and if you've already dared to jump to 5.x-2.x-dev, then I'd recommend updating when new ones become available, but -dev snapshots should not be used in production.

salvis’s picture

salvis
he/his
commented
Status: Active » Closed (fixed)

Subscriptions 2.0 has been rewritten from the ground up — I'm closing this issue because it refers to obsolete code that was removed.

If you'd like to take a first look and help with testing, then get it from the link on http://drupal.org/project/subscriptions, but do heed the warnings!

Please open new issues for feedback about the new version 2.0!