在查找文章的時候有文章就提到

Check Your Current Collation: Look at your database tables. If you see a collation like utf8mb3_unicode_ci, this is likely the cause of the problem. WordPress tables should ideally use utf8mb4_unicode_520

才想到查一下我的 DB 是不是 utf8mb3 ，一查之下果然是，老的 WordPress 用的資料庫果然夠老，轉換資料庫也碰到一些問題，主要是 wp_comments 這個資料庫的問題，可以先去 WordPress comments 刪除所有垃圾留言

在 wp-config.php 內設定成 utf8mb4

define('DB_CHARSET', 'utf8mb4');
define('DB_COLLATE', 'utf8mb4_unicode_ci');

導出 wp_comments 的資料庫

mysqldump -u [用戶名] -p --skip-set-charset --default-character-set=latin1 [資料庫名] wp_comments > wp_comments.sql

導回 wp_comments 的資料庫

mysql -u [用戶名] -p --default-character-set=utf8mb4 [資料庫名] < wp_comments.sql

轉換整個資料庫

#!/bin/bash
DB_NAME="your_database"
USER="your_user"
PASS="your_password"

TABLES=$(mysql -u $USER -p$PASS -Nse "SHOW TABLES;" $DB_NAME)
for TABLE in $TABLES; do
    mysql -u $USER -p$PASS -e "ALTER TABLE $TABLE CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;" $DB_NAME
done

DeepSeek 這邊做的非常好，直接給 shell script 幫助完成，Grok 就沒給出這麼方便的 Script.

The post WordPress utf8mb3_general_ci 改utf8mb4_unicode_ci appeared first on richliu's blog.

沒想到，突然靈光一動，看是不是能改 html 就達到相同的目地，以為用 style 包就可以，不過怎麼會像蠢人想的這麼簡單呢？沒想到，更簡單，其實只要去拿 PTT 的 CSS 來用就可以了。然後用 GPT 之類的程式（這次我是試用 deepseek）找出不符合規範的 CSS 部份修改或是移除就好。現代人有 GPT 真的省事很多，我知道這不是最佳解，但是只是備份，有就很開心，效果還不錯，跟我想要的效果一樣。

以下截圖的連結 [心得] 囤物族的不丟東西整理術

以下是我用的 CSS ，只有改字體以及拿到不要的部份，感覺沒影響到的我也沒拿

.bbs-content {
    font-size: 16px !important;
	font-family: "細明體", "AR PL UMing TW", "Menlo", "LiSongPro", monospace;
}

.bbs-screen {
    width: auto !important;
}

#main-content {
    white-space: normal;
}

#navigation div {
    display: inline-block;
    margin: 0 4px;
}

#banner {
    text-align: center;
    width: 100%;
    text-decoration: none;
}

.richcontent {
    text-align: center;
    margin: 1em;
}


/* ansi colors */
.b0 { background-color: #000; }
.b1 { background-color: #b00; }
.b2 { background-color: #0b0; }
.b3 { background-color: #bb0; }
.b4 { background-color: #00b; }
.b5 { background-color: #b0b; }
.b6 { background-color: #0bb; }
.b7 { background-color: #bbb; }

.f0 { color: #000; }
.f1 { color: #900; }
.f2 { color: #090; }
.f3 { color: #990; }
.f4 { color: #009; }
.f5 { color: #909; }
.f6 { color: #099; }
.f7 { color: #999; }

.hl { color: #fff; }
.hl.f0 { color: #666; }
.hl.f1 { color: #f66; }
.hl.f2 { color: #6f6; }
.hl.f3 { color: #ff6; }
.hl.f4 { color: #66f; }
.hl.f5 { color: #f6f; }
.hl.f6 { color: #6ff; }
.hl.f7 { color: #fff; }

/* main layout */
.bbs-screen {
	color: #bbb;
	background-color: #000;
	line-height: 100%;
	overflow-wrap: break-word;
	word-wrap: break-word;
	margin: 0 auto;
    padding: 0;
	width: 100%;
}

.bbs-content {
	font-family: "細明體", "AR PL UMing TW", "Inconsolata", "LiSongPro", monospace;
}

.bbs-footer-message {
    text-align: center;
    margin-top: 1em;
}

.center {
    text-align: center;
}

.warning-box {
    border: 1px solid #555;
    background-color: #333;
}

.small {
	font-size: small;
}

#main-container {
	margin: 0;
	padding: 0 0 3ex 0;
	position: relative;
}

#main-content {
	position: relative;
	white-space: normal;
}
#main-content a:link {
    text-decoration: none;
    box-shadow: inset 0 -2px #555;
}
#main-content a:hover {
    box-shadow: inset 0 -2px #777;
}


body {
	background-color: #000;
	margin: 0;
	padding: 40px 0 24px 0;
}


.share {
	line-height: 40px;
	vertical-align: middle;
}
.brdname {
	float: right;
}
#navigation .board {
	padding: 0 10px;
}
#navigation .bar {
	background-color: #888;
	width: 4px;
	height: 100%;
	padding: 0;
}

.push {
	line-height: 130%;
	white-space: normal;
	clear: both;
    position: relative;
}
.push > span {
	white-space: normal;
}
.push-tag {
	display: inline-block;
	min-width: 3.5ex;
	white-space: normal;
}
.push-content {
}
.push-ipdatetime {
	float: right;
}

.richcontent {
    position: relative;
	text-align: center;
    width: 100%;
    margin: 0.5em auto;
    max-width: 800px;
}
.resize-container {
    position: relative;
    width: 100%;
}
.resize-container:before {
    content: "";
    display: block;
    padding-top: 56.25%;
}
.resize-content {
    position: absolute;
    top: 0;
    left: 0;
    bottom: 0;
    right: 0;
}
.youtube-player {
    width: 100%;
    height: 100%;
}

.article-metaline {
	margin: 0;
	padding: 0;
	background-color: #008;
}
.article-metaline-right {
	position: absolute;
	right: 0;
	top: 0;
	background-color: #008;
}
.article-meta-tag {
	padding: 0 1ex;
	background-color: #999;
	color: #008;
}
.article-meta-value {
	padding: 0 1ex;
	background-color: #008;
	color: #999;
}

img {
	max-width: 100%;
	max-height: 800px;
}

The post 幫備份 PTT 的 WordPress 文章上色 appeared first on richliu's blog.

Shorter message:

Fatal error: Uncaught TypeError: count(): Argument #1 ($value) must be of type Countable|array, false given in formatting.php

Conclusion

Root cause is WordPress uses the regular expression to convert content text smilies to images. It will exhaust the php pcre library backtrack quickly. Especially when the images in the the article over 500.

Just keep the images number under 500 or separate  it into several articles.

if unfortunately, it happend, add “pcre.backtrack_limit=1000000000” to php.ini and restart website, it might make it work again, would be very very very slow to load the page.

If still cannot solve this problem, or too slow, probably use the number “pcre.backtrack_limit=10000000” can make it work. because default value is not so big like, when it can edit the article again, just remove some images can make it work.

How to Get the debug message?

Enable the debug in the wp-config.php, turn on following messages in the file.

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_DISPLAY', true );
define( 'WP_DEBUG_LOG', true );

Or check the web server error log.
Original Message

Fatal error: Uncaught TypeError: count(): Argument #1 ($value) must be of type Countable|array, false given in formatting.php

PHP Fatal error:  Uncaught TypeError: count(): Argument #1 ($value) must be of type Countable|array, false given in /var/www/htdocs/wp-includes/formatting.php:3507\nStack trace:\n#0 /var/www/htdocs/wp-includes/class-wp-hook.php(324): convert_smilies()\n#1 /var/www/htdocs/wp-includes/plugin.php(205): WP_Hook->apply_filters()\n#2 /var/www/htdocs/wp-content/plugins/seo-by-rank-math/includes/modules/links/class-links.php(171): apply_filters()\n#3 /var/www/htdocs/wp-content/plugins/seo-by-rank-math/includes/modules/links/class-links.php(59): RankMath\\Links\\Links->process()\n#4 /var/www/htdocs/wp-includes/class-wp-hook.php(326): RankMath\\Links\\Links->save_post()\n#5 /var/www/htdocs/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()\n#6 /var/www/htdocs/wp-includes/plugin.php(517): WP_Hook->do_action()\n#7 /var/www/htdocs/wp-includes/post.php(4828): do_action()\n#8 /var/www/htdocs/wp-includes/post.php(4930): wp_insert_post()\n#9 /var/www/htdocs/wp-includes/rest-api/endpoints/class-wp-rest-posts-controller.php(880): wp_update_post()\n#10 /var/www/htdocs/wp-includes/rest-api/class-wp-rest-server.php(1230): WP_REST_Posts_Controller->update_item()\n#11 /var/www/htdocs/wp-includes/rest-api/class-wp-rest-server.php(1063): WP_REST_Server->respond_to_request()\n#12 /var/www/htdocs/wp-includes/rest-api/class-wp-rest-server.php(439): WP_REST_Server->dispatch()\n#13 /var/www/htdocs/wp-includes/rest-api.php(428): WP_REST_Server->serve_request()\n#14 /var/www/htdocs/wp-includes/class-wp-hook.php(324): rest_api_loaded()\n#15 /var/www/htdocs/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()\n#16 /var/www/htdocs/wp-includes/plugin.php(565): WP_Hook->do_action()\n#17 /var/www/htdocs/wp-includes/class-wp.php(418): do_action_ref_array()\n#18 /var/www/htdocs/wp-includes/class-wp.php(813): WP->parse_request()\n#19 /var/www/htdocs/wp-includes/functions.php(1336): WP->main()\n#20 /var/www/htdocs/wp-blog-header.php(16): wp()\n#21 /var/www/htdocs/index.php(17): require('...')\n#22 {main}\n  thrown in /var/www/htdocs/wp-includes/formatting.php

ref.
Fatal error: Uncaught TypeError: count():

The post WordPress Fatal error: Uncaught TypeError: count() appeared first on richliu's blog.

簡單的事情也花了我三個小時.

The post 升級到 WordPress 3.0.6 appeared first on richliu's blog.

The post WordPress Update to 2.3.3 appeared first on richliu's blog.