Black Friday: 30% OFF on all plans, applied automatically at checkout View plans
Log in Cart

Pages by User Role for WordPress Changelog

Every recorded version, newest first, with what changed in each one.

Latest 1.7.2.10111915 versions

Undated · 15 versions

  1. 1.7.2.101119

    Latest
    1 new
    New
    • New Feature: Add always Allow Usernames and always Disallow Usernames access control. Access by username has higher priority than access by user role.
  2. 1.7.1.10456

    1 new
    New
    • New Feature: Added support for allowing specific usernames to login. Is useful if you need to perform maintenance on your website and only want specific users to access your website (wp-admin).
  3. 1.7.0.10317

    3 new1 fix1 change
    New
    • New Feature: Added an option to hide a post (custom post type) from the frontend, but continue to show in wp-admin, Ajax, and REST API. Use case: Hiding a course from the frontend of the website, but still showing the course inside the BuddyBoss App.
    • New Feature: Added Integrations tab to Settings. Allows the Administrator to toggle ON/OFF the hide in frontend setting in the Access Control metabox.
    • New Feature: Added status message in post list (Access Control column)
    Fixed
    • Bug Fixed: When a role is blocked from the front page, WooCommerce checkout Ajax crashes.
    Changes
    • Version: 1.6.5.100179 - October 29, 2021
  4. 1.6.4.99097

    1 new
    New
    • New Feature: Restrict an entire Post Type by User Role. This will ignore the option to allow non-logged in users access to restricted content. If the user role has access to the post type, other restrictions may still apply. Like when individual settings are set for an individual Post Type.
  5. 1.6.3.99091

    1 new
    New
    • New Feature: Access to wp-admin by User Role.
  6. 1.6.2.98892

    1 new1 improvement
    New
    • New Feature: Set homepage by User Role
    Improved
    • Use properly escaping in PHP
  7. 1.6.0.98592

    4 new3 improvements
    New
    • New Feature: Added new React based Options Panel to the plugin.
    • Added new updated .pot file for translation (English)
    • Added support for custom redirect Url when using Forced Login.
    • Added support for using wildcard /* in Forced Login white list.
    Improved
    • Converted all old features from Options Panel to new React based Options Panel
    • Used "strict mode" for all Javascript.
    • Removed empty folders
  8. 1.5.1.98183

    1 fix
    Fixed
    • Bug Fixed: Forced Login was causing the user to enter password twice.
  9. 1.5.0.97742

    4 new1 fix
    New
    • New Feature: Forced Login. Make your website completely private
    • New Feature: White-list Pages, Posts, and Custom Post Types (Always Visible) even though you have enabled the Forced Login feature
    • New Feature: White-list URLs. This is useful if you want to white-list e.g. archives and categories when the Forced Login feature is enabled.
    • New Feature: Added support for settings a specific front-page for users not logged in and a front-page for users logged in. This feature can be used with or independently of the Forced Login feature.
    Fixed
    • Bug Fixed: Block access to a Taxonomy term archive page
  10. 1.4.7.97641

    1 improvement
    Improved
    • Compatibility Fix: Javascript error in Options Panel after upgrading to WordPress 5.5.
  11. 1.4.6.96524

    1 improvement
    Improved
    • Added support for restricting access to Pages added to WooCommerce > My Account when using the WooCommerce Account Pages plugin
  12. 1.4.5.86663

    1 improvement
    Improved
    • Styling improvements in Options Panel
  13. 1.4.4.83225

    2 fixes
    Fixed
    • Bug Fixed: PHP warning in the frontend
    • Bug Fixed: PHP warning on IIS server
  14. 1.4.3.82846

    1 improvement
    Improved
    • Compatibility Fix: Pages by User Role caused the content of blog posts on some websites to be hidden when using WordPress Notification plugin and Pages by User Role.
  15. 1.4.2.82096

    1 fix
    Fixed
    • Bug Fixed: When blocking access to a Page for one specific User Role and allowing users that are not logged in to access the page, the remaining user roles were blocked. This was related to the new feature we just introduced.

Changelog published by the developer, in their original language.