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
Having studies the GRAV and Gantry 5 docs there does not appear to be a way of overriding the Gantry 5 language strings and having them be retained after either a Gantry 5 update or a theme update.
As a specific example, /user/plugins/gantry5/admin/translations/en/nucleus.yaml contains a number of string including GANTRY5_ENGINE_BLOG_ITEM_NEXT_POST and GANTRY5_ENGINE_BLOG_ITEM_PREV_POST which are "Next post" and "Previous post" respectively.
You can add German with /user/plugins/gantry5/admin/translations/de/nucleus.yaml file and that will work but the whole new folder will be removed by a gantry5 plugin update.
There should be a mechanism to override these constants by language that is not overwritten again by updates. I have tried using a "language.yaml" file but that does not appear to work.
After discussion with @mahagr he needs to investigate.
The text was updated successfully, but these errors were encountered:
Having studies the GRAV and Gantry 5 docs there does not appear to be a way of overriding the Gantry 5 language strings and having them be retained after either a Gantry 5 update or a theme update.
As a specific example, /user/plugins/gantry5/admin/translations/en/nucleus.yaml contains a number of string including GANTRY5_ENGINE_BLOG_ITEM_NEXT_POST and GANTRY5_ENGINE_BLOG_ITEM_PREV_POST which are "Next post" and "Previous post" respectively.
You can add German with /user/plugins/gantry5/admin/translations/de/nucleus.yaml file and that will work but the whole new folder will be removed by a gantry5 plugin update.
There should be a mechanism to override these constants by language that is not overwritten again by updates. I have tried using a "language.yaml" file but that does not appear to work.
After discussion with @mahagr he needs to investigate.
The text was updated successfully, but these errors were encountered: