[Remember Mailing List] How to disable a member's login?

[Mark Phillips]

I have an older site, Plone 2.5.5 running membrane1.0  and remember 1.0b1. It is a school newspaper site, so each year a couple of new students join the staff and few graduate. I can't delete the students who have graduated as the school wants to keep their work archived on the site. I set up a workflow for content and have an archive state, so only this year's content is displayed, and the archived content is in another folder. However, I don't have a way to disable the user accounts for the students who have graduated. I am looking for an easy way to disable logins to these accounts, but still preserve the content and the fact that John wrote these articles, and Samantha wrote these articles, even though they cannot login anymore.

I guess I would need a way to "un-disable" an account, in case I disable the wrong one...;-)

I have googled for a possible solution and searched this list, but I can't find anything under "disable member" and similar patterns.

Thanks for any suggestions you may have!

Mark

--
Archive: http://www.coactivate.org/[…]/1295453339470
To unsubscribe send an email with subject "unsubscribe" to reme...@lists.coactivate.org. Please contact remember...@lists.coactivate.org for questions.

[Cristopher Ewing]

On Jan 19, 2011, at 8:08 AM, Mark Phillips wrote:

I have an older site, Plone 2.5.5 running membrane1.0  and remember 1.0b1. It is a school newspaper site, so each year a couple of new students join the staff and few graduate. I can't delete the students who have graduated as the school wants to keep their work archived on the site. I set up a workflow for content and have an archive state, so only this year's content is displayed, and the archived content is in another folder. However, I don't have a way to disable the user accounts for the students who have graduated. I am looking for an easy way to disable logins to these accounts, but still preserve the content and the fact that John wrote these articles, and Samantha wrote these articles, even though they cannot login anymore.

I guess I would need a way to "un-disable" an account, in case I disable the wrong one...;-)

I have googled for a possible solution and searched this list, but I can't find anything under "disable member" and similar patterns.

Thanks for any suggestions you may have!

Mark,

I haven't used remember specifically, but Products.FacultyStaffDirectory (1)(2) implements member and group enabling/disabling via workflow states.  You could take a look at the membrane adapters in that product for the FSDPerson and FSDPersonGrouping objects and see how it's done there.  Perhaps there would be a convenient mapping to remember functionality that you could implement.

HTH

c

(1) http://pypi.python.org/pypi/Products.FacultyStaffDirectory/3.0b2

(2) https://weblion.psu.edu/trac/weblion/browser/weblion/Products.FacultyStaffDirectory/tags/3.0b2

********************************

Cris Ewing

Webmaster, Lead Developer

Department of Radiology Web Services

University of Washington

School of Medicine

Work Phone: (206) 616-1288

Cell Phone: (206) 708-9083

E-mail: cew...@u.washington.edu

Web: http://www.rad.washington.edu

*******************************

--
Archive: http://www.coactivate.org/[…]/1295455088120

[Clayton Parker]

On Jan 19, 2011, at 11:36 AM, Cristopher Ewing wrote:

> On Jan 19, 2011, at 8:08 AM, Mark Phillips wrote:
>
>> I have an older site, Plone 2.5.5 running membrane1.0 and remember 1.0b1. It is a school newspaper site, so each year a couple of new students join the staff and few graduate. I can't delete the students who have graduated as the school wants to keep their work archived on the site. I set up a workflow for content and have an archive state, so only this year's content is displayed, and the archived content is in another folder. However, I don't have a way to disable the user accounts for the students who have graduated. I am looking for an easy way to disable logins to these accounts, but still preserve the content and the fact that John wrote these articles, and Samantha wrote these articles, even though they cannot login anymore.
>>
>> I guess I would need a way to "un-disable" an account, in case I disable the wrong one...;-)
>>
>> I have googled for a possible solution and searched this list, but I can't find anything under "disable member" and similar patterns.
>>
>> Thanks for any suggestions you may have!
>>
>
> Mark,
>
> I haven't used remember specifically, but Products.FacultyStaffDirectory (1)(2) implements member and group enabling/disabling via workflow states. You could take a look at the membrane adapters in that product for the FSDPerson and FSDPersonGrouping objects and see how it's done there. Perhaps there would be a convenient mapping to remember functionality that you could implement.

