Choose in the template setting Display Social Share = Yes
Visit your Forum as guest
Expected behavior
Social Share should be available
Actual result
Guests can't see the buttons
Additional context
But when we make Social Share available to guests, then makes the profile setting "Social Share - Yes or No" no sense.
As soon as a member log out, the Social Share buttons are back, also if in their profile is set "Social Share - No".
My opinion, it is the task of the website operator to inform his users about privacy (GDPR) and to define if there are Social Share on his website or not.
System information (please complete the following information)
Joomla version: 3.8.10 and 3.8.11-dev
Kunena version: 5.1.2-dev
Php version: 7.0.25 and 7.2.1
Database version:
Desktop (please complete the following information):
OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]
Smartphone (please complete the following information):
Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]
The text was updated successfully, but these errors were encountered:
Describe the bug
https://www.kunena.org/forum/general-questions-and-how-tos/153355-social-share-buttons
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Social Share should be available
Actual result
Guests can't see the buttons
Additional context
But when we make Social Share available to guests, then makes the profile setting "Social Share - Yes or No" no sense.
As soon as a member log out, the Social Share buttons are back, also if in their profile is set "Social Share - No".
My opinion, it is the task of the website operator to inform his users about privacy (GDPR) and to define if there are Social Share on his website or not.
System information (please complete the following information)
Joomla version: 3.8.10 and 3.8.11-dev
Kunena version: 5.1.2-dev
Php version: 7.0.25 and 7.2.1
Database version:
Desktop (please complete the following information):
Smartphone (please complete the following information):
The text was updated successfully, but these errors were encountered: