On 29/07/10 21:52, Shane Bryzak wrote:
> Hey guys,
>
> I've finished working on the enhancements to the wiki software so
that
> we can deal easier with spam. Here's a list of the changes that
have
> been made.
>
> 1) Added a 'Report as spam' button to the comments section of all
> document pages - this includes all FAQ and knowledge base pages,
however
> not forum topics. I decided not to add it to the forums because
> anything posted there goes to the mailing list (which has many eyes
> watching it), so I thought it was unnecessary. Clicking this
button
> simply creates a record in the new database table called
> WIKI_SPAM_REPORT, it does not affect the display of the comment at
all.
>
> 2) Added a 'Spam reports' tab to the Admin screen. This displays
a list
> of all the comments that have been reported as spam, the user who
made
> the report and the user who posted the comment. From here, you can
> either delete the comment, or mark it as not spam which will
remove all
> spam reports for that comment.
>
> 3) Added a 'Nuke' button to the user edit page. This button
deletes the
> user and all their comments, topics, etc - basically any content
they
> have posted to the site. This is a *proper* delete (the normal
delete
> just re-assigns ownership of all posts to the admin user) so use
with
> care! This action will also blacklist the user's e-mail address
and IP
> address. The IP address is recorded the first time the user
registers.
>
> 4) Added a 'Blacklist' tab to the Admin screen. This lists all the
> records in the blacklist table, and gives the option to remove
> individual records. Users with an e-mail address or IP address
that's
> on the blacklist are not able to register new accounts, instead
they are
> presented with a 'you have been blacklisted' message.
>
> I'm pretty much ready to roll this out to production, however I
would
> ideally like if we could test the changes more thoroughly in some
kind
> of staging environment. The wiki software is quite complex and I
cannot
> be 100% certain that my changes haven't broken or in some way
affected
> some obscure feature that isn't readily detectable in basic
testing. Do
> we have an environment where we can set this up and test it for a
few
> days before deploying to production?
>
> Also it would be nice to give the upgrade a couple of test runs to
make
> sure all DDL scripts etc are without error.
>
> Shane
> _______________________________________________
> seam-dev mailing list
>
seam-dev@lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/seam-dev
>
_______________________________________________
seam-dev mailing list
seam-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/seam-dev