It has been a while since I have done anything with Remember or membrane. IIRC, there are settings in the membrane tool that say what states are "active", you could have a disabled state that is not in the active list.

Clayton
--
Six Feet Up, Inc. | Where sophisticated web projects thrive
Direct Line: +1 (317) 861-5948 x603
Email: cla...@sixfeetup.com
Try Plone 4 Today at: http://plone4demo.com

How am I doing? Please contact my manager Gabrielle Hendryx-Parker
at gabr...@sixfeetup.com with any feedback.

--
Archive: http://www.coactivate.org/projects/remember/lists/remember/archive/2011/01/1295455529250

[Clayton Parker]

On Jan 19, 2011, at 11:08 AM, Mark Phillips wrote:

> I have an older site, Plone 2.5.5 running membrane1.0 and remember 1.0b1. It is a school newspaper site, so each year a couple of new students join the staff and few graduate. I can't delete the students who have graduated as the school wants to keep their work archived on the site. I set up a workflow for content and have an archive state, so only this year's content is displayed, and the archived content is in another folder. However, I don't have a way to disable the user accounts for the students who have graduated. I am looking for an easy way to disable logins to these accounts, but still preserve the content and the fact that John wrote these articles, and Samantha wrote these articles, even though they cannot login anymore.
>
> I guess I would need a way to "un-disable" an account, in case I disable the wrong one...;-)

Here is an example from the remember sample user.

http://svn.plone.org/svn/collective/Products.sampleremember/trunk/Products/sampleremember/profiles/default/membrane_tool.xml

I looked on an old site of mine, but didn't see the UI for this anywhere. Hopefully this will point you in the right direction though.

Clayton
--
Six Feet Up, Inc. | Where sophisticated web projects thrive
Direct Line: +1 (317) 861-5948 x603
Email: cla...@sixfeetup.com
Try Plone 4 Today at: http://plone4demo.com

How am I doing? Please contact my manager Gabrielle Hendryx-Parker
at gabr...@sixfeetup.com with any feedback.

--
Archive: http://www.coactivate.org/projects/remember/lists/remember/archive/2011/01/1295455935510

[Wichert Akkerman]

On 1/19/11 17:45 , Clayton Parker wrote:
> On Jan 19, 2011, at 11:36 AM, Cristopher Ewing wrote:
>
>> On Jan 19, 2011, at 8:08 AM, Mark Phillips wrote:
>>
>>> I have an older site, Plone 2.5.5 running membrane1.0 and remember 1.0b1. It is a school newspaper site, so each year a couple of new students join the staff and few graduate. I can't delete the students who have graduated as the school wants to keep their work archived on the site. I set up a workflow for content and have an archive state, so only this year's content is displayed, and the archived content is in another folder. However, I don't have a way to disable the user accounts for the students who have graduated. I am looking for an easy way to disable logins to these accounts, but still preserve the content and the fact that John wrote these articles, and Samantha wrote these articles, even though they cannot login anymore.
>>>
>>> I guess I would need a way to "un-disable" an account, in case I disable the wrong one...;-)
>>>
>>> I have googled for a possible solution and searched this list, but I can't find anything under "disable member" and similar patterns.
>>>
>>> Thanks for any suggestions you may have!
>>>
>>
>> Mark,
>>
>> I haven't used remember specifically, but Products.FacultyStaffDirectory (1)(2) implements member and group enabling/disabling via workflow states. You could take a look at the membrane adapters in that product for the FSDPerson and FSDPersonGrouping objects and see how it's done there. Perhaps there would be a convenient mapping to remember functionality that you could implement.
>
> It has been a while since I have done anything with Remember or membrane. IIRC, there are settings in the membrane tool that say what states are "active", you could have a disabled state that is not in the active list.

That is no longer true with current versions of membrane. Membrane is an
infrastructure package, so it leaves this kind of functionality to the
implementation of member types instead of hard coding a specific
behaviour itself. You can easily do this in the authentication method or
adapter for your member type by checking the workflow state of the object.

If you are using remember this support is already provided by remember.

Wichert.

--
Archive: http://www.coactivate.org/projects/remember/lists/remember/archive/2011/01/1295456131830

[ken manheimer]

On Wed, Jan 19, 2011 at 11:08 AM, Mark Phillips <ma...@phillipsmarketing.biz> wrote:

