Filters {{ page.date | timeago }} become invalid date about jekyll-timeago HOT 3 CLOSED

Hi @diazsepta 👋

First weird thing I see 👀 => in your _config.yml you copy-pasted the example from the docs, to customize the plugin options:

jekyll_timeago:
  depth: 4
  translations_path: '/path_to_your_translations/*.yaml'
  default_locale: 'en'
  fallbacks: true
  available_locales:
    - 'en'
    - 'es'
    - 'fr'

You only need to override those entries in case you want to change defaults, and of course with "valid" options: /path_to_your_translations/*.yaml is just an example, that path probably doesn't exist in your repo... You can just ✂️ the entire section from the _config.yml, if defaults are fine for you.

from jekyll-timeago.

@markets thanks for reply, you right, its work now. but i have new problem. i think your plugin not work on _includes statement (maybe, if I not wrong 😂), so i want to make my header post with timeago, but the header is was includes on _includes/header.html which will be called on _layouts/default.html. now the is problem, when i puts {{ page.date | timeago }} on _includes/header.html it will be get error:

Liquid Exception: Liquid error (_includes/header.html line 2): invalid date included in /_layouts/default.html

i try puts on any place in _includes/header.html or any file on _includes folder and it's still error. but {{ page.date | timeago }} work perfectly on _layouts\post.html & _layouts\home.html maybe you can explain to me, what is my problem now?

from jekyll-timeago.

I'm not 100% sure (I have no access to code, so this is just intuition...), but I think the last problem is due to: you can't access the page object in "includes" files (cause they are generic to the whole site, and not page specific like page.date).

Maybe this guide will be helpful: https://jekyllrb.com/docs/includes/#using-variables-names-for-the-include-file. The whole section explains really well how "includes" works in Jekyll. I recommend you to read it to understand better how this Jekyll feature works.

Please re-open in case you suspect this is really a jekyll-timeago bug and not a Jekyll misuse.

from jekyll-timeago.