Disable Certain Comment Via Phpmyadmin?

wiguna · January 15, 2018, 10:03pm

Ojs Comment section is overwhelming by spam poster, while some of them are indeed “real” Legit Comment but 80% Comment on my Journal Site is just plain Spam

Admin rarely checking up the comment section, one thing they knew is overwhelming database size, i knew we can turning off comment via admin dashboard but how do i do this via PHPmyadmin

and is it possible when we disable comment, it doesn’t effect globally… i mean some of them are legit Comment and some time important one therefore its hard to decide…keeping spam or Legit comment

Thanks

vvucic · January 15, 2018, 10:07pm

First of all, you and your admin should investigate why there is so much spam.
Which version of OJS you use?

wiguna · January 15, 2018, 10:16pm

its still using 2.4.2.0,i think we don’t need that . it obvious there only two choice, allowed Comment or Disable completely …

if we allowed comment then there is no some kind of filter, the captcha is almost no use it easy to bypass…user simply just need to register and post their comment…no moderation after that

ctgraham · January 16, 2018, 2:22pm

The next upcoming release of OJS 2.x (either 2.4.8-3 or 2.4.9) will have support for ReCAPTCHA v2, which though imperfect is much better than CAPTCHA and the legacy ReCAPTCHA.

asmecher · January 16, 2018, 10:24pm

Hi all,

Note that I’ve just released OJS 2.4.8-3 – it’s available on the download page. It includes support for the newer ReCaptcha API.

Regards,
Alec Smecher
Public Knowledge Project Team

wiguna · January 17, 2018, 9:16am

hi graham, sweet looking for that, anyway what is the sql command to turn off reading tool comment via PHPmyadmin or direct from database

we have so many installation of OJS ,sometime is much faster if we site manager execute this from database instead of journals admin loggin via web dashboard

wiguna · January 17, 2018, 9:29am

Hi asmecher

This is great news, i hope The Recaptcha V2 can at least stop the automated spamming tool

but if i can make suggestion ,perhaps in next release maybe The OJS TEam can consider to make the comment section nofollow ? its just a suggestion , perhaps to combat spam it to understand what is the purpose of them doing that

after studying their behavior it seems their only goal is only after Follow links (to acumulate pagerank) and trying to manipulate the search engine (as article comment section is in default indexed and followed by search engine)

if we analyze server logs, only small percent of this spam is done by automated bot (at least on our server) the rest of them are doing by hand ( real human visitor)

ctgraham · January 17, 2018, 1:40pm

All untrusted links on this forum are marked nofollow, and yet we still regularly delete spam posts on this site. I don’t think the abusers bother to consider that the links are nofollow.

That said, if you wanted to append a rel="nofollow" to links in your comments, you could make that change here:

github.com

pkp/ojs/blob/143e794ad8c671ab3c20bf501c75069863dc1902/templates/comment/comments.tpl#L74



	{if $isManager}
		{if $hasPriorAction}&nbsp;|&nbsp;{/if}
		<a href="{url op="delete" path=$articleId|to_array:$galleyId:$comment->getId()}" {if $comment->getChildCommentCount()!=0}onclick="return confirm('{translate|escape:"jsparam" key="comments.confirmDeleteChildren"}')" {/if}class="action">{translate key="comments.delete"}</a>
		{assign var="hasPriorAction" value=1}
	{/if}

	<br />
	</p>

	{$comment->getBody()|strip_unsafe_html|nl2br}

<br /><br />

<div class="separator"></div>

{if $comments}<h3>{translate key="comments.replies"}</h3>{/if}

{/if}

{foreach from=$comments item=child}

(Though best would probably be to implement this as a smarty filter)

ctgraham · January 17, 2018, 1:52pm

In journal_settings, there is a setting_name with a value of “enableComments”. The setting is a “string” setting_type with a setting_value of 1 or 0 to enable or disable comments, keyed on the journal_id. This value is cached in the files cache/fc-journalSettings-*.php. Changing it only in the database will not be immediately effective.