We want to restrict some of the community's benefits for the non-registered users to push them to register.
How can we, for example, restrict for non-registered users viewing of "accepted" status for the solutions?
@Myko_P- You can restrict user from taking any action e.g reply to any post, viewing any user profile. By clicking on these action links, you can show a pop for registration or redirect user to registration page. You can get the reference from community.fitbit.com .
You also can show notification bar below the header of you community, which will have Register button and some text. Reference https://www.en.advertisercommunity.com/
You can simple hide the accepted status for the anonymous and not registered users.
<#if (!user.anonymous || !user.registration.complete)>
// your CSS here
I can't think of a built-in way to hide solutions - both the marker on the forum board page as well as the solution messages within a topic - based on a user's role. Such functionality could be created via custom components that overwrite the "solved" indicator widgets and wrap them in a role check. But before you do that I'd ike to ask:
What are the gains for the visitor - and secondarily to you as the community owner - for registering a community account? Instead of creating artificial tiers maybe you can highlight existing benefits (e.g. the ability to subscribe to topics and be notified about new replies, the ability to kudo and share feedback, the ability to reply) instead to convince your visitors to register.
Are you supporting your community's shared purpose with the drive to registrations?
You can simple hide the accepted status for the anonymous and not registered users.<#if (!user.anonymous || !user.registration.complete)>
// your CSS here
Did you mean I need to hide elements with class="solved " for the non-registered users in the Community Skin CSS?
Yes, you can hide solved class or any other element which you don't want to show to unregistered users.
There was small issue on my above code. Updated code is below.
<#if (user.anonymous || !user.registration.complete)>
Completely agree with @ClaudiusH. Even if you can accomplish this, I think you should consider the value. There is great value to you for any customer or interested party finding an answer to a problem they are experiencing with your product, or pre-purchase question, as fast as possible. Knowing that a particular reply was chosen as an Accepted Solution helps them find that answer faster. If a user comes to your community, likely through Google search assuming it is public, quickly finds an answer to their problem or question and goes away happy with your product or goes out and purchases one, it is all to your benefit. I don't think there is enough benefit of adding a registered user to interrupt that process.
Welcome to the Technology board!Curious about our platform? Looking to connect on social technology? You've come to the right place!