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

页脚菜单组中的子菜单无法展示 #168

Closed
Haoke98 opened this issue Aug 28, 2024 · 2 comments · Fixed by #169
Closed

页脚菜单组中的子菜单无法展示 #168

Haoke98 opened this issue Aug 28, 2024 · 2 comments · Fixed by #169
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@Haoke98
Copy link

Haoke98 commented Aug 28, 2024

系统信息

  • 外部访问地址: http://blog.0p.fit/
  • 启动时间: 2024-08-28 13:32
  • 版本: 2.18.1
  • 构建时间: 2024-08-28 13:30
  • 已激活主题: theme-earth (Default theme for Halo 2.0)
  • 还未启动任何插件, 默认状态

使用的哪种方式运行?

Docker

发生了什么?

如下图所示, 子菜单的名字没有渲染出来
截屏2024-08-28 13 39 03
但检查网页静态代码, 可以观察到, 子菜单的ul标签和链接都渲染出来了, 只是缺乏标题文字(如下图所示)
截屏2024-08-28 13 40 11

复现步骤

No response

相关日志输出

No response

附加信息

No response

@JohnNiang
Copy link
Member

/area theme
/ping @halo-dev/sig-halo

@ruibaby
Copy link
Member

ruibaby commented Aug 29, 2024

可以确定是主题的问题

th:text="${menuItem.spec.displayName}"

<a
  th:href="@{${menuItem.status.href}}"
  class="transition-all hover:text-gray-900 hover:underline dark:hover:text-white"
  th:text="${menuItem.spec.displayName}"
></a>

这里应该是 menuItem.status.displayName

@ruibaby ruibaby transferred this issue from halo-dev/halo Aug 29, 2024
@ruibaby ruibaby self-assigned this Aug 29, 2024
@ruibaby ruibaby added the kind/bug Categorizes issue or PR as related to a bug. label Aug 29, 2024
f2c-ci-robot bot pushed a commit that referenced this issue Aug 29, 2024
Resolve issue with footer menu items not displaying

/kind bug

Fixes #168 

```release-note
修复页脚菜单项名称可能不显示的问题。
```
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants