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

fixed a problem of 'reward and wechat-subscriber' #2064

Closed
wants to merge 1 commit into from
Closed

fixed a problem of 'reward and wechat-subscriber' #2064

wants to merge 1 commit into from

Conversation

kuleyu
Copy link

@kuleyu kuleyu commented Jan 2, 2018

fixed the problem that the images of 'reward and wechat-subscriber area' can't display when the main '_config.yml' set 'root: /xxxxxx/'

PR Checklist

Please check if your PR fulfills the following requirements:

  • The commit message follows our guidelines.
  • Tests for the changes have been added (for bug fixes / features).
    • Muse | Mist have been tested.
    • Pisces | Gemini have been tested.
  • Docs have been added / updated (for bug fixes / features).

PR Type

What kind of change does this PR introduce?

  • Bugfix.
  • Feature.
  • Code style update (formatting, local variables).
  • Refactoring (no functional changes, no api changes).
  • Build related changes.
  • CI related changes.
  • Documentation content changes.
  • Other... Please describe:

What is the current behavior?

the images of 'reward and wechat-subscriber area' can't display when the main '_config.yml' set 'root: /xxxxxx/'
Issue Number(s): N/A

What is the new behavior?

Now if you set the main '_config.yml' as 'root: /xxxxxx/', the images of 'reward and wechat-subscriber area' can display correctly.

How to use?

In NexT _config.yml:

...

Does this PR introduce a breaking change?

  • Yes.
  • No.

…ea' can't display when the main '_config.yml' set 'root: /xxxxxx/'
@ivan-nginx
Copy link
Collaborator

This NexT version not supported anymore (at least by me). For now it rebased under theme-next organization and have this path. So, u can do pull there.

More information in #2061 issue.

@ivan-nginx ivan-nginx closed this Jan 2, 2018
@ivan-nginx ivan-nginx added the v6.x label Jan 3, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants