I've seen this plan in the project, but I want to list some great features with rules power.

After integrate with rules, you can:
a) set/change node limit to a individual user automatically due to any events
b) easily send any notes to users via mail, heartbeat etc
c) easily integrate with commerce, eg:manage advertising
d) easily integrate with any other modules play well with rules..

We need rules actions:
a) change node limit, add/reduce

Comments

DuaelFr’s picture

Due to a lack of (my) time, this is not planned in the near future.
If you want to participate, you are very welcome but the module will absolutely need a 2.x refactoring before thinking to build this kind of features.

wOOge’s picture

I've written a tutorial on how to achieve some of this module's functionality in Rules here:

http://drupal.org/node/1893978

pinkonomy’s picture

Any news on this one?

kopeboy’s picture

Issue summary: View changes

Interested as well..

What I am looking for is increasing node limit from 0 to 1 of a particular content type when the user buys a product.
Or, the other way around, set all other content types from 1 to 0 when the user buys a product.

kopeboy’s picture

Priority: Normal » Major

Maybe we can copy some code from here https://www.drupal.org/project/node_limitnumber ?
They have integration with Rules, but only drupal 6 version..

I am just building websites, I'm not a php dev otherwise I would love to help :/

Also, I think we can look into Contet Access rules integration.
The only problem with using that already is that I cannot restrict node creation but only editing and visibility :(

Example of functionality to build with this module and rules:

User (supplier) can create a node (his activity) choosing from 15 business categories (they can be very different and have many fields, so there are 15 distinct content types), after he pays for it. Creating 15 different roles is unfeasible and unnecessary (apart from this functionality atm). The supplier can choose from any activity and create it, but it will be unpublished until he buys it. After he creates one, he cannot create others (any supplier can only create 1 activity).

All this would be very easy to implement if we could modify core roles permissions with rules, but if I'm not wrong, we can't :(

chilligroup’s picture

following

kopeboy’s picture

I ended up unistalling Node limit and creating the limit functionality from zero with normal (hidden) Fields and Rules..
Maybe not as performant (not sure though), but flexible as you want it to be.

Jedd Casella’s picture

@kopeboy - would you mind sharing the rule you created or a simple walk-through on how to achieve this without node limit?

vaccinemedia’s picture

@kopeboy I'm also interested in how you managed to achieve this