NOTE:: Before reporting an issue, make sure you are running the latest version, currently 3.3.1
|Anonymous | Login | Signup for a new account||30-04-17 11:55 BST|
|My View | View Issues | Change Log | Roadmap|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0008244||phplist application||User Management||public||15-10-06 06:52||23-05-12 12:25|
|Target Version||4.0.x||Fixed in Version||2.11.7|
|Summary||0008244: disabled field seems to serve no purpose|
i cannot see any use for the disabled field for a subscriber. I performed a test and disabled a user by entering 1 into the field and saving the update. I then attempted to send him an email and the subscriber got it! Why do you need the disabled field wen the unconfirmed does the job?
|Tags||No tags attached.|
|In addition I thought that they disabled tag might stop a subscriber from changing their details but the test allowed a subscriber who is marked as disabled to changed their details|
|it has a purpose in the Webbler, www.webbler.org, but you're right that it may cause confusion and unmet expectations.|
from my point of view this is a very serious issue. although its old and dusty. as mentioned in the documentation:
"When importing you can include a column labeled "Is this account disabled?". Values in the column can be 0 or 1. If 1, the users account will be disabled, if 0, the user will be normal. This can help in situations like this: You maintain a membership list independent of PHPList. Some people indicate to you that they don't want to receive email newsletters and you keep track of it via the membership list. Of course others unsubscribe via PHPList. So now you have to reconcile the two. The way to do it would be, include a column in your import file "Is this account disabled?". Mark the records with a 1 that have indicated they want to receive no email newsletters. Leave all the other records blank in that column. When you import those with a 1 should be marked as disabled, while the blank records should be left in the state they were previously in. (It would be wise to test this first on your own PHPList installation using a small test list.)"
if you rely on this you get lots of trouble! please raise the priority and fix this issue!
On or around line 470 (of version 2.10.5) in ./lists/admin/processqueue.php change:
$userconfirmed = ' and user.confirmed and !user.blacklisted ';
$userconfirmed = ' and user.confirmed and !user.blacklisted and !user.disabled ';
This will exclude "disabled" accounts when PHPlise selects accounts to send email to.
|Copyright © 2000 - 2017 MantisBT Team|