Content Control – Extension de restriction d’accès utilisateur

Description

Content Control est une extension légère et puissante qui vous permet de prendre le contrôle total du contenu de votre site web en restreignant l’accès aux pages/publications aux utilisateurs connectés, à des rôles utilisateur spécifiques ou aux utilisateurs déconnectés.

L’extension vous permet également de restreindre l’accès à certaines parties d’une page/publication à l’aide de codes courts, par exemple [content_control]Contenu si connecté[/content_control]

Enfin, l’extension vous permet de contrôler la visibilité de chaque widget de colonne latérale ou de pied de page en sélectionnant qui peut voir chaque widget (tout le monde, utilisateurs déconnectés, utilisateurs connectés, rôles utilisateurs spécifiques).

Liste complète des fonctionnalités

Content Control vous permet de faire ce qui suit :

  • Restrict access to pages/posts to logged in/out users or specific user roles
  • Restrict access to media attachment pages, tags, categories, format to logged in/out users or specific user roles
  • Display a custom message to users who do not have permission to view the content
  • Redirect users who do not have permission to view the content to login page (redirects back to page/post after login), website homepage or custom URL
  • Display certain content on a page/post to logged in users only
  • Display certain content on a page/post to specific user roles
  • Display certain content on a page/post to logged out users
  • Apply custom CSS classes to on page content restriction shortcodes
  • Control the visibility of each sidebar/footer widget by selecting who can view each widget (everyone, logged out users, logged in users, specific user roles).

Note: Content Control restricts access to media at the content level via the media attachment pages. Content Control does not restrict access at the server level to actual media files (e.g.: .jpg, .gif, .pdf, and .webp files).

Shortcode

This example allows only logged-in subscribers and editors to see the text « Logged in content ».

[content_control roles= »subscriber,editor » class= »custom-css-class » message= »You don’t have access to this. »]Logged in content[/content_control]

If you are logged out or aren’t logged in as a subscriber or editor, you’ll see the « You don’t have access to this. » denial message.

All parameters are optional. If you add a parameter, make sure it’s followed by an equals (=) sign and the values of your parameters are inside double quotes («  »).

List of parameters:

  • roles – By default, all roles will have access to restricted content. If you want to give access only to specific roles, add this parameter with a comma-separated list of valid WordPress user roles wrapped by double quotes («  »). See the example above.
  • logged_out= »1″ – Only logged out visitors can see this content. If you want the opposite (only logged-in people can see the content), leave this parameter out. I.e., By default, Content Control restricts content so only logged-in visitors can view it.
  • class – Add the name of your custom CSS class if you want to add custom styles to your restricted content.
  • message – Your custom denial message if you want to override the default message from the plugin settings.

Créé par Code Atlantic

Content Control is built by the Code Atlantic team. We create high-quality WordPress plugins that help you grow your WordPress sites.

Découvrez certaines de nos extensions les plus populaires :

  • Popup Maker – #1 Popup & Marketing Plugin for WordPress
  • Menu utilisateurs – Afficher ou masquer les éléments de menu pour différents utilisateurs

Nécessite WordPress 3.6 et PHP 5.3

Captures d’écran

  • Create unlimited restriction sets.
  • Choose who can see the restricted content.
  • Display a message in place of restricted content.
  • Redirect users to log in or to another page if they access restricted content.
  • Choose any content you can think of to protect.
  • Use shortcodes to protect content inline.
  • Restrict widgets as well.

Installation

Prérequis minimum

  • WordPress 3.6 or greater
  • PHP version 5.3 or greater

Installation

  • Install Content Control either via the WordPress.org plugin repository or by uploading the files to your server.
  • Activer Content Control.

If you need help getting started with Content Control please see FAQs which explains how to use the plugin.

FAQ

Where can I get support?

If you get stuck, you can ask for help in the Content Control Plugin Forum.

Where can I report bugs or contribute to the project?

Bugs can be reported either in our support forum or preferably on the Content Control GitHub repo.

Avis

2 octobre 2022
I very happy with this plugin. I need to differentiate the content between the public and the members. The use of this extension made it very easy to manage.
28 septembre 2022
I hate adding plugin after plugin to get Wordpress to do everything, so it refreshing when one just works. Once I read the documentation everything was super easy. Thank you to the developer for putting this out.
18 septembre 2022
This plugin does what it should. It gives you control over permissions and access to posts.
15 septembre 2022
This plugin is outstanding. Within minutes of installing it I was able to test it out. I protected pages and custom post types quickly. A lot of care went into the interface, and a lot of thought went into the feature set. I love it.
Lire les 388 avis

Contributeurs & développeurs

« Content Control – Extension de restriction d’accès utilisateur » est un logiciel libre. Les personnes suivantes ont contribué à cette extension.

Contributeurs

“Content Control – Extension de restriction d’accès utilisateur” a été traduit dans 7 locales. Remerciez l’équipe de traduction pour ses contributions.

Traduisez « Content Control – Extension de restriction d’accès utilisateur » dans votre langue.

Le développement vous intéresse ?

Parcourir le code, consulter le SVN dépôt, ou s’inscrire au journal de développement par RSS.

Journal

v1.1.9 – 09/30/2021

  • Fix: Error when using Gutenberg Preview.

v1.1.8 – 07/17/2021

  • Fix: Error when Elementor instance preview proptery was null.

v1.1.7 – 07/17/2021

  • Fix: Prevent warning if widget settings don’t exist in options table.
  • Fix: Arbitrary limit of 10 on current items listed in Restriction Editor due to WP query default args.
  • Fix: Prevent restrictions from activating when using the Elementor page builder.

v1.1.6 – 03/21/2021

  • Fix: Nonce validation was preventing 3rd party plugin from saving widget settings when it failed. Thanks @jacobmischka
  • Fix: Prevent corrupted options from preventing saving of settings.

v1.1.5 – 02/22/2021

  • Fix: Issue where roles with - would not save when checked.

v1.1.4 – 03/24/2020

  • Improvement: Added gettext handling for several strings that were not translatable.
  • Tweak: Process shortcodes in default denial message contents.
  • Tweak: Various improvements in form reliability & user experience.
  • Fix: Issues with ajax search fields not retaining their values after save.
  • Fix: Issue where only would show 10 pages.
  • Fix: PHP 7.4 compatibility fixes.

v1.1.3 – 12/03/2019

  • Fix: Custom post type conditions were not always registered.

v1.1.2 – 11/10/2019

  • Tweak: Remove erroneous console.log messages in admin.
  • Fix: Fatal error when empty shortcode used.

v1.1.1 – 10/15/2019

  • Fix: Bugs where variables were not always the expected type.

v1.1.0

  • Improvement: Added default denial message to shortcode.
  • Improvement: Render nested shortcodes in the [content_control] shortcode.
  • Fix: Bug where multiple roles checked together in restriction editor.

v1.0.3

  • Fix: Minor notice on activation.

v1.0.2

  • Fix: Call to undefined function.

v1.0.1

  • Fix: Non static method called statically
  • Fix: Bug when using invalid variable type.

v1.0.0

  • Initial Release