You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 28, 2019. It is now read-only.
I have the following data in a my tanslations.yml file :
general:
404:
title:
en: "404 Page Not Found"
fr: "404 - Page non trouvée"
de: "404 Seite nicht gefunden"
es: "404 Página no encontrada"
pt-BR: "404 Página não encontrada"
subtext_html:
en: 'The page you requested does not exist. Click here to continue shopping.'
fr: "Cette page n'est pas disponible. Retourner au magasin"
de: 'Die von Ihnen angeforderte Seite existiert nicht. Klicken Sie hier, um den Einkauf fortzusetzen.'
es: 'La página que ha solicitado no existe. Haga clic aquí para continuar la compra.'
pt-BR: 'A página que você solicitou não existe. Clique aqui para voltar às compras.'
And I can't have access to this data in my 404.liquid page:
---
title: Page not found
published: false
---
{% extends theme %}
{% block 'content' %}
{{ 'general.404.title' | translate }}
{{ 'general.404.subtext_html' | t }}
{% endblock %}
In locomotive/mounter/translation.rb file there is just 2 fields: key and values
Does this mean that we can't structure translations data like this?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I have the following data in a my tanslations.yml file :
And I can't have access to this data in my 404.liquid page:
In locomotive/mounter/translation.rb file there is just 2 fields: key and values
Does this mean that we can't structure translations data like this?
The text was updated successfully, but these errors were encountered: