Posted by greggles on November 10, 2008 at 10:16pm
Last updated by duncan.moo on Wed, 2012-09-26 13:06
Last updated by duncan.moo on Wed, 2012-09-26 13:06
There are a lot of modules which aim to limit the number of nodes that a user/role can create. Here's a brief roundup (please add more types or qualifications via comments).
Node limitnumber
- 5.x, 6.x only
- 6.x-2.x relies on rules
- Limits can be created using rules.
- Time-intervals are now implemented
- Under active development
create quota
- Relies on rules
- 6.x only
- Claims to be extensible
- Seems to require the implementer to write some code
- No longer maintained
user_quota
- Limits per user, per content type.
- Users who are not limited on a content type can create as many of that type as they want.
- Admin screen shows a history of each alteration of a user's quota and allows admins with "administer site configuration" to add (or subtract) from the quota.
nodefamily
- 4.7, 5.x only
- Creates relationships between nodes
- Limits the number of nodes of a type that a user can create
- No longer maintained
node_limit
- 6.x, 7.x
- Allows for per-user, per-role, per-og (Dropped), per-timeframe (Dropped), per-timeinterval, per-taxonomyterm, etc limits (or any combination thereof)
I have actually built yet another one of these which has limits per user per content type. If there is no limit for a uid/type then it allows the content to be created. If folks agree this is a not a duplicate of the existing nodes I'll contribute it and document it's difference from the existing solutions ;)
Comments
Is your UI significantly
Is your UI significantly different than the Node Limitnumber module? It seems like you provide similar functionality, except that instead of limiting per role, you limit per user. How difficult would it be to extend the Node limitnumber module so that you could choose either role or user (or both) as options for limiting node creation?
This way we would be cutting down on duplication of modules.
pro/con
A pro/con of nearly all of these is that they are largely unmaintained, so if I actively contribute patches it could be easy to vastly alter the module.
A real con of all but the create_quota is a serious deviation from coding standards/style which makes it painful to work with them :/
It looks like node_limitnumber provides this per-user-per-content-type facility at least somewhat (the install file shows support for users or roles, but none of the code seems to actually use it).
--
Growing Venture Solutions | Drupal Dashboard | Learn more about Drupal - buy a Drupal Book
knaddison blog | Morris Animal Foundation
I know your pain with the
I know your pain with the coding standards. Maybe we can specify a general procedure to follow then when taking over an unmaintained module.
If you are planning on creating a module anyway, or have built a module, it should be possible to take over/co-maintain one of these projects and steer it in the direction of your desired functionality.
That being said, I know of a few modules which are 'partially maintained' which means that if patches are supplied, the maintainer checks the patch and commits it to the project. I think most of my projects fall in this category.
True enough. Step 1 of any
True enough.
Step 1 of any code change should be a non-invasive patch to bring it up to coder.module standards.
They are just no fun to touch/patch otherwise.
Step 2 is PHP strict compliance.
Then functional fixes or additions.
Then test cases :-)
... not that I always follow that myself, but that's how it SHOULD go if there was a responsive 'maintainer' or you'd been granted CVS.
resolution
In the end I did post my slightly duplicate module (but it isn't a true duplicate since it is per user and per content type limits while these are mostly per role).
However, I got Doug Muth to let me put my project into the old user quota project. So, the net impact on the world is slightly positive
* -1: new duplicate module created
* +1: old abandoned module removed
* +.5: documentation clarifying all these duplicates created
--
Growing Venture Solutions | Drupal Dashboard | Learn more about Drupal - buy a Drupal Book
knaddison blog | Morris Animal Foundation
Pros
It's good idea to extend current "user_quota" module by implementing per user + per role + per content type
Cases (node type)
1) User profile node (only one)
2) User places (better to limit per role)
3) Photoalbums - limit per role + per user (for example if user gains enoght "userpoints")
There's also
There's also http://drupal.org/project/quota_by_role
Not tried it, but according to the project page this allows quotas to be set per day.
NodeLimit: The final solution?
There is a brand new addition to this, that maybe will be the final solution to all this mess: NodeLimit. It will made available to limit nodes, nodes per group, and even the creation of users.
It´s in dev version, and it´s facing a architectural challenge that needs help. Maybe someone here could help it out, as I´m not a programmer, my help is very limited.
Regards,
Rosamunda
Maximum of nodes to create for each user
We want each of our members to submit a maximum of 3 pictures in a photo competition. For this only Node limitnumber appears to be the right solution. We hope this module will have a final D6 version soon.
The Node Limit Number project
The Node Limit Number project has been resurrected and many new features have been added. This module now integrates with Rules and the limits are very easy to create. Head over to the Node Limit Number project and grab the latest development copy. The 2.0 release will be out soon.
Limit comments
Do any of these (or other) modules limit the number of comments by a user per day or per hour? I have a few over-active site members who are in need of other hobbies, apparently.
Thanks for any suggestions.
Per Organic Group
I think that there is definitely a need for node creation limitation based on Organic Groups too.
I'm looking into how to use Rules to accomplish this, but I'm not sure if I can actually. If you guys have any way to redirect me, I'd be more than happy to jump into that.
Subscribing...
Subscribing...
Node Limit doesn't seem to work...
Downloading and trying both the release and the dev version, neither one seemed to work for me. My use case was that I wanted members of a given role to be restricted in their node creation, so user_quota didn't seem to work for me because it wanted me to set up quotas per user. I eventually ended up with Node LimitNumber, which seems to work fine.
-john
Any options for D7
It appears that none of these options are available for Drupal 7. Does anyone know of any options for this that are on D7?
subscribing
Does anyone know of any options for this that are on D7?
robin
http://gazwal.com/fr
http://biboo.net
http://twitter.com/gazwal
limit access per day?
don't know if this is relevant to this discussion, but am interested in a module that would limit a role to a number of node-type views per day.
anyone ever stumbled upon this before?
related?
thanks..
Does anyone know if the Node Limit Module for D7 works
Hi! I'm planning a project, and need to know if the D7 version of Node Limit module works. I do understand that it's in Alpha and has some bugs... But does it kind-of work?