Common content restriction settings

Overview

Ultimate Member's Content Restriction allows you to manage site visibility for everyone or logged-in users globally, customize per-page or per-post access rules, and define specific restrictions and redirect behaviors for both logged-in and logged-out users, including the option to lock the homepage for certain user roles. This guide details the configurations to control access to the site and pages, which can be located at wp-admin > Ultimate Member > Settings > Access > Restriction Content.

Global Site Access

The Global Site Access feature provides that let you the flexibility to define the accessibility of your entire site with two primary options:

  • Site accessible to Everyone:

    • This is the default Global Site Access setting, allowing everyone, including non-members or users, to view all pages and posts on your site.
    • Use this option to permit non-members to access your site's content while restricting certain pages to members only.
    • The illustration below demonstrates that everyone, including logged-out users, can view the Members Page.

      • In this example, an attempt was made to restrict only the Member Page, while the global access is set to "Site accessible to Everyone." As a result, the Member Page becomes restricted while other pages remain accessible to everyone.

  • Site accessible to Logged in users:

    Note: Pages such as Login, Registration, and Password Reset cannot be restricted and are exceptions.

    • Choosing this option limits access to logged-in users only. Every page or post on your site will be available solely to users who are logged in unless you change the access rule on a particular page or post to make a page available to everyone.
    • If this option is selected, additional settings will be available:
      • Custom Redirect URL: Redirects logged-out users attempting to access restricted content to the specified URL.
      • Exclude the following URLs: Excludes specified URLs from content restrictions, allowing them to be accessible to everyone.
      • Allow Homepage to be accessible: Grants access to the homepage for everyone if enabled.
      • Allow Category pages to be accessible: Permits access to category pages for everyone if enabled.

However, it's crucial to create a designated page for non-members or logged-out users to sign up or log in when using this option. For instance, you may consider making your homepage a landing page to encourage new users to sign up. If a logged-out user attempts to access a restricted page, they will be redirected to the homepage or landing page. In the example below, we set the custom redirect URL to the login page URL. So, when a logged-out user visits a restricted page (e.g., Members page), they are redirected to the login page.

Replace the restricted post title

This option allows setting the restricted post's title for the content that isn't accessible to the visitor or current user.

  • Restricted Access Post Title

    This is the title shown to users who do not have permission to view the post. It affects the individual post page, archive post in a widget, or post link in the nav menu titles. The default title is " Restricted content"

Restricted Access Message#

This message will be shown to users who do not have permission to view the content, this will be the global default message. It can be edited visually or as HTML text.

Enable the "Content Restriction" settings for the Gutenberg Blocks

This enables the admin to set the restriction settings for Gutenberg Blocks. If enabled,the admin can enable or disable content restrictions for the Gutenberg blocks in each post.

  • Restricted Access Block Message

    • This message will be shown to users who do not have permission to view the Gutenberg block.

    • If the admin has selected Show global default message under the Restriction action in edit post/page > Block settings, the restricted access block message is displayed to logged-out users.

      • How it looks in the front end:

    • Logged-out users are not able to access or view the restricted Gutenberg block if the admin has selected 'Hide block' under the Restriction action.

      • How it looks in the front end:

Enable the "Content Restriction" settings for post types

This enables the "Content Restriction" feature for the individual posts of the selected post types.

  • If enabled, the admin can enable or disable content restriction of a post while editing, and they can also choose who can access the post with the following options: Everyone, Logged out users, Logged in users. Individual post-restriction settings are described here.

Enable the "Content Restriction" settings for taxonomies

This enables the "Content Restriction" feature for the individual terms of the selected taxonomies.

  • If enabled, the admin can manage content restriction of a taxonomy while editing. Individual taxonomy restriction settings are described here.

Related Articles