Hi,

can you please provide URL to the page where we can see this issue?

Hi Igor.
Thanks for your answer.
The page is http://meal.creaweb38.fr/a-faire
I have written explanation comments on the site to illustrate what seems to be a bug.

Hi,

I have assigned the ticket to our developer so he can comment on this

Thank you very much.
Does the developer need to access to my website ?
(The website is normally not accessible, at the request of the person for whom I develop it)

Hi.
I have no news from the developer.
Do you know if someone is working on this issue ?

Up ?

Hi,

I apologise for not replying sooner. I just remind the developer to take a look and reply back. I guess that this ticket fell out of his radar somehow

Hey there Myster Dog

At first I was - "wasn't that bug been fixed already" and after looking into the code - yes it is resolved long time ago.

// Use the entered name in the comment
$name = $comment->name;

// If the username is logged in, then use either real or user name
if ($comment->userid)
{
$name = $config->get('layout.use_name', 0) ? $comment->user_realname : $comment->user_username;
}

You said that "use names" is disabled in your settings. Are you using ccomment Core or PRO? In the pro version one is able to change this setting and you would see the user's real names in the comments.

Regards,
Daniel

Hello Daniel.

Thanks for your answer.
I'm using CComment Core.

I've noticed that in comment.json.php :

// If the username is logged in, then use either real or user name

if ($comment->userid)

{

	$name = $config->get('layout.use_name', 0) ? $comment->user_realname : $comment->user_username;

}

whereas in comment.php :

if ($comment->userid)

{

	if ($config->get('layout.use_name', 1))

	{

		$json[$key]->name = $comment->user_realname;

	}

	else

	{

		$json[$key]->name = $comment->user_username;

	}

}

Is it normal to have $config->get('layout.use_name', 1) in comment.php (and not $config->get('layout.use_name', 0) as in comment.json.php) ?

Hi Daniel.

Did you have some time to look at my issue since my last post ?

what happens if you change it to 0? Is it working as you want it?

Yes.

The bug comes from this little mistake (and that's the reason why I told you to look at this difference).
The error is in components/com_comment/helpers/comment.php on line 84.

I thought you would change it...

If I change it on my side, the error will recur at the next update...

fix added. So you are safe to update that file. Next version will contain the change.

The problem comes from the fact that you are using the core version and the settings in the core version is disabled. So, once you click save - no value is stored for this option. And then since we set the value to 1 there, we end up in the wrong if.

If you were using the pro version you wouldn't run into that because a value of 0 would be stored for the option.

Anyway, now it will work correctly in core as well. Thanks for the help!

Thanks for your explanation!
Have a nice end of day