Installed 6.x-4.0-beta4 Messaging and Notifications modules (2010-May-11) and went bug hunting. (They're hard to find!)

However, found one when altering existing subscriptions in both 'My Account' and 'Administer Subscriptions'

Process:
1. In My Account/Notifications/Subscriptions, I select edit link for an existing Custom Subscription that I'm already subscribed to.
2. The Edit subscription form opens and I change 'send method' and 'send interval' values and click save.
3. After save, I'm returned to My Account/Notifications/Subscription however values for both fields haven't altered.

* The same steps, but in Administer/Messaging & Notifications/Manage Subscriptions also do not update the subscription.

* Editing individual Node subscriptions that already exist in the same way does update correctly with both fields changing.

Comments

jose reyero’s picture

jose reyero commented
Status: Active » Fixed

Thanks for the report. The issue should be already fixed (I think today with some other issue).

Btw, just released Beta5, bug hunters wanted :-)

Anonymous’s picture

Anonymous (not verified) commented

In Beta5, I tried the same procedure as originally listed.

I can confirm that changing [send method] and/or [send interval] does not save the new selections in 'My Account' or 'Administer/Messaging & Notifications/Manage Subscriptions'

I now see a message (green) "You are not allowed to create this type of subscription."

Is this by design? As far as I can see, you do not set [send method] or [send interval] when creating a new custom subscription.

Rick :)

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

kswan’s picture

kswan commented
Version: 6.x-4.0-beta4 » 6.x-4.0-beta6
Status: Closed (fixed) » Active

The behavior described in #2 still occurs in beta6.

jose reyero’s picture

jose reyero commented
Status: Active » Fixed

Opps, I had missed the 'custom subscription' detail.

I've tried and was getting an 'access denied' message for custom subscriptions ("You are not allowed to create that.."). Fixed with latest commit, along with some improvements to access check

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.