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
Error messages in form_validation_lang.php not contained in a namespace #539
Comments
I agree with you, however I don't think it would be good to change it because it would then break all existing sites when they upgrade. |
I see your point, maybe possible in CI3. |
With CI 3.0 coming soon, we better decide on this one soon. +1 from me, if it's done with a proper explanation in the upgrade guide. Any other opinions? |
Form validation language line keys were not prefixed. They are now prefixed with 'form_validation_' in order to avoid collisions. The old keys will still work if a prefixed match is not found, but are DEPRECATED and will be removed in the next major version. Also added upgrade notes and changelog entries for the new error message format from PR #961.
See the above referenced commit. |
One question, the format tweaks is for the custom callback rule and the field name too suggest just apply only for callbacks array(
'field' => 'fieldname',
'label' => 'lang:fieldname', #bit tedious for converting this
'rules' => 'required|callback__validate_fieldname' #yes suggest just prefix this ....
); what do you guys think ? |
I can't understand what you're trying to say. |
what i mean is from 'label' => 'lang:fieldname'
form_validation_fieldname # it is very much not convenient to name spacing this no need to using language key name spacing. sorry for my bad english what i mean is just namspacing the callback language key that's enough, |
Form validation language line keys were not prefixed. They are now prefixed with 'form_validation_' in order to avoid collisions. The old keys will still work if a prefixed match is not found, but are DEPRECATED and will be removed in the next major version. Also added upgrade notes and changelog entries for the new error message format from PR bcit-ci#961.
For example, it should be:
Rather than:
The text was updated successfully, but these errors were encountered: