Troubleshooting Common Errors and Fixes

table of contents

• unable to run jekyll s
• jekyll issues in general
• unable to generate derivatives
• PDF include doesn't work
• some weird error from Git
• broken images

unable to run jekyll s

Error: when you open the terminal and attempt to run jekyll and it gives you an error that says "Could not find gem 'jekyll-paginate x64-mingw32' in any of the gem sources listed in your Gemfile. (Bundler::GemNotFound)"

Solution: type "bundle update" into the terminal and hit Enter. Then, try to run jekyll again - it should work now.

Other Solution: instead of jekyll s, type bundle exec jekyll s -- that will let the bundler run the repository with the specific plugins needed.

Jekyll issues in general

The two commands listed above should clear up most of those. So here are the hammers to throw at the issue:

• bundle exec jekyll s -- this will run the repo with the gems defined in Gemfile.lock
• bundle update -- this will update your gem files to match those defined in the Gemfile.lock
• Alternatively .. delete Gemfile.lock. This will let the repo remake that file based on the gems defined in your Gemfile
  • if you do this, and then you push the change to Gemfile.lock to the repo, let us know so we're not surprised if we need to bundle update to get things to work.

unable to generate derivatives

Error: when you open the terminal and attempt to generate derivatives, it gives you an error.

Solution: make sure the file names of the images do not contain any spaces or dashes (underscores are allowed)

PDF include doesn't work

Error: you added an include to a PDF but when you preview the post in Jekyll, it doesn't show up.

Solution 1: the PDF will not show up in the test server (just running Jekyll s). It will only appear once it's live on the harvester.lib.uidaho.edu site.

Solution 2: make sure you use the correct include command "{% include feature/item-pdf-embed.html objectid="lumber###" %}

Some weird error from Git

Error: Git or GitHub Desktop gives you some error message or merge message that you can't make sense of.

Solution: If the error or merge doesn't make sense, do not push it up to GitHub--the error is only in your local copy until you Push. Often the easiest way to recover is to just start over fresh! If you have changes that you need to save: copy the file(s) into another location, delete the "spec-lumber" folder (i.e. the repository), clone a fresh copy of the repository from GitHub (where the error won't exist), then copy your file back into the fresh repository. (for example, you wrote a new post "_posts/2020-01-06-oh-dam.md", temporarily copy the .md file into another folder such as Downloads, then delete "spec-lumber".)

XKCD Git

Broken image

Error: An image is broken (it may not be showing a preview on the post, or it may not be downloadable, etc.)

Solution 1: Make sure you ran rake generate_derivatives and moved images to the appropriate folders in Shared (S:)/Webpages/Library/Spec/Harvester/Objects

Solution 2: If your original file if a TIFF (ending in .tiff), in the Lumber spreadsheet, you need to put "filename.jpg" NOT "filename.tiff." This is because, when you do rake generate_derivatives, the small and thumb will be generated as jpgs, not tiffs. Thus, if you put "filename.tiff" in the spreadsheet, it won't grab the small or thumb jpgs, and the image will be broken.