But I'm afraid this is too complex for me since i'm not a programmer.
i've got another question, for which i'm afraid your answer might be the same:
When a paying subscriber publishes a certain post type posting by entering a form, they can enter all their social media channel url's, which then will show at the front end.
But we also offer a free subscription. In that subscription i want them to be able to fill in all these url's, but it should not show on the post. (Unless they decide to buy a payed subscripttion)
I tried this with conditional fields in the post type template, But i can't find a way to hide the url when the publisher has a free subscription.
Hope you can help me out on these 2 issues / wishes.
Once you create test site using any of the reference site on your local machine or server - you can add your additional plugins or add your desired theme and check and play with that that will allow you to explore features and functionalities build on top using Toolset.
By following this path you will have hand-on experience about how you can implement the functionality.
However - at any point you can raise a ticket with where you require further help and we are happy to assist you further.
If above does not help, you can always share problem URL and admin access details with all required information and we are happy to fix the issue.
*** Please make a FULL BACKUP of your database and website.***
I would also eventually need to request temporary access (WP-Admin and FTP) to your site. Preferably to a test site where the problem has been replicated if possible in order to be of better help and check if some configurations might need to be changed.
I have set the next reply to private which means only you and I have access to it.
As you can see with the following screenshot: hidden link
I've added another conditional block and I'm checking the current user role and if current user role is not equal to "packet_1" it will display those links:
=> hidden link
Can you please confirm it works as expected.
Regarding the additional question, as per our support policy, we entertain only one question per ticket. This will help other users searching on the forum as well as help us to write correct problem resolution summery for the original issue reported.
May I kindly ask you to open a new ticket with every new question you may have with all required details.
Hi, i also figured that one out, but that is not what i mean 😉
It's not about what the USER sees, its what EVERBODY sees. So these social links and the website link, that whole block should disappear for everybody who visits the site when the author of that post has a pakket 1 user role 🙂
I've added the following shorcode to "Custom Code" section offered by Toolset:
=> hidden link
function func_get_current_post_author_role(){
global $authordata;
$author_roles = $authordata->roles;
$author_role = array_shift($author_roles);
return $author_role;
}
add_shortcode( 'get_post_author_role', 'func_get_current_post_author_role' );
I've registered the shortcode name "get_post_author_role" at:
=> Toolset => Settings and click on the "Front-end Content" tab. Look for the section called "Third-party shortcode arguments"
Then I've modified the conditional block on the following page:
=> hidden link
I've added the it as you can see with the following screenshot:
=> hidden link
Can you please confirm it works as expected:
- hidden link
thanks a lot, yes now it works!!
I don't know if you're still working on it, but i'm seeing the block recovery button again: this block contains unexpected or invalid content. On the template edit page
Ok - it will not affect functionality. I do not have any other solution to share for that as you are using third-party block inside conditional and toolset blocks.
Maybe you can create a content template and move all those blocks to that content template and then wrap the content template with the conditional block of role.
Could be possible or due to the custom function or nested conditions you have. If you do not have any issues with that you should leave at as its going to work without any issues on frontend.