Skip to content

When I try to customize the table prefix, the cache may have problems finding the key value; For example, set table_prefix to xxxx_. The possible cause is that the prefix of the cache value related to "global_xxxx“ is set in the code. #1208

When I try to customize the table prefix, the cache may have problems finding the key value; For example, set table_prefix to xxxx_. The possible cause is that the prefix of the cache value related to "global_xxxx“ is set in the code.

When I try to customize the table prefix, the cache may have problems finding the key value; For example, set table_prefix to xxxx_. The possible cause is that the prefix of the cache value related to "global_xxxx“ is set in the code. #1208

Triggered via issue July 25, 2024 12:45
@aqlx86aqlx86
commented on #745 f658968
Status Success
Total duration 16s
Artifacts

translate_issues.yml

on: issue_comment
translate issues
4s
translate issues
Fit to window
Zoom out
Zoom in

Annotations

2 warnings
translate issues
The following actions uses node12 which is deprecated and will be forced to run on node16: tomsun28/issues-translate-action@v2.5. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
translate issues
The following actions uses Node.js version which is deprecated and will be forced to run on node20: tomsun28/issues-translate-action@v2.5. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/