Requiring the user to agree to terms & conditions on registration and change of conditions is a good start, but I want our user to also check some conditions when submitting content to the site. The attached patch does provide this ability:
- a global text for content submission terms
- a checkbox for every content type to enable requiring the acceptance on content submission
- a permission to not bother administrative users with the terms and conditions
Comments?
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | legal-content-terms-3.patch | 8.63 KB | ray007 |
| #1 | legal-content-terms-2.patch | 6.17 KB | ray007 |
| legal-content-terms-1.patch | 5.5 KB | ray007 |
Comments
Comment #1
ray007 commentedThere doesn't seem to be much interest in this patch, but here's the next generation:
you now can have different terms & conditions per content type.
Maybe now some comments?
Comment #2
robert castelo commentedAll sound like good features.
Looking forward to reviewing this as time allows.
Many thanks for contributing back.
Comment #3
ray007 commented*Bump*
anything wrong with my patch?
Comment #4
robert castelo commentedApologies Ray, nothing wrong with your patch, in fact it sounds excellent - just haven't had time to review it yet.
Comment #5
ray007 commentedNew version with minor enhancement, now we also have "print" links to show terms & conditions in their own window.
Hope you find time to have a look at it ;-)
Comment #6
ddyrr commentedThis is so freakin awesome! Just what I needed! I have a content type that is actually another type of account, and they need to accept a different terms of use if they wish to create one or more of these accounts. THANK YOU!!
Comment #7
ddyrr commentedThe only other thing that would be great to have in this patch would be an optional name. Since the content type terms of use may be different from the main one, it would be great to be able to provide a name that could either be displayed just before "Terms & Conditions" title, or in place of it. For example, I could name one of the terms forms the "My content type Terms & Conditions".
Comment #8
ddyrr commentedI don't know how to make a patch for this, but I was able to create an easy workaround by simply querying node_type for the name based on either arg(1) (for the print version), or the $form['type']['#value'] as the type. This gives the name of the node type, so you can print something like "Node type Terms & Conditions" for all content types.
Comment #9
dardia commentedI'll second the support for this patch. It performs a very useful function for me.
Comment #10
robert castelo commentedFinally got round to reviewing....
I like the feature ideas here, but not the implementation.
There's no record of which version of the content type T&C the user has accepted. Also once the T&C has been accepted it shouldn't be necessary to accept it again when you edit the node.
Variables are not properly named, e.g. $v, $nt,$c....
Also because a few different features have been put together in one patch, it's difficult to review them individually - always create a new issue for each feature and provide one patch per feature.
I'm currently working on Legal for Drupal 6, will look at adding these features once that's released.
Comment #11
kwgossett commentedHi Ray,
What you've created, is a close cousin to something I've asked for on several occasions - acceptance to a liability waiver each time an event is registered for. You can read a bit more on the Legal module's feature request. http://drupal.org/node/242301
Robert has apparently reviewed your patch, and made some suggestions to clean up the implementation. If either of you could take a look at the feature request above, and adapt the work you've done on the legal module to a waiver module, that would be hugely appreciated! :)
Kelly
Comment #12
Turkish Delight commentedDoes anything like this exist for an unauthorized user to view a node?
Comment #13
zilla commentedthis should be in drupal core!!!
drupal core includes an upload module but NO way to make users confirm that they have permission to upload whatever it is they're uploading.
imho this is not a responsibility for the legal module, it is a drupal core issue.
t&c has always been on my mind as a drupal core issue, or at least an element of COPPA compliance, but this appears to not be on the priority list for what is considered core functionality.
just my two cents.
Comment #14
halisemre commentedanyone has this for d 6
Comment #15
wqmeng commentedThe feature is very useful, while patch of #5 don't work with the latest 6.x-2.2-beta4.
Comment #16
dangriff commentedHi all this is just what i have been looking for!! sorry to say i am a newbee to php and alittle advice on where to put this code wouldbe great.. thanks in advance,
Dan
Comment #17
teflo commentedIs there a version for the legal 6.x-8.2?
Comment #18
ipwa commentedMarking #242301: Adapt legal Module for liability waiver & #282149: Attach legal to any content type as duplicates. If any patches are submitted for this, they should preferably be for 7.x.