I have an older site, Plone 2.5.5 running membrane1.0  and remember 1.0b1. It is a school newspaper site, so each year a couple of new students join the staff and few graduate. I can't delete the students who have graduated as the school wants to keep their work archived on the site. I set up a workflow for content and have an archive state, so only this year's content is displayed, and the archived content is in another folder. However, I don't have a way to disable the user accounts for the students who have graduated. I am looking for an easy way to disable logins to these accounts, but still preserve the content and the fact that John wrote these articles, and Samantha wrote these articles, even though they cannot login anymore.

unfortunately, any answers i have for you are going to be for different versions of everything - membrane, remember, and plone.  however, i can tell you that the standard remember workflows include a "disabled" state specifically designed to inhibit the ability for logins on otherwise existing, functional accounts.

disabling an account is something that properly authorized accounts, like admins, can do by visiting the member instance in <site-root>/portal_memberdata and using the workflow content menu (on the right top of the content well) to change the workflow status of the member to disabled.  you could also visit the contents view of the portal_memberdata tool, select the members which you want to disable, and do a "Change State" activity, which will let you change the workflow state of a bunch of members.

when i say "you could...", i'm assuming that your setup works like the more recent versions i'm familiar with.  there's a bunch of things that could be getting in the way of your seeing that, all compounded by the biggest one which is that i'm not sure the way things work in your versions:

1. your site's accounts are not being instantiated as remember accounts.  if you can't find the accounts in the <site-root>/portal_memberdata tool, then the accounts may not be remember-instantiated. check the Site Setup / Remember Settings add-on configuration activity to see what the default member type is.
2. the workflow for your remember accounts does not include the disable step.  i think the default remember 1.0b1 workflows include that, but am not sure.
3. plone 2.5.5 is not exposing the workflow choices, or some other big version difference.

I guess I would need a way to "un-disable" an account, in case I disable the wrong one...;-)

that's one of the nice things about the status being implemented via workflow - it is already tailored for administrative deactivation and reactivation, and you can add workflows or adjust existing ones to custom tailor it as you wish.  provided the workflow version in your plone installation offers the ability to migrate instance workflows, etc...

 

I have googled for a possible solution and searched this list, but I can't find anything under "disable member" and similar patterns.

remember is specifically designed for that purpose.  i'm not sure why you're not seeing it - perhaps it's where you're not looking, or perhaps there's a version problem.

Thanks for any suggestions you may have!

Mark

let us know what you find.

ken manheimer

http://myriadicity.net

--
Archive: http://www.coactivate.org/[…]/1295453339470
To unsubscribe send an email with subject "unsubscribe" to reme...@lists.coactivate.org. Please contact remember...@lists.coactivate.org for questions.

--
Archive: http://www.coactivate.org/[…]/1295456458349

[Mark Phillips]

On Wed, Jan 19, 2011 at 9:55 AM, ken manheimer <ken.ma...@gmail.com> wrote:

On Wed, Jan 19, 2011 at 11:08 AM, Mark Phillips <ma...@phillipsmarketing.biz> wrote:

I have an older site, Plone 2.5.5 running membrane1.0  and remember 1.0b1. It is a school newspaper site, so each year a couple of new students join the staff and few graduate. I can't delete the students who have graduated as the school wants to keep their work archived on the site. I set up a workflow for content and have an archive state, so only this year's content is displayed, and the archived content is in another folder. However, I don't have a way to disable the user accounts for the students who have graduated. I am looking for an easy way to disable logins to these accounts, but still preserve the content and the fact that John wrote these articles, and Samantha wrote these articles, even though they cannot login anymore.

unfortunately, any answers i have for you are going to be for different versions of everything - membrane, remember, and plone.  however, i can tell you that the standard remember workflows include a "disabled" state specifically designed to inhibit the ability for logins on otherwise existing, functional accounts.

disabling an account is something that properly authorized accounts, like admins, can do by visiting the member instance in <site-root>/portal_memberdata and using the workflow content menu (on the right top of the content well) to change the workflow status of the member to disabled.  

 

I don't have this option  under portal_memberdata. Probably just an older version.

you could also visit the contents view of the portal_memberdata tool, select the members which you want to disable, and do a "Change State" activity, which will let you change the workflow state of a bunch of members.

 

This works perfectly! Thanks!!

