Skip to content
This repository has been archived by the owner on Mar 1, 2023. It is now read-only.

Translation of error messages #65

Open
haraldkrischner opened this issue May 3, 2017 · 3 comments
Open

Translation of error messages #65

haraldkrischner opened this issue May 3, 2017 · 3 comments

Comments

@haraldkrischner
Copy link

Hi there!
Though the rest of my Typo3 is in German the formz error messages are English. I have updated the languages but to no success. Any idea?

Thanks.

P.S.: Oh, another small question: How to put the results into an email, is there a best practice or some code to share?

@romm
Copy link
Owner

romm commented May 3, 2017

Hi @haraldkrischner,

Thank you for your report, I will need some more information to be able to help you out:

  • Do you use the English language in your TYPO3 instance (frontend)?
  • Are the error messages provided by default? Meaning were they not written by you/your team?
  • Can you share me a couple of messages that are in English?

You also need to know that FormZ does not provide any german translation at the moment. I am not a native german speaker and did not have any help concerning german translation yet.

For your information, you are able to customize any validator message (localization supported), see official documenation for more information.

I will try to take some time later to register this extension on TYPO3 translation service so people can contribute to translation.


P.S.: Oh, another small question: How to put the results into an email, is there a best practice or some code to share?

For now, FormZ does not provide any sort of helper to send emails, this is your own responsibility to have this feature.

In the future (development is in progress), some new tools will be provided to help you out for this kind of features.

@haraldkrischner
Copy link
Author

My Typo3 backend is set to German and so is config.language = de and config.locale_all = de_DE.UTF-8

This field is required.

This field must contain a valid email address.

I guess these fields may reside somewhere in the Typo3 core?

I could offer you some help with the translation, though I am not experienced in using the typo3 translation service. For now I will take a look into custom error messages…

Oh, another question: The JS validation jumps to the erroneous field on submit. But as I have a sticky header on top of the page that field jumps out of the visible part of the page. Can I hook into that behaviour?

@romm
Copy link
Owner

romm commented May 3, 2017

Ok, indeed these messages come from FormZ core (and not TYPO3 core). So this is "normal" that you don't have a german translation by default.

For now, I'd suggest using the custom messages feature I talked about previously.


Oh, another question: The JS validation jumps to the erroneous field on submit. But as I have a sticky header on top of the page that field jumps out of the visible part of the page. Can I hook into that behaviour?

I'm afraid this is hardcoded and can not be customized for now (see Formz.Form.SubmissionService.js#L121).

This is obviously an issue, and if you really need a fix for that I'll try to release it asap.


If you need more help, do not hesitate to join the Slack channel at #ext-formz.

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

No branches or pull requests

2 participants