Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Translation tags #20

Closed
mikaldl opened this issue Jul 5, 2021 · 2 comments
Closed

Translation tags #20

mikaldl opened this issue Jul 5, 2021 · 2 comments

Comments

@mikaldl
Copy link

mikaldl commented Jul 5, 2021

Eventhough it's not the recommended way of using the i18n like that; it works and it's way nicer than being creative with the names, I really would like to have this not throw an error. (or atleast have a way to ignore it)

image

Multiple dots are the problem; which makes the entire block failing.

@kinglozzer
Copy link
Owner

Thanks, I’d normally reject something like this as it’s best to stick to Silverstripe’s conventions... but in this case, the template parser definitely allows it and it’s a simple change. It should work as you’re expecting in 1.0.1 when the update is approved 😃

@mikaldl
Copy link
Author

mikaldl commented Jul 6, 2021

Thanks for the quick fix! Looking forward to see the update :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants