Role based legal

In order not to duplicate this ,
subscribing for D6 !

I would like this too

This would be a great feature, and thanks @mdayton for the tip about agreement module!

+1 to D6!

I'm in the same boat. I have buyer roles and seller roles. Each of which need different T&Cs.

++

There's a lot mentioned on the Agreement module's description page that would sit well in this module. I'm rather surprised that none of it features here.

I'd love to just sit down and code this right now, but I really can't justify it with so much else on, dangit.

Ok so a specific use case. I create users of a certain role long before they use the site. These users are in the system unwittingly at first. When they have passed certain criteria, a rule kicks in and promotes them to another role. These users never log in until this point, indeed they probably don't even know they're in the site at all, but that's when they are automatically sent a password reminder, at which point they can then log in with their new role. It doesn't, at any point, make sense to challenge these users before they have this role. Indeed, it is more likely to be a hindrance than anything.

Furthermore, in this same site, there are two distinct sections. In the section not relating to the above scenario, there is no need to challenge any of the associated roles *at all* - content managers, etc.

That said, legal.module still issues an appropriate challenge at the point of login for those newly-promoted users, which is fine. The point is, users can exist *with* roles before they ever log in; they can be created *with roles* in the create UI; etc. That they are challenged on the registration page is of course admirable, but there are many other use cases.

Placing a multi-checkbox widget on the settings page is relatively trivial, as is implementing the checks on that in code - if the current role is not selected on the widget, don't challenge them.

I see from testing that any user will not be challenged until they log in directly. Masquerade does not trigger the challenge for example, which is good, this is a start.

I actually quite like what http://drupal.org/project/agreement offers, from its description. I don't see a need to shy away from displaying the Legal page (view legal page permission). That can be done with content_access or other access modules. I don't see a need to be creating revisions internally either - why not just use a node and be done with it? Or failing that (as there was an obvious architectural decision made) why not offer a choice? Radio between hard coded /legal and a choice of node via autocomplete widget?

I understand why the terms-on-registration thing is useful as a short-cut. That said, it is a one-hit affair. If the registration is approved, either by admin or email confirmation, then the user gains the "authenticated user" role. If another role is granted by the system under different circumstances, then the user may then be in a role selected for challenge. Under either of these circumstances, could a check not be applied *then*, as an alternative? This is seemingly the default behaviour in any case, if the user has gotten to a position where the challenge has not yet been accepted.

In any case, I am curious as to what the performance hit is of all this? It strikes me there must be some check performed on every page load to ensure the challenge has been met...?

Perhaps some of this is off-topic, but better out than in! ;)

I have used a trick that doesn't require any of the modules. This is for Drupal 7.x
1) First add a field set having title similar to 'Terms & Conditions' or any thing you want
2) Install markup module and add a markup field
3) Copy past your legal text and put the field under the fieldset
4) Now, add a boolean check box and make it 'requited'
5) Give it a lable like 'I agree to above terms & conditions'
6) Place this field blow the markup field, within the fieldset and you are done.

Now, you need to hide both these feilds using the display settings.
Also, once the node/profile created, you need to write a hook_form_alter and disable the checkbox.

This is worked for me quite nicely.
I appreciate your feedback.

Regards.