Senri Miura

I’ve suggested corrections to the following words:

“Entry” → “投稿”

Hello Marcel,

I confirmed import to GlotPress. Thank you very much.

The link below is an approved Japanese translation of the Gwolle Guestbook plugin in GlotPress.

Translation to Japanese (GlotPress)

When I checked it, I found a serious mistranslation, so I corrected it.
The corrected content is “at → 場所”.
“場所” means a place, so it is clearly a mistranslation. There is no problem here even if it is left as “at”.
This shows the time when you wrote it in the guestbook, and since it is obviously a strange translation, I corrected it to “at → -“.
However, it is uncertain at what time the correction will be approved.

I’ve proposed another correction as follows:
“Of →の” is changed to “of → /”

This part seems to be the word used on the screen that displays the guestbook entry in the settings, but if you translate it to “の”, the meaning will be reversed in Japanese grammar.
That is, a / b is interpreted as b / a.

In addition, I don’t have any authority such as GTE / PTE, so I would like to ask those who have authority to approve it.

• This reply was modified 3 years, 3 months ago by Senri Miura.

Hello Marcel Pol,

Thank you for your suggestions for GlotPress.
I don’t know the details about GlotPress, so I don’t think I can take immediate action.
I will consider it after investigating. thank you very much.

Senri

@timmy321

You can also insert the plug-in WP Rollback and roll back.

Thank you very much, Hector.

Certainly the update to version 5.3.5 fixed the issue.

Thank you for your prompt response!

Hi cheryanne,

Probably there is a problem with the character code.
English is displayed correctly, but the screen is broken in Japanese and other languages.

併せて、以下のブログもご参照願います。

ホームページビルダーがhpb22へバージョンアップしたのにWordPress機能は5年以上更新されないまま放置（WP5.5非互換/Google検索非互換/SSL非対応など）- hpb Dashboard 改修

上記のコードは文字化けしているため、詳細は以下のブログをご参照下さい。

WordPress 5.5/5.7へのアップグレードでクラシックエディタなどのプラグインが動かなくなった問題について（HPBテーマ&hpbseo、biz calendar等のjQuery 3.0非互換対策

なお、上記の修正を行うと、WordPressダッシュボード内における「Jetpackごとの統計」がクラッシュし表示されなくなります。
よって、hpbseoの修正版がリリースされるまでは、できるだけ「Enable jQuery Migrate Helper」を有効化することを推奨します。（jQueryバージョンは「WordPressのデフォルト」でOK、「自動ダウングレード」をチェック）

あくまでも、間に合わせでの対応となりますが、hpbseoのPHPプログラムにおいて、以下の関数を修正する事でブロックエディタでの動作不良は改善されるようです。

/**—————————————————————————-
* jsファイル読込（ダッシュボード用）
* ————————————————————————–*/
function fncHpbSeo_IncludeAdminJS() {
wp_enqueue_script( “jquery”);
wp_enqueue_script( “hpbseo_admin_js”, PLUGIN_URL . JS_FILE_NAME_ADMIN);
}

上記の関数「fncHpbSeo_IncludeAdminJS()」を以下のように修正します。これにより、プラグイン「Enable jQuery Migrate Helper」は不要となりますが、クラシックエディタの動作不良は改善されないようです。
もしかしたら、プラグインの干渉が原因の可能性もあります。

/**—————————————————————————-
* jsファイル読込（ダッシュボード用）
* ————————————————————————–*/
function fncHpbSeo_IncludeAdminJS() {
// 旧jQueryの読み込み（ここから） – Added by Senri on 2021.06.25
wp_deregister_script( ‘jquery’ );
wp_register_script( ‘jquery’, ( ‘https://cdnjs.cloudflare.com/ajax/libs/jquery/2.2.4/jquery.min.js’ ), false, null, true );
// ここまで

wp_enqueue_script( “jquery”);
wp_enqueue_script( “hpbseo_admin_js”, PLUGIN_URL . JS_FILE_NAME_ADMIN);
}

Hi there!

Yesterday, I received the following contact from the hosting company CoreServer as follows.

The response we have taken this time is to lift all restrictions by IP address, such as restrictions on the connection source IP address of behavior that is suspected of brute force attack on WordPress.

So I’ve checked the operation of Jetpack.
As a result, I confirmed that the following problems have been resolved on CoreServer.

1. When I turn on / off the Jetpack extension module, a “Status 400” error occurs.
2. Site Accelerator (CDN) does not work

However, the phenomenon that Jetpack’s comment section was broken was not improved.
Therefore, when I checked Jetpack’s “Known Issues” as shown below, it turned out that “Google Captcha (reCAPTCHA) by BestWebSoft” corresponds to this website.

https://jetpack.com/support/getting-started-with-jetpack/known-issues/

Antispam Bee, Spam Free WordPress, Bad Behavior, WP?SpamShield, CommentLuv, Anti?spam, Google Captcha (reCAPTCHA) by BestWebSoft
These plugins are currently not compatible with the Jetpack Comments module.

For the time being, if Jetpack’s comment module does not support Google Captcha (reCAPTCHA), I will not use Jetpack comments, so I will close this topic once.
I’d like to thank all the people who cooperated in the survey.
Thank you very much.

Best Regards,
Senri Miura

Hello, Michelle Paese

thank you so much.
If the hosting company contacts me again, I’ll let you know in this thread.
Thank you for your continued support.

Hello, MadHatter

Thank you for your polite commentary.
When I checked with core server support yesterday, I got the following answer.

‘As a result of confirmation by the department in charge of our company, some IP addresses were rejected on our server side within the range of the IP address of “192.0.64.0/18” that we contacted, and connection restrictions were enforced.

The above restrictions have been lifted by the department in charge.’

For the time being, after removing the IP address restrictions, I checked the operation of Jetpack, but unfortunately the situation did not improve.

Perhaps the cause is that the core server security process considers the source IP address to be overloaded and still limits it.
This is in line with the view that, as MadHatter points out, “although you’re using a whitelisted IP, there’s a security outage process after a certain amount of time.”

I’ve already contacted core server support for this issue, but I think it’s probably difficult to fix the core server security system right away.
So far, the basic functions of Jetpack are working, so I will continue to use it in the current state.
Unfortunately, I will give up using Jetpack’s comment function.

Thank you very much for this time.

Today, I’ve received the following answer (removing the connection restriction to IP addresses that send and receive from Automattic) from the support of the CoreServer, but unfortunately, the problem of Jetpack has not been fixed yet.

from CoreServer
—- from here
As a result of confirmation by the department in charge of our company, some IP addresses were rejected on our server side within the range of the IP address of “192.0.64.0/18” that we contacted, and connection restrictions were enforced. ..
The above restrictions have been lifted by the department in charge.
However, we have a security mechanism that automatically rejects the connection source IP address that causes a high load on the server.

Therefore, we may refuse the connection from the target IP address again, but for security reasons, we cannot stop the implementation of the above restrictions.
Thank you for your understanding.
—- to this point

I’ve provided the following list of IP addresses used by Automattic, but is there anything else?

# Allow Automattic (Jetpack)

allow from 66.135.48.128/25
allow from 66.155.8.0/22
allow from 66.155.38.0/24
allow from 69.174.248.128/25
allow from 72.233.119.192/26
allow from 76.74.248.128/25
allow from 76.74.254.0/25
allow from 76.74.255.0/25
allow from 185.64.140.0/22
allow from 192.0.64.0/18
allow from 198.181.116.0/22
allow from 192.0.64.0/255.0.64.0
allow from 207.198.101.0/25
allow from 207.198.112.0/23
allow from 209.15.21.0/24
allow from 216.151.209.64/26

P.S.

The comment field is not displayed in <Bug 3>, but if you set the share button display to OFF, it will be in the same state as <Bug 2>.

• This reply was modified 3 years, 5 months ago by Senri Miura.

Apparently, the following Jetpack malfunctions have been reported by others on the core server (https://www.coreserver.jp/).
By the way, when I set the share button of Jetpack, the comment field disappeared.

<Bug 1>
All images disappear when Jetpack site accelerator is enabled. (CDN is disabled)

<Bug 2>
When I enable comments on Jetpack’s SNS account, the comment field is broken.

<Bug 3>
If you enable comments on Jetpack’s SNS account after setting the Jetpack share button on Jetpack, the comment field will not be displayed.

• This reply was modified 3 years, 5 months ago by Senri Miura.