Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

系统初始化之后安装了评论插件需要在全局设置点一次保存才能使用评论组件 #4561

Closed
guqing opened this issue Sep 6, 2023 · 0 comments · Fixed by #4562
Assignees
Labels
area/core Issues or PRs related to the Halo Core kind/improvement Categorizes issue or PR as related to a improvement.
Milestone

Comments

@guqing
Copy link
Member

guqing commented Sep 6, 2023

What is version of Halo has the issue?

latest

What database are you using?

H2

What is your deployment method?

Docker

Your site address.

No response

What happened?

系统初始化之后安装了评论插件需要在全局设置点一次保存才能使用评论组件

Relevant log output

No response

Additional information

/kind improvement
/area core
/milestone 2.10.x
/assign

@f2c-ci-robot f2c-ci-robot bot added the kind/improvement Categorizes issue or PR as related to a improvement. label Sep 6, 2023
@f2c-ci-robot f2c-ci-robot bot added this to the 2.10.x milestone Sep 6, 2023
@f2c-ci-robot f2c-ci-robot bot added the area/core Issues or PRs related to the Halo Core label Sep 6, 2023
f2c-ci-robot bot pushed a commit that referenced this issue Sep 7, 2023
#### What type of PR is this?
/kind improvement
/area core
/milestone 2.10.x

#### What this PR does / why we need it:
补全系统全局设置的默认值

how to test it?
1. 初始化 halo
2. 安装评论组件
3. 到文章页面可以评论

#### Which issue(s) this PR fixes:
Fixes #4561

#### Does this PR introduce a user-facing change?
```release-note
补全系统全局设置的默认值
```
@ruibaby ruibaby modified the milestones: 2.10.x, 2.10.0 Sep 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/core Issues or PRs related to the Halo Core kind/improvement Categorizes issue or PR as related to a improvement.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants