Mist is correct about the permissions issues and viewing comments. You can see an example of this here: http://test.peakbeta.com/trip-report/test3

I think it's related to the fact that there is no privacy setting to allow public comments as seen here:

Thanks for sharing Josh

Thanks for replying Mark.
Comments accessibility ("read" permissions for general public) it's a big issue for me because i am using EasySocial comments integrated in Joomla article and everything must be "read" by the public

Hey Mist,

I guess the only way is for you to not allow users to change their privacy but I really don't reckon doing that. If the user doesn't want their comments to be seen publicly, you are already going against their privacy and it would probably make them furious?

My users can't change their privacy, i don't use EasySocial as a "regular" social network community
The privacy settings remains the way i set-up them in EasySocial backend, the user can't change them.

As Josh mentioned above, in EasySocial backend there is no "Everyone" privacy settings for EasySocial comments, so i can't setup the comments to be "read" by everyone

Then you will need to hack your own set of customizations to make this happen

Cool , would help me a lot some instructions on how to do it.

Maybe for the upcoming releases, if you have some time, you guys can fix this with an "everyone" privacy settings for EasySocial comments.
There is no point into allowing EasySocial comments integration with public Joomla Articles, if comments can't be read by general public.

Thanks a lot Mark !

Sorry but unfortunately we will not be able to provide support for customizations

I would need only some hints on what code / file to change ... and i will have my programmer look into it.

The file responsible to handle comments is in /administrator/components/com_easysocial/includes/comments/comments.php

Mark wrote:

If the user doesn't want their comments to be seen publicly, you are already going against their privacy and it would probably make them furious?

The user does not have the freedom of choice for making their comments public under the current system. Most of the Privacy Options have an option to show to "Everyone". Even Messages and Post Story have an option to allow anyone to do those actions!



A user is much more likely to want their comments public than for non registered users to be able to send them a message. By forcing the comments to be hidden from the public, we removed the visual feel of an active community in our articles to those who potentially may join our site. In addition to this, scenarios arise such as if a user wanted to see comments on their featured article but did not want to login due to not wanting their cookies to be stored on someone else's devise. And of course it's a convenience thing. The easier it is to access content (when appropriate), the better the user experience is going to be.

By allowing things to be public, you let your potential users get a better feel of what the site is like.

Yep, i agree with Josh on this. This thing it's a glitch within EasySocial.
Basically it lacks the "Everyone" privacy settings for EasySocial comments "read/view"
(other areas have this setting available, maybe it was missed to be added for comments aswell ... too much coffee ).

Without having the option to make the comments "visible" for guests, our joomla articles will not have basically any comments shown at all and this is really bad

We'll see what we can do for this in the future

Mark, are you sure that the file responsible for hidding comments for visitors/guests is this ?

/administrator/components/com_easysocial/includes/comments/comments.php

I inspected the file and it seems that this is handling other comments stuff like comments deleting and so on.
Basically, i just want to add a small hack to just enable comments "viewing" for everybody.

It starts from there

And where it ends ? )))) If you can be more specific i can have my programmer make the necessary modifications.
Without proper guidance he will search for the needle in the haystack, taking a lot of time to debug it.

Thx !

Well he / she should look at the codes and try to search for it