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

二级菜单下的相册部署在本地/gitee、github/vercel产生的目录结构不同 #816

Closed
i-abc opened this issue May 14, 2022 · 2 comments

Comments

@i-abc
Copy link

i-abc commented May 14, 2022

二级菜单下的相册部署在本地/gitee正常,然而部署在github/vercel出错。

一、部署在github/vercel:

  1. https://i-abc.github.io/galleries
    github1

  2. 点击,本应该是跳转到 https://i-abc.github.io/galleries/2022 的,结果跳转到了 https://i-abc.github.io/2022
    github2

  3. 直接输入 https://i-abc.github.io/galleries/2022 则正常:
    github3

二、部署在本地/gitee时正常,无以上跳转错误

https://i-abc.gitee.io/galleries/
gitee1

gitee2

三、补充

这个相册搭建我按Yafine大佬的教程来的:修改 matery 原有主题相册

@i-abc
Copy link
Author

i-abc commented May 14, 2022

目前猜测是github/vercel部署后的 https://i-abc.github.io/galleries 缺少了/,如果把/加上 https://i-abc.github.io/galleries/ 则正常了,但我不知道该如何修改。

我也看了#133,还是搞不懂,我其他的目录都正常,只有二级菜单下相册这个出了问题。
这是我的设置:

url: https://seeseeme.cn/
root: /
repo: 
   gitee:  https://gitee.com/i-abc/i-abc.git
   github: https://github.com/i-abc/i-abc.github.io.git

@i-abc i-abc changed the title 二级菜单下的相册部署在本地/gitee、github/vercel产生的效果不同 二级菜单下的相册部署在本地/gitee、github/vercel不同 May 14, 2022
@i-abc i-abc changed the title 二级菜单下的相册部署在本地/gitee、github/vercel不同 二级菜单下的相册部署在本地/gitee、github/vercel产生的目录结构不同 May 14, 2022
@i-abc
Copy link
Author

i-abc commented May 14, 2022

我改了下主题设置的_config.yml,正常了。

  # 二级菜单写法如下
  Medias:
    icon: fas fa-list
    children:
      - name: 相册
        url: /galleries
        icon: fas fa-image

改为了:

 url: /galleries/

这下github/vercel/本地/gitee都正常了。
我也是瞎试的,没想到成功了,但不知道正确方法是不是这样,还是等作者看看确定了再close。

@i-abc i-abc closed this as completed Jun 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant