• Resolved jmax

    (@jomansor)


    I want to hide posts made by members Their role (um_custom_role_1) and show them to other users role (um_custom_role_2) and the member who posted them only.

    Because if I activate Content Restriction And display content only for (um_custom_role_2) The content does not appear to the content owner Because he is (um_custom_role_1).



Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support yuriinalivaiko

    (@yuriinalivaiko)

    Hello @jomansor

    The post author can access the post regardless of the Content Restriction settings for the post.

    The content owner who is (um_custom_role_1) should see the post if the post setting “Who can access this post?” is set to “Logged in users” and the “Select which roles can access this post” setting is set to other users role (um_custom_role_2).

    Regards

    Thread Starter jmax

    (@jomansor)

    It works on the condition that I activate option to redirect to an external link, and if I make a restrict message appear to the user, the message will be on the header only, The rest of the content will appear normally

    Note that I use the directory plugin ( directorist ), which allows the user to publish his own lists.

    Plugin Support yuriinalivaiko

    (@yuriinalivaiko)

    This may be because of a plugin conflict. Can you do a conflict test and see if the issue goes away? This doc explains how to do a conflict test:?How to do a plugin/theme conflict test??Can post authors access their own posts if the directory plugin is deactivated?

    Take a screenshot of the post Content Restriction settings and the post view at frontend if you can not solve a problem.

    Regards

    Plugin Support andrewshu

    (@andrewshu)

    Hi @jomansor

    This thread has been inactive for a while so we’re going to go ahead and mark it Resolved.

    Please feel free to re-open this thread if any other questions come up and we’d be happy to help. ??

    Regards

Viewing 4 replies - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.