Translator Reviews ( Japanese → English )
Rating: 59 / 2 Reviews / 23 Mar 2014 at 05:12
Word censorshipの機能を追加して欲しい
その際に投稿内容やコメント欄、そしてユーザー名のWordもチェックできるようにしてください
この機能がないとAdsenseを利用することが難しいです
あと以前、報告したかもしれませんがタグが1つだけの場合、その投稿がタグページに表示されません
またパスワードをリセットするページで登録したメールアドレスを入力して送信すると白いページになってしまいます
同じようなエラーをサポートしたことはありませんか?おそらくサーバーの問題だと思います
I would like for you to add a word censorship function.
In that case, please make it so that I can check the content of submissions, the comment column, and usernames as well.
If I don't have this function, it is difficult to use Adsense.
I may have reported this before, but when only one tag is used, that submission won't display on the tag page.
Furthermore, when I input and submit a registered email address on the password reset page, the page goes blank.
Haven't you given support with similar errors before? I think it is perhaps a problem with the server.
Reviews ( 2 )
私はいいと思います。
This review was found appropriate by 100% of translators.
original
I would like for you to add a word censorship function.
In that case, please make it so that I can check the content of submissions, the comment column, and usernames as well.
If I don't have this function, it is difficult to use Adsense.
I may have reported this before, but when only one tag is used, that submission won't display on the tag page.
Furthermore, when I input and submit a registered email address on the password reset page, the page goes blank.
Haven't you given support with similar errors before? I think it is perhaps a problem with the server.
corrected
I would like you to add a word censorship function.
In that case, please make it so that I can check the content of submissions, the comment column, and usernames as well.
If I don't have this function, it is difficult to use Adsense.
I may have reported this before, but when only one tag is used, that submission won't display on the tag page.
Furthermore, when I input and submit a registered email address on the password reset page, the page goes blank.
Haven't you given support with similar errors before? I think it is perhaps a problem with the server.