Require users to accept your Terms and Conditions in several different ways:
- On signup page
- When submitting a comment
- When submitting any Formidable form
- Before accessing specified pages in the back- or front-end
In the back-end, this plugin presents all users except admins with your terms and conditions the first time they login. The Admin menu is hidden until they accept your terms if the option to require agreement on ‘All Admin pages’ is selected. Existing users and those added in the admin will also need to agree to the Terms and Conditions on their next log in. After the terms are accepted, users are presented with a fully customizable welcome message to help them get started using WordPress.
In the front-end, whether users are logged in or not, they must agree before gaining permission to view the specified page(s). If not logged in, the agreement date and initials are saved to a cookie.
- No changes need to be made to the Sign up process.
- Existing users can agree to terms.
- Users can view the terms at any time.
- The date the user agreed is displayed on the profile page with a link to the terms.
- Option to require user initials on agreement.
- Option to require terms agreement on comment form in WordPress version 2.9 and above.
- Option to clear all agreement dates when the terms are changed so users will need to reaccept terms.
- Option to show agreement date on profile.
[terms-of-use]for use in pages or posts
- Select a front-end page to protect. If user is not logged in, a cookie will be set when terms are accepted.
- Japanese (BNG NET)
terms-of-use-2folder to the
- Activate the plugin through the ‘Plugins’ menu
- Users can view the terms under the ‘Dashboard’ menu.
- Use shortcode [terms-of-use] in pages or posts to avoid duplication of content.
Colaboradores y desarrolladores
¿Interesado en el desarrollo?
Revisa el código , echa un vistazo al repositorio SVN o suscríbete al registro de desarrollo por RSS.
Registro de cambios
- Added error messages to the settings page
- Updated language files
- Don’t automatically set users as accepting terms on registration
- Don’t return error if editing Formidable entry
- Show error messages consistently when inserting in a Formidable form
- Strip slashes from agreement link so the link will work correctly
- Fixed default link from [terms_url] to [terms-url]
- Corrected language naming conventions to load language files
- Added Japanese translation (BNG NET)
- Rewrote plugin code
- Added Formidable integration
- Added option to require terms for multiple pages
- Added a PO file for translating. Please send translations to support at strategy11.com
- Added agreement date to the user listing table
- Save terms agreement to database if user is logged in when commenting
- Replaced all instances of
- Fixed bug keeping boxes checked on settings page
- Hopefully fixed parse error some users are getting
- Added functionality to the «Clear previous agreement» option, to also require users to agree again if they were not logged in when agreed (agreement saved to a cookie)
- Fixed front-end redirect to work with default permalinks
- Simplified front-end terms requirements with a page drop-down in the admin settings, and auto content if the page is blank.
- Added option to require terms on comment form
- Updated instructions for admin menu selected
- Fixed registration page error… again
- Fixed bug preventing terms agreement checkbox to show on WP registration page
- Removed code causing signup issue in WPMU
- Added Profile page as an option on admin pages to protect
- Fixed admin redirect bug
- Fixed redirect after terms accepted on WPMU front-end
- Bug fix for ‘header information already sent’ bug some users reported
- Fixed bug that overwrote custom options on plugin update.
- Added shortcode for use of terms in pages or posts.
- Added option to allow users to accept terms during signup. Known to not save correctly in WPMU.
- Changed date format for profile page to the format selected on Settings > General
- Added option to select which admin page to protect
- Added option to select which front-end page to protect
- Added ‘Settings’ link on the plugins page
- Added option to require initials on agreement page
- Moved ‘Welcome’ heading from code to database
- Fixed plugin subnav links
- Fixed WPMU bugs with link urls.
- Fixed folder name in config file.