Closed Bug 519428 Opened 15 years ago Closed 14 years ago

Need better permission systems for forums

Categories

(quality.mozilla.org :: Website, defect, P1)

Product:
quality.mozilla.org
Component:
Website
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: cbook, Unassigned)

Details

One spammer used the way that the events forum is picked up by pmo and so spammed planet. This happened because authenticated user were allowed to post new forum topics.

To prevent this spamming again i have disabled creating new forum topics for authenticated user (except admins/community leads/mozilla-team). User can still reply/comment to postings from us. 

To find a better future solution, i think we should rethink this forum system and get a better Forum Access Control System in Place. We should investigate if http://drupal.org/project/forum_access is a solution for this problem. 

This is a blocker for 1.2
We could use Mollom (http://drupal.org/project/mollom) to protect QMO from spam. What do you think of?
I thought we were using Mollom already?
Yeah, we're already using mollom.
Ah, haven't known that. The list of modules we are using is somewhat in-transparent for us who are not directly involved in the work.
The end goal here is unclear, I think.

Can we be more specific about what a "better" system would be?  Or, what the core problem is?

If the problem was that any auth'ed user can create new forum topics, then I think that's been solved in comment #0

If the problem is spamming PMO, we could look at adjusting what PMO aggregates from QMO.

The Forum Access module will add a lot of granularity to forum access control, but it might add a bunch of complexity you don't need or want too.
Alex, we can disregard this bug for 1.2 because its unclear.
Target Milestone: 1.2 → 1.3
This bug is being moved to a resolved state of invalid due to one of the following reasons:

- we're moving to wordpress and so all drupal cruft is not going to be fixed
- the feature is not supported on the new qmo, at least for this release.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → INVALID
This bug is being moved to a resolved state of invalid due to one of the following reasons:

- we're moving to wordpress and so all drupal cruft is not going to be fixed
- the feature is not supported on the new qmo, at least for this release.
Target Milestone: 2.3 → ---
You need to log in before you can comment on or make changes to this bug.