Changes between Initial Version and Version 1 of Ticket #11090, comment 15


Ignore:
Timestamp:
Aug 16, 2013 7:51:02 AM (11 months ago)
Author:
rjollos
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #11090, comment 15

    initial v1  
    11Replying to [comment:14 anonymous]: 
    2 > Execuse me, I stumbled uppon this again and noticed changeset 13290. 
     2> Execuse me, I stumbled uppon this again and noticed changeset [13290]. 
    33Welcome. 
    44 
    5 > What happend: I disabled acct_mgr.notification.accountchangelistener, cause again got above error for some reason. Anyway, a user invoked "forgot my password" and claimed, he didn't receive password change email. 
     5> What happend: I disabled `acct_mgr.notification.accountchangelistener`, cause again got above error for some reason. Anyway, a user invoked "forgot my password" and claimed, he didn't receive password change email. 
    66How shall he? If you disabled that component, this would effectively disable all !AcctMgr notifications. 
    77 
    8 > I checked that and it turns out that acct_mgr.notification.accountchangelistener and email password change seem to be disabled together? 
     8> I checked that and it turns out that `acct_mgr.notification.accountchangelistener` and email password change seem to be disabled together? 
    99> If so, then why does UI not care about this? 
    1010I'll have to investigate for confirming this, but likely you have hit a weak spot here. About why, well, actually not the web-UI, rather the developer has to care about, and notification is not as mature as most other parts of this plugin yet. 
     
    1212Disabling a feature as long as at least one of its dependencies have not been met is desired, sure. However its harder to tell then to do for every single feature we have in this plugin today. Keeping track of all dependencies has been improved over time, but is certainly not perfect yet, so you'll likely find other combinations of enabled and disabled plugin components that won't work as expected. But it is OT here, and I strongly suggest to open another ticket for such issues for dealing with it separately. 
    1313 
    14 > And finally, what is described in 13290 sounds very close to this issue. So is it fixed now? 
     14> And finally, what is described in [13290] sounds very close to this issue. So is it fixed now? 
    1515Fixed in `trunk` yes, but not in a stable release yet. Its planned to go into v0.5, but treat `trunk` as release candidate, if you need the fix now - just test it.