So you have post before register switched on in System>Settings>Posting & Editor?

You probably have the Post Before Registering setting enabled. It allows guests to reply, but they have to register/validate an account before the comment appears:

Allowed where Members group can post

Guests will see the ability to submit content and then will immediately be prompted to register an account before the content is actually submitted and viewable. This is useful for encouraging guests to register.

Guest users will have up to one week to complete their registration before their content will be permanently removed. If the guest user does not complete their registration immediately, they will be sent a reminder email shortly after making the post.

Edited February 26Feb 26 by teraßyte
typo

thanks both, i switched that off previously when was investigating:

Thats is probably what was causing it in that case. Im assuming you can no longer post as guest now?

 

Thats is probably what was causing it in that case. Im assuming you can no longer post as guest now?

sorry, I mean I switched this off before while investigating the issue.

Guests can still post

We would need to look further into this for you, however the access details on file appear to be incorrect or missing. Could you please update these details by visiting your client area, selecting the relevant purchase, then clicking "Review/Update Access Information" under the "Stored Access Information" section. 

We look forward to further assisting you. 

thanks updated the board and SFTP login details

Hi there, I also realized I have the same issue, that Guests can comment on Blog posts despite that "post before register" is switched off. Would be great to have this fixed (spam risk!)

not sure how these are triaged. Ive had to update the code so no longer present on my site. I was having 100+ comments a day.

\applications\blog\sources\entry\entry.php | 813

	else if(!$member->member_id)
	{
		return FALSE;
	}

Thank you for bringing this issue to our attention! I can confirm this should be further reviewed and I have logged an internal bug report for our development team to investigate and address as necessary, in a future maintenance release.

This has already been fixed for 5.0.4.

 

This has already been fixed for 5.0.4.

Can not see 5.0.4 on my client area?

 

Can not see 5.0.4 on my client area?

You wont be able to. Its not out quite yet :)

nice work!

 

This has already been fixed for 5.0.4.

This bug still exists for me. Version 5.0.6.

Could you please check to ensure you dont have anything like post before register switched on?

Hi Marc! Post before registering is disabled. I should mention that this is a self-hosted installation.

We would need to look further into this for you, however the access details on file appear to be incorrect or missing. Could you please update these details by visiting your client area, selecting the relevant purchase, then clicking "Review/Update Access Information" under the "Stored Access Information" section. 

We look forward to further assisting you. 

Thanks Marc!

I think the problem in my case is that the system returns TRUE for Group::load( Settings::i()->member_group )->g_blog_allowcomment despite the check box for Can comment on blog entries? under the blog area in settings for Members->Guests is disabled. Therefore line 811 in entry.php return (bool) Group::load( Settings::i()->member_group )->g_blog_allowcomment; returns TRUE where it should return FALSE.

Have you tested this on the latest beta at all? I know there have been permission issues resolved on the latest upcoming release

No, will install the beta now and get back to you.

Thanks Marc for the suggestion!

The bug still exists for me on the latest beta. I have tried switching languages and themes as well with no success. Previously I was on another host and under another domain name and I have manually moved the installation so it might be a problem limited to my installation. If no one else is experiencing issues I'm starting to believe that that is the case and I am happy with commenting out line 811 in entry.php and manually returning FALSE instead.

Doesnt appear this is just you, and have reopened the bug report

Ok I have updated the information under the Review/Update Access Information. Do you want me to restore Entry.php to its original state for now?

Not needed. A bug report has been added, so it will just be updated in a future release