The ‘Node Limit User’ logic seems to work well with a single specified user and a complementary catch-all rule (Limit for Authenticated user is zero).

However, when two users are specified (with a complementary catch-all rule), neither of them can create a node of the restricted content type. The example in the attached pdf may make more sense than my text.

I am not sure if this is a bug, a feature, or an unavoidable limitation. Honestly, this is not a real concern for me, but I point it out in case it is possible to give more flexibility to the module.

Thanks for your work on this interesting about powerful project!

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

DuaelFr’s picture

Status: Active » Needs review

Alpha4 contains some improvements to avoid some limits to apply when they would not.

dougsap’s picture

Title: Summary of 'Node Limit User' testing on 7.x-1.0-alpha3 » The ‘Node Limit User’ logic with complementary catch-all rule stopped working in Alpha04
Version: 7.x-1.0-alpha3 » 7.x-1.0-alpha4
FileSize
492.5 KB

The ‘Node Limit User’ logic which seemed to work well with a single specified user and a complementary catch-all rule (Limit for Authenticated user is zero) in Alpha03, stopped working in Alpha04.

In Alpha04, it is not possible for the Specified user (or any Authenticated user to create any of the particular Content Type). The attached image may help recreate the test case. Don't get discouraged, this is really complex stuff and not easy. Thanks!

Comment: At some point, it might be useful or necessary to create a matrix of the Node Limit Modules which are valid to combine, and indicate the order of precedence.

dougsap’s picture

Status: Needs review » Needs work

I just realized that I should have changed status to 'needs work' with my previous post. Thanks!

dougsap’s picture

Version: 7.x-1.0-alpha4 » 7.x-1.0-alpha5
FileSize
751.35 KB

Results in alpha5 are similar to alpha4.

Node Limit for a specified user works, but seems of limited usefulness if you can't somehow specify a restriction for the remaining users of the population.

If a complementary 'catch-all' restriction is defined for Authenticated users for a node limit value of zero, it won't let the specified user create any nodes either. See attached for more detail.

DuaelFr’s picture

As indicated in the release, I just fixed some documentation and the critical bug.
Do not waste more time reviewing this for the moment but thank you very much for your involvement :)