| 1 |
=== Content Control - The Ultimate User Access Restriction Plugin === |
| 2 |
Contributors: codeatlantic, danieliser |
| 3 |
Author URI: https://code-atlantic.com/?utm_campaign=upgrade-to-pro&utm_source=plugins-page&utm_medium=plugin-ui&utm_content=action-links-upgrade-text |
| 4 |
Plugin URI: https://contentcontrolplugin.com/?utm_campaign=plugin-info&utm_source=readme-header&utm_medium=plugin-ui&utm_content=author-uri |
| 5 |
Donate link: https://code-atlantic.com/donate/?utm_campaign=donations&utm_source=readme-header&utm_medium=plugin-ui&utm_content=donate-link |
| 6 |
Tags: access control, content, content restriction, permission, private, restrict, restrict access, restriction, user, visibility, widget |
| 7 |
Requires at least: 5.6 |
| 8 |
Tested up to: 6.3.1 |
| 9 |
Stable tag: 2.0.4 |
| 10 |
Requires PHP: 5.6 |
| 11 |
License: GPLv3 or Any Later Version |
| 12 |
|
| 13 |
Unleash your WordPress content's potential! With Content Control, restrict your content, pages, posts, widgets, and even individual blocks with precision, based on user status, roles, device type & more. |
| 14 |
|
| 15 |
== Description == |
| 16 |
|
| 17 |
Content Control v2.0 is a transformative plugin, enabling you to fine-tune every aspect of your WordPress website's content. Dictate who sees what, where and when - whether it's pages, posts, widgets, using our shortcode, or even individual blocks. Your content, your rules, executed with precision! |
| 18 |
|
| 19 |
Content Control is user-friendly, yet powerful, catering to logged in users, specific user roles or logged out users. Our controls even extend to the block level, providing unparalleled control for Gutenberg and Full Site Editor users. |
| 20 |
|
| 21 |
= Key Features = |
| 22 |
|
| 23 |
Content Control is packed with features that allow you to: |
| 24 |
|
| 25 |
- Full control over your sites content, pages, posts, widgets, and even individual blocks. |
| 26 |
- Per block controls for Gutenberg and Full Site Editor, including user roles, device type, and more. |
| 27 |
- Restrict access to pages, posts, widgets, and individual blocks based on user status, roles, device type & more. |
| 28 |
- Manage access to [media attachment pages](https://www.hongkiat.com/blog/wordpress-attachment-pages/), tags, categories, formats for logged in/out users or specific user roles. |
| 29 |
- Display a custom message to users who do not have permission to view the content |
| 30 |
- Redirect users without access permission to a login page, website homepage, or a custom URL. |
| 31 |
- Display specific content on a page or post to logged in users only, specific user roles, or logged out users. |
| 32 |
- Use the `[content_control]` shortcode to protect content inline. |
| 33 |
- Control widget visibility by selecting the user type that can view each widget. |
| 34 |
|
| 35 |
[Content Control Documentation](https://contentcontrolplugin.com/docs/?utm_campaign=plugin-info&utm_source=readme-description&utm_medium=wordpress&utm_content=documentation-link) |
| 36 |
|
| 37 |
**Note: Content Control restricts media access at the content level via media attachment pages. It does not restrict server-level access to actual media files (e.g.: .jpg, .gif, .pdf, .webp files).** |
| 38 |
|
| 39 |
= Brought to You by Code Atlantic = |
| 40 |
|
| 41 |
Content Control is a [Code Atlantic][codeatlantic] product. We pride ourselves on creating high-quality WordPress plugins designed to help your WordPress sites thrive. |
| 42 |
|
| 43 |
Explore some of our most popular plugins: |
| 44 |
|
| 45 |
- **[Popup Maker][popupmaker]** - #1 Popup & Marketing Plugin for WordPress |
| 46 |
- **[User Menus][usermenus]** - Show, Hide & Customize Menu Items For Different Users |
| 47 |
|
| 48 |
[codeatlantic]: https://code-atlantic.com "Code Atlantic - High Quality WordPress Plugins" |
| 49 |
[popupmaker]: https://wppopupmaker.com "#1 Popup & Marketing Plugin for WordPress" |
| 50 |
[usermenus]: https://wordpress.org/plugins/user-menus/ "Show, Hide & Customize Menu Items For Different Users" |
| 51 |
|
| 52 |
== Installation == |
| 53 |
|
| 54 |
- Install Content Control either via the WordPress.org plugin repository or by uploading the files to your server. |
| 55 |
- Activate Content Control. |
| 56 |
|
| 57 |
If you need help getting started with Content Control please see [FAQs][faq page] which explains how to use the plugin. |
| 58 |
|
| 59 |
[faq page]: https://wordpress.org/plugins/content-control/faq/ "Content Control FAQ" |
| 60 |
|
| 61 |
== Frequently Asked Questions == |
| 62 |
|
| 63 |
= Where can I get support? = |
| 64 |
|
| 65 |
If you get stuck, you can ask for help in the [Content Control Plugin Forum](http://wordpress.org/support/plugin/content-control). |
| 66 |
|
| 67 |
= Where can I report bugs or contribute to the project? = |
| 68 |
|
| 69 |
Bugs can be reported either in our support forum or we are happy to accept PRs on the [Content Control GitHub repo](https://github.com/code-atlantic/content-control/issues). |
| 70 |
|
| 71 |
== Screenshots == |
| 72 |
|
| 73 |
1. Restrict access to individual blocks. |
| 74 |
2. Create unlimited restriction sets. |
| 75 |
3. Choose who can see the restricted content. |
| 76 |
4. Display a message in place of restricted content. |
| 77 |
5. Redirect users to log in or to another page if they access restricted content. |
| 78 |
6. Choose any content you can think of to protect. |
| 79 |
7. Use shortcodes to protect content inline. |
| 80 |
8. Restrict widgets as well. |
| 81 |
|
| 82 |
== Changelog == |
| 83 |
|
| 84 |
= v2.0.4 - 09/18/2023 = |
| 85 |
|
| 86 |
- Fix: Error when WP Query vars include anoymoush function closures. |
| 87 |
|
| 88 |
= v2.0.3 - 09/18/2023 = |
| 89 |
|
| 90 |
- Fix: Log errors instead of throwing exceptions to prevent uncaught exceptions turning into fatal errors. |
| 91 |
|
| 92 |
= v2.0.2 - 09/18/2023 = |
| 93 |
|
| 94 |
- Fix: Fatal error from error logger on systems without write access. |
| 95 |
|
| 96 |
= v2.0.1 - 09/17/2023 = |
| 97 |
|
| 98 |
- Fix: Fatal error from unregistered or unknown rule types from 3rd party plugins/themes or custom code. Now they are logged in plugin settings page. |
| 99 |
|
| 100 |
= v2.0.0 - 09/17/2023 = |
| 101 |
|
| 102 |
- Feature: Restrict individual blocks in the Gutenberg editor. |
| 103 |
- Feature: Restrict individual blocks in the Full Site Editor. |
| 104 |
- Feature: Use a custom page template for restricted content. |
| 105 |
- Feature: Restrict blocks by device type with customizable breakpoints. |
| 106 |
- Feature: Restrict blocks by user status & role. |
| 107 |
- Feature: Global restrictions now offer more control over how restricted content is handled. |
| 108 |
- Choose to redirect or replace content with a custom page. |
| 109 |
- Filter or hide posts in archives or custom loops. |
| 110 |
- Secondary controls for posts if found in an archive. |
| 111 |
- Improvement: Match or exclude specific roles. |
| 112 |
- Improvement: Updated interface with intuitive and responsive controls. |
| 113 |
- Improvement: Boolean editor improvements. |
| 114 |
- Improvement: Control who can modify plugin settings. |
| 115 |
- Improvement: Upgraded tooling & Code quality improvements. |
| 116 |
|
| 117 |
= v1.1.10 - 12/28/2022 = |
| 118 |
|
| 119 |
- Security: Fix unescaped output for CSS classname in the [contentcontrol] shortcode allowing users with the ability to edit posts to inject code into the page. |
| 120 |
|
| 121 |
= v1.1.9 - 09/30/2021 = |
| 122 |
|
| 123 |
- Fix: Error when using Gutenberg Preview. |
| 124 |
|
| 125 |
= v1.1.8 - 07/17/2021 = |
| 126 |
|
| 127 |
- Fix: Error when Elementor instance preview proptery was null. |
| 128 |
|
| 129 |
= v1.1.7 - 07/17/2021 = |
| 130 |
|
| 131 |
- Fix: Prevent warning if widget settings don't exist in options table. |
| 132 |
- Fix: Arbitrary limit of 10 on current items listed in Restriction Editor due to WP query default args. |
| 133 |
- Fix: Prevent restrictions from activating when using the Elementor page builder. |
| 134 |
|
| 135 |
= v1.1.6 - 03/21/2021 = |
| 136 |
|
| 137 |
- Fix: Nonce validation was preventing 3rd party plugin from saving widget settings when it failed. Thanks @jacobmischka |
| 138 |
- Fix: Prevent corrupted options from preventing saving of settings. |
| 139 |
|
| 140 |
= v1.1.5 - 02/22/2021 = |
| 141 |
|
| 142 |
- Fix: Issue where roles with `-` would not save when checked. |
| 143 |
|
| 144 |
= v1.1.4 - 03/24/2020 = |
| 145 |
|
| 146 |
- Improvement: Added gettext handling for several strings that were not translatable. |
| 147 |
- Tweak: Process shortcodes in default denial message contents. |
| 148 |
- Tweak: Various improvements in form reliability & user experience. |
| 149 |
- Fix: Issues with ajax search fields not retaining their values after save. |
| 150 |
- Fix: Issue where only would show 10 pages. |
| 151 |
- Fix: PHP 7.4 compatibility fixes. |
| 152 |
|
| 153 |
= v1.1.3 - 12/03/2019 = |
| 154 |
|
| 155 |
- Fix: Custom post type conditions were not always registered. |
| 156 |
|
| 157 |
= v1.1.2 - 11/10/2019 = |
| 158 |
|
| 159 |
- Tweak: Remove erroneous console.log messages in admin. |
| 160 |
- Fix: Fatal error when empty shortcode used. |
| 161 |
|
| 162 |
= v1.1.1 - 10/15/2019 = |
| 163 |
|
| 164 |
- Fix: Bugs where variables were not always the expected type. |
| 165 |
|
| 166 |
= v1.1.0 = |
| 167 |
|
| 168 |
- Improvement: Added default denial message to shortcode. |
| 169 |
- Improvement: Render nested shortcodes in the [content_control] shortcode. |
| 170 |
- Fix: Bug where multiple roles checked together in restriction editor. |
| 171 |
|
| 172 |
= v1.0.3 = |
| 173 |
|
| 174 |
- Fix: Minor notice on activation. |
| 175 |
|
| 176 |
= v1.0.2 = |
| 177 |
|
| 178 |
- Fix: Call to undefined function. |
| 179 |
|
| 180 |
= v1.0.1 = |
| 181 |
|
| 182 |
- Fix: Non static method called statically |
| 183 |
- Fix: Bug when using invalid variable type. |
| 184 |
|
| 185 |
= v1.0.0 = |
| 186 |
|
| 187 |
- Initial Release |
| 188 |
|
