View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|05593||Bug reports||[All Projects] Data Entry (non public)||public||2011-11-24 11:55||2012-04-26 08:32|
|Target Version||2.00a2||Fixed in Version||2.00RC1|
|Summary||05593: Blacklist Control Bug|
|Description||No content in:|
|Tags||No tags attached.|
|Complete LimeSurvey version number (& build)||00000|
|I will donate to the project if issue is resolved||No|
|Database & DB-Version||Online|
|Operating System (Server)||Online|
|Webserver software & version||Online|
||Please add a description of the bug and some instructions how we can reproduce the problem step by step.|
First head yourself to:
and login. There is no blacklisted users. When there are is no blacklisted user, if you go to:
there is only header and footer. It looks buggy. Personally, I would add dummy row or something to let administrator know everything is ok.
||I agree, there should at least be a short "No blacklisted users exist." message.|
||ajs, can you please check if this issue still exists in Yii and if appropiate fix it. Thank you.|
|Ok... I'm not exactly sure what is supposed to happen on this screen, but as it stands now there's a 500 error at the blacklist page.|
||I hope this helps: http://docs.limesurvey.org/Central+participants+database+%28User+panel%29#Blacklist_Control|
||ajs, yes, the goal is to fix that one ;). Let me know if you need more info. Also have a look at how it works in 1.91/1.92.|
|As far as I can tell, this feature does not exist in 1.91+ or the 1.92RCs. Am I mistaken?|
|Ok. I confirmed with aniessh that this code was only written for CI. Also, based on my discussion with aniessh, the features from http://docs.limesurvey.org/img/wiki_up/Screen_shot_5.png were not ever actually implemented meaning this will take slightly more time.|
||Sure, np. Thank you for taking care of this!|
I added the blacklist menu. None of the settings do anything at this point... but it saves/recalls everything from global settings.
How/where do I blacklist users (or where am I supposed to be able to blacklist users)? Is this in the db schema already, or does it need added?
In the participants table there is a field 'blacklisted' (Y/N)
In general it should be possible to blacklist one ore more users from the CPDB grid.
Ok. For some reason I thought blacklists were per survey. Would you take a look at the options and let me know if those still accurately represent what we are trying to do. If blacklisting is global... that seems to change things.
Either way, can you also let me know what you want for each default?
I think in general a survey invitation email could have some kind of blacklist link.
I am not sure how this originally this was intended by Jason/Aniesh. Mabye Jason can give us some insight?
ajs & carsten, I have aniessh's updates for some of the missing CI elements, which I'm trying to implement but GIT keeps stuffing me around. I've changed the files 3 times now, and then GIT refuses to commit them. Sigh.
ajs if you're working on CPDB now, can you please let me know which areas, because I'm also cleaning up the code and trying to get it to work the way it was intended after GSoC last year. I'm using it as an opportunity to learn about YII as well, so I don't want the goalposts to keep moving.
|I'm not really working on it other than resolving the bugs assigned to me. That being said, I can probably try to help you if you need help.|
The original idea was that the blacklist control will be both per survey and global, the global blacklist was to be stored under the cpdb database, and the local one to be stored under the token table.
If a user is blacklisted locally , he shouldn't be sent invitation/reminder email but can be copied from cpdb to other surveys, if he chooses to be blacklisted globally, he will not be allowed to be copied to any other survey.
The email that is sent out as invitation will have 3 links
1) blacklist locally
2) un-blacklist locally
3) blacklist globally
that's all I know was intended to be implemented.
||I'm pretty sure that this bug should be closed. The blacklist control page wasn't supposed to show lists of those blacklisted, just options in relation to blacklisting - which it appears to do. So I'm closing this for now. Let me know if I've misunderstood.|
|2011-11-24 12:11||Mazi||Note Added: 16702|
|2011-11-24 12:11||Mazi||Assigned To||=> aniesshsethh|
|2011-11-24 12:11||Mazi||Status||new => feedback|
||Note Added: 16703|
||Status||feedback => assigned|
|2011-11-24 12:40||Mazi||Note Added: 16704|
|2012-01-23 17:08||c_schmitz||Assigned To||aniesshsethh => user16774|
|2012-01-23 17:08||c_schmitz||Target Version||=> 2.00a2|
|2012-01-23 17:08||c_schmitz||Note Added: 16924|
||Note Added: 16942|
||Status||assigned => acknowledged|
|2012-01-24 17:13||Mazi||Note Added: 16943|
|2012-01-24 21:49||c_schmitz||Note Added: 16965|
|2012-01-24 21:49||c_schmitz||Status||acknowledged => assigned|
||Note Added: 16968|
||Note Added: 16969|
|2012-01-25 13:19||c_schmitz||Note Added: 16970|
||Note Added: 18080|
|2012-03-26 18:26||c_schmitz||Note Added: 18088|
||Note Added: 18095|
|2012-03-26 20:25||c_schmitz||Note Added: 18096|
|2012-03-26 20:25||c_schmitz||Assigned To||user16774 => jcleeland|
|2012-03-26 20:25||c_schmitz||Status||assigned => feedback|
|2012-03-27 00:30||jcleeland||Note Added: 18097|
||Note Added: 18098|
|2012-03-27 15:50||aniesshsethh||Note Added: 18100|
|2012-04-26 08:32||jcleeland||Note Added: 18481|
|2012-04-26 08:32||jcleeland||Status||feedback => closed|
|2012-04-26 08:32||jcleeland||Resolution||open => fixed|
|2012-04-26 08:32||jcleeland||Fixed in Version||=> 2.00RC1|