dan
/
jekyll
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Merge pull request #6928 from ashmaroli/troubleshooting-docs 

Correct errors in troubleshooting.md
This commit is contained in:
Frank Taillandier 2018-04-16 13:47:14 +02:00 committed by GitHub
parent 2a86c00011 6fc2cfea6e
commit 7e72cbddd2
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 13 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

27
docs/_docs/troubleshooting.md
View File

@ -111,7 +111,7 @@ possible to run Jekyll as a non-superuser and without having to install
gems to system-wide locations by adding the following lines to the end gems to system-wide locations by adding the following lines to the end
of your `.bashrc` file: of your `.bashrc` file:
```sh ```
# Ruby exports # Ruby exports
export GEM_HOME=$HOME/gems export GEM_HOME=$HOME/gems
@ -133,20 +133,20 @@ currently-running shell.
If you see the following error when running the `jekyll new` command, If you see the following error when running the `jekyll new` command,
you can solve it by using the above-described procedure: you can solve it by using the above-described procedure:
``` ```sh
$ jekyll new test jekyll new test
Running bundle install in /home/user/test... Running bundle install in /home/user/test...
Your user account isn't allowed to install to the system RubyGems. Your user account isn't allowed to install to the system RubyGems.
You can cancel this installation and run: You can cancel this installation and run:
bundle install --path vendor/bundle bundle install --path vendor/bundle
to install the gems into ./vendor/bundle/, or you can enter your password to install the gems into ./vendor/bundle/, or you can enter your password
and install the bundled gems to RubyGems using sudo. and install the bundled gems to RubyGems using sudo.
Password: Password:
``` ```
Once this is done, the `jekyll new` command should work properly for Once this is done, the `jekyll new` command should work properly for
@ -227,13 +227,13 @@ jekyll serve --baseurl '/blog'
… then make sure that you access the site at: … then make sure that you access the site at:
```sh ```
http://localhost:4000/blog/index.html http://localhost:4000/blog/index.html
``` ```
It won’t work to just access: It won’t work to just access:
```sh ```
http://localhost:4000/blog http://localhost:4000/blog
``` ```
@ -252,7 +252,7 @@ specified elsewhere.
**Note: From v3.3.0 onward, Jekyll does not process `node_modules` and certain subdirectories within `vendor`, by default. But, by having an `exclude:` array defined explicitly in the config file overrides this default setting, which results in some users to encounter an error in building the site, with the following error message:** **Note: From v3.3.0 onward, Jekyll does not process `node_modules` and certain subdirectories within `vendor`, by default. But, by having an `exclude:` array defined explicitly in the config file overrides this default setting, which results in some users to encounter an error in building the site, with the following error message:**
``` ```sh
ERROR: YOUR SITE COULD NOT BE BUILT: ERROR: YOUR SITE COULD NOT BE BUILT:
------------------------------------ ------------------------------------
Invalid date '<%= Time.now.strftime('%Y-%m-%d %H:%M:%S %z') %>': Invalid date '<%= Time.now.strftime('%Y-%m-%d %H:%M:%S %z') %>':
@ -290,9 +290,8 @@ problems.
### Liquid ### Liquid
The latest version, version 2.0, seems to break the use of `{{ "{{" }}` in Liquid version 2.0 seems to break the use of `{{ "{{" }}` in templates.
templates. Unlike previous versions, using `{{ "{{" }}` in 2.0 triggers the Unlike previous versions, using `{{ "{{" }}` in 2.0 triggers the following error:
following error:
```sh ```sh
'{{ "{{" }}' was not properly terminated with regexp: /\}\}/ (Liquid::SyntaxError) '{{ "{{" }}' was not properly terminated with regexp: /\}\}/ (Liquid::SyntaxError)