I've just had a three month baptism of open registration and user administration.<br><br>Registrations are driven by "backlinkers" in pursuit of page rank. Some registrants will comment or post with backlinks as well as pimping their sites in profiles.<br>
<br>Moderation is a must to prevent embarrassing content leaking to a sensitive audience. The burden of moderation can be mitigated by spam suppression like mollom and recaptcha.<br><br>Initially I "blocked" errant registrants but the profiles persist which is the primary goal of the backlinkers. I have since opted to "delete" rather than block. Advuser helps, "prune" is too crude.<br>
<br>In the medium run, I am honing an SQL query to separate the sheep from the goats preserving valued registrants meaning those who post relevant content. Hopefully that will lead to a "purge" module that can be "cron"-ed.<br>
<br>Jim<br><br><div class="gmail_quote">On Sun, Mar 21, 2010 at 10:34 AM, Scott <span dir="ltr"><<a href="mailto:scott@bscottholmes.com">scott@bscottholmes.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I just tested this and it does seem to be the case. I tried blocking a<br>
test user by clearing the value in the password field and setting the<br>
blocked toggle while monitoring the encrypted password value in _users<br>
using mysql. The user record was saved correctly and the encrypted<br>
password string remained the same. I should have suspected this.<br>
Thanks.<br>
<div><div></div><div class="h5"><br>
<br>
On Sat, 2010-03-20 at 17:05 -0400, Adept wrote:<br>
> On 3/20/2010 3:58 PM, Scott wrote:<br>
> > I'm getting an error when I try to ignore the password fields. The<br>
> > confirm password field is blank and the message I get is that the<br>
> > passwords don't match. Therefore the user record is not updated.<br>
> ><br>
> ><br>
><br>
> it's possible that if you have stored your own log-in password in your<br>
> browser, that your browser is auto-filling the Password field wtih<br>
> _your_ password. When making changes to another user's account, make<br>
> sure *both* password fields are blank, unless you are in there to reset<br>
> their password (in which case you will need to replace the contents of<br>
> the Password field with _their_ password and then retype it in the<br>
> Confirm Password field).<br>
><br>
> make sense?<br>
><br>
> kazar<br>
<br>
--<br>
[ Drupal support list | <a href="http://lists.drupal.org/" target="_blank">http://lists.drupal.org/</a> ]<br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Rev. Jim Tarvid, PCA<br><a href="http://ls.net">http://ls.net</a><br><a href="http://drupal.ls.net">http://drupal.ls.net</a><br><a href="http://crossleft.org">http://crossleft.org</a><br>
<br><br>