when i say "you could...", i'm assuming that your setup works like the more recent versions i'm familiar with.  there's a bunch of things that could be getting in the way of your seeing that, all compounded by the biggest one which is that i'm not sure the way things work in your versions:

1. your site's accounts are not being instantiated as remember accounts.  if you can't find the accounts in the <site-root>/portal_memberdata tool, then the accounts may not be remember-instantiated. check the Site Setup / Remember Settings add-on configuration activity to see what the default member type is.
2. the workflow for your remember accounts does not include the disable step.  i think the default remember 1.0b1 workflows include that, but am not sure.
3. plone 2.5.5 is not exposing the workflow choices, or some other big version difference.

I guess I would need a way to "un-disable" an account, in case I disable the wrong one...;-)

that's one of the nice things about the status being implemented via workflow - it is already tailored for administrative deactivation and reactivation, and you can add workflows or adjust existing ones to custom tailor it as you wish.  provided the workflow version in your plone installation offers the ability to migrate instance workflows, etc...

 

I have googled for a possible solution and searched this list, but I can't find anything under "disable member" and similar patterns.

remember is specifically designed for that purpose.  i'm not sure why you're not seeing it - perhaps it's where you're not looking, or perhaps there's a version problem.

 

Not sure....but you solved it for me! Thanks again!

Thanks for any suggestions you may have!

Mark

let us know what you find.

ken manheimer

http://myriadicity.net

--
Archive: http://www.coactivate.org/[…]/1295453339470

To unsubscribe send an email with subject "unsubscribe" to reme...@lists.coactivate.org. Please contact remember...@lists.coactivate.org for questions.

--
Archive: http://www.coactivate.org/[…]/1295456458349

To unsubscribe send an email with subject "unsubscribe" to reme...@lists.coactivate.org. Please contact remember...@lists.coactivate.org for questions.

--
Archive: http://www.coactivate.org/[…]/1295498923532

[ken manheimer]

i'm glad you have a solution.  just one clarification, interspersed with the cited text.

On Wed, Jan 19, 2011 at 11:48 PM, Mark Phillips <ma...@phillipsmarketing.biz> wrote:

On Wed, Jan 19, 2011 at 9:55 AM, ken manheimer <ken.ma...@gmail.com> wrote:

[...]

disabling an account is something that properly authorized accounts, like admins, can do by visiting the member instance in <site-root>/portal_memberdata and using the workflow content menu (on the right top of the content well) to change the workflow status of the member to disabled.  

I don't have this option under portal_memberdata. Probably just an older version.

i was trying to point you to the pages for the individual members, which are collectively found in the portal_memberdata container.  each remember account page found there should have a workflow menu on the content bar, by which you can do things like disable and reenable accounts, depending on their current workflow state.

you could also visit the contents view of the portal_memberdata tool, select the members which you want to disable, and do a "Change State" activity, which will let you change the workflow state of a bunch of members.

 

This works perfectly! Thanks!! 

that's a good way to change the state of a bunch of accounts at the same time, while the individual account workflow control is convenient for individual members.

 

I have googled for a possible solution and searched this list, but I can't find anything under "disable member" and similar patterns.

remember is specifically designed for that purpose.  i'm not sure why you're not seeing it - perhaps it's where you're not looking, or perhaps there's a version problem.

 

Not sure....but you solved it for me! Thanks again!

it may be a "forest for the trees" documentation problem.  anyway, i'm glad you're on track.

ken

--
Archive: http://www.coactivate.org/[…]/1295562426022

[Mark Phillips]

Ken,

Thanks for the clarification. I added a note in the cited test...

On Thu, Jan 20, 2011 at 3:26 PM, ken manheimer <ken.ma...@gmail.com> wrote:

i'm glad you have a solution.  just one clarification, interspersed with the cited text.

On Wed, Jan 19, 2011 at 11:48 PM, Mark Phillips <ma...@phillipsmarketing.biz> wrote:

On Wed, Jan 19, 2011 at 9:55 AM, ken manheimer <ken.ma...@gmail.com> wrote:

[...]

disabling an account is something that properly authorized accounts, like admins, can do by visiting the member instance in <site-root>/portal_memberdata and using the workflow content menu (on the right top of the content well) to change the workflow status of the member to disabled.  

 

I don't have this option under portal_memberdata. Probably just an older version.

