polyglot: site translation broken after pushing to gh-pages
Hi Untra,
After merging my polyglot branch to gh-pages the site is not able to display all the translated strings, nor in default or /en/ language.
Actually, when trying to reach the not-default website.com/en/ I get a 404
You can check the website here
So far I have tried to:
- remove the CNAME
- remove the
data_dir: ./_dataanddestination: ./_sitefrom_config.yml - set
parallel_localization: falsein_config.yml
None of the above helped…
Any idea how to proceed? Thanks a lot for your help.
About this issue
- Original URL
- State: closed
- Created 9 years ago
- Comments: 15 (2 by maintainers)
Commits related to this issue
- config: gemfile이 필수는 아닌 것 같아서 제거 - https://github.com/george-gca/multi-language-al-folio 참고 - https://github.com/untra/polyglot/issues/75#issuecomment-2093316206 처럼 gemfile의 제한이 에러를 만들기도 함 — committed to meansoup/meansoup.github.io by meansoup 3 years ago
- config: 기본으로 설정하기 - https://github.com/untra/polyglot/issues/75#issuecomment-2093077338 참고 — committed to meansoup/meansoup.github.io by meansoup 3 years ago
Actually the
Deploy siteaction triggers thepages-build-deploymentaction. Internally the JamesIves/github-pages-deploy-action is used, which is the action that actually uploads the site correctly. These are the minimum steps required:Meaning, get the code, setup the build environment, build the site, and upload the generated
_site/directory to GitHub pages.@george-gca Thank you. I did it thanks to you.
You should look at the full stacktrace to get more information about your error. Checking your failed workflow there is:
Which is what is set in your Gemfile.lock.
No idea what this error means. Note that you can’t take my deploy and use it as-is. Some steps during my process are custom made to the repo, like the
Update _config.ymlstep and thePurge unused CSS 🧹one.GitHub Pages doesn’t accept many plugins, so if you want to do anything serious with Jekyll you pretty much have to build your site locally or with any CI system and then push it to your GitHub Pages branch.
Here’s the documentation from TravisCI on how to do this. Don’t skip the step where you have to manually generate and register a private token for TravisCI.
Here’s also my configuration with the build step if that helps. Works like a charm for me. My configuration is a little special because I had to push to the
masterbranch instead of thegh-pagesbranch because I’m using it for the root of the GitHub Pages website. I also have to use another branch thanmasterfor the source code, so I used thesourcebranch and I set it as the default branch for the project so this one would show up on my project’s homepage instead ofmaster.