HEADER

First of all thanks for this great component!

Just been playing with the new validation features of 2.3. Looking good so far.

Since my customers aren't English speakers (readers), I quickly hacked the validation messages. Might not be perfect, but it seems to work. The edited file is attached to this message.
I'll try to alter the regex's ($'s and such) as well to get an entirely localized version.

As a suggestion how about putting that stuff in external files and conditionally include them (like with _en suffixes), depending on a language setting (to be added)? Seems to me to be the easiest way to handle translations.


On a sidenote, has anybody a good tutorial on how to do server side validation with this component? Thanks in advance.


Dave

Hi Dave,

Thanks for that, I have a hacked version of 2.3 with pretty much all of the language (front & back-end) pulled out into Joomla 1.0 style define files. I'll make sure that these get added in. I'm hoping that Max will adopt these mods for a future version.

Don't know of any good server-side validation tutorials for ChronoForms - what kind of thing do you have in mind?? Pretty much anything can be done with a little php.

Bob

GreyHead wrote:

QUOTE:

Thanks for that, I have a hacked version of 2.3 with pretty much all of the language (front & back-end) pulled out into Joomla 1.0 style define files. I'll make sure that these get added in. I'm hoping that Max will adopt these mods for a future version.

Sounds good. I could do a German translation if there's any demand.

Hi Dave,

I had a look at your translations and all looks good, but my JavaScript skills aren't good enough to add a language include to the existing files. Maybe someone else knows how to do that?

Bob

Thanks Dave, we are planning some changes to JS validation and sure the German translation will be included with someway to choose language at the backend.

Regarding the server side validation, I see some requests for it and so I will try to have a solution soon, but what I have in mind now is that the form action URL should be the same as the form URL, the 2 functions at chronocontact.php will be combined and we will switch the code by checking if this is a submitted form and VALID, if you are in rush then you can try doing this yourself, I am planning to have it but not sure when exactly as there is too many other earlier requests too

Thanks again!!

Max

GreyHead wrote:

QUOTE:
I had a look at your translations and all looks good, but my JavaScript skills aren't good enough to add a language include to the existing files. Maybe someone else knows how to do that?

Well, keep it simple.

You could always turn validation.js into validation_js.php, replace the static text messages with variables, put them into include files (one for each language), and include them depending on an additional language setting which would just be another drop down menu in the ChronoForms configuration, nothing too fancy. There you go.

(I'd do it myself, if I had more time at hand right now...)