The modules forces every user to reconfirm the legal bit every time a change is made. While this makes sense, it would be useful to control this - e.g. if you have a spelling mistake and fix it it's unreasonable that every user will have to accept again...

For the terms & conditions I'm using HTML with links to my terms & to the privacy policy. There's no other way since there's only a possibility for one document... I need two. The checkboxes are not good enough because I can't just have 2 of those without the "main" checkbox.

And if you could have the text/terms/link come up in a pop-up window... But that's no big deal.

Thanks.

Comments

Athaclena’s picture

Well, since I wanted this for my site anyway I went and hacked legal to do this. I brutally removed all of legal_user but the register case, I made the main terms text-box not required and disabled the validation on it and removed the main check box.

All that it does now is shows 2 checkboxes (configures as extra checkboxes) at register, both required. I really hope I haven't broken anything - it doesn't look like it. I'd appreciate any input in any case.
Thanks!

robert castelo’s picture

Status: Active » Closed (works as designed)

My concept for this module is that T&Cs are permanent once committed, down to comas and spaces - what the user is presented with is exactly what they signed off on, and will not be changed in any way at a later date unless they sign it as a new version (just like a paper version).

So I'm not going to implement this request.

I'm actually interested in taking this further by generating a checksum and a downloadable version of the T&Cs.

Athaclena’s picture

Fair enough. It's just that I personally had a spelling mistake (or wrong comma or something) and this way looks like slight overkill in that case.

Thanks for answering.

How about the other part of my request? If I need 2 separate documents for the user to accept? At the moment you either have to link to them both in the HTML box or have one in a box and one as a checkbox - but both (or even more) could be equally important. In my case a terms & conditions and a privacy policy...
Either having 2 text boxes or an ability to leave the text box empty could help in this case.

Rachel

robert castelo’s picture

This is why it's important to separate out each feature requests into their own issue.

I've started the discussion on this one over here:

http://drupal.org/node/290547