i was trying to point you to the pages for the individual members, which are collectively found in the portal_memberdata container.  each remember account page found there should have a workflow menu on the content bar, by which you can do things like disable and reenable accounts, depending on their current workflow state.

I think I found what you are talking about. I went to portal_memberdata, selected a member and clicked edit. That page has an workflow tab. However, there aren't any options to change the state of the member. The link under workflow just goes to the general portal workflow tab. Maybe just an older version. I have attached some screen shots, which will probably not make it to the list, but might to your email account.

Thanks again for your help!

you could also visit the contents view of the portal_memberdata tool, select the members which you want to disable, and do a "Change State" activity, which will let you change the workflow state of a bunch of members.

 

This works perfectly! Thanks!! 

that's a good way to change the state of a bunch of accounts at the same time, while the individual account workflow control is convenient for individual members.

 

I have googled for a possible solution and searched this list, but I can't find anything under "disable member" and similar patterns.

remember is specifically designed for that purpose.  i'm not sure why you're not seeing it - perhaps it's where you're not looking, or perhaps there's a version problem.

 

Not sure....but you solved it for me! Thanks again!

it may be a "forest for the trees" documentation problem.  anyway, i'm glad you're on track.

ken

--
Archive: http://www.coactivate.org/[…]/1295563857832

[ken manheimer]

On Thu, Jan 20, 2011 at 5:50 PM, Mark Phillips <ma...@phillipsmarketing.biz> wrote:

Ken,

Thanks for the clarification. I added a note in the cited test...

On Thu, Jan 20, 2011 at 3:26 PM, ken manheimer <ken.ma...@gmail.com> wrote:

[...]

i was trying to point you to the pages for the individual members, which are collectively found in the portal_memberdata container.  each remember account page found there should have a workflow menu on the content bar, by which you can do things like disable and reenable accounts, depending on their current workflow state.

I think I found what you are talking about. I went to portal_memberdata, selected a member and clicked edit. That page has an workflow tab. However, there aren't any options to change the state of the member. The link under workflow just goes to the general portal workflow tab. Maybe just an older version. I have attached some screen shots, which will probably not make it to the list, but might to your email account.

seeing the screen shots is informative.  they show Zope Management Interface views of the pages.  the workflow status content menu is a plone feature, which would be available from the plone content view of the page.  (not sure how you wind up there - but, as you say, this is remember running under zope 2, with which i'm unfamiliar.)  when on the views for one of the accounts, try the 'View' tab, that might show the plone view with the content.

ken

--
Archive: http://www.coactivate.org/[…]/1295564325852

[Mark Phillips]

On Thu, Jan 20, 2011 at 3:58 PM, ken manheimer <ken.ma...@gmail.com> wrote:

On Thu, Jan 20, 2011 at 5:50 PM, Mark Phillips <ma...@phillipsmarketing.biz> wrote:

Ken,

Thanks for the clarification. I added a note in the cited test...

On Thu, Jan 20, 2011 at 3:26 PM, ken manheimer <ken.ma...@gmail.com> wrote:

[...]

i was trying to point you to the pages for the individual members, which are collectively found in the portal_memberdata container.  each remember account page found there should have a workflow menu on the content bar, by which you can do things like disable and reenable accounts, depending on their current workflow state.

I think I found what you are talking about. I went to portal_memberdata, selected a member and clicked edit. That page has an workflow tab. However, there aren't any options to change the state of the member. The link under workflow just goes to the general portal workflow tab. Maybe just an older version. I have attached some screen shots, which will probably not make it to the list, but might to your email account.

seeing the screen shots is informative.  they show Zope Management Interface views of the pages.  the workflow status content menu is a plone feature, which would be available from the plone content view of the page.  (not sure how you wind up there - but, as you say, this is remember running under zope 2, with which i'm unfamiliar.)  when on the views for one of the accounts, try the 'View' tab, that might show the plone view with the content.

The View tab works to access a page with a drop down to disable the member. For posterity - plone_memberdata -> edit the member -> view tab.

BTW, I got to the workflow status page from screenshot_17, clicking on the link under the workflow heading. It was the only link on the page. Sorry about failing to mention that the screen shots went in numerical order - 15->16->17->18.

Cheers!

Mark

--
Archive: http://www.coactivate.org/[…]/1295565304921