I have a weird issue with translating the Userforms backend (the cms) - so it has nothing to do with Translatable. I just can't get the templates/Incluses/AddField.ss template to translate. Everything else translates fine, the $lang['AddField.ss'][..] are all there, Still I get the english 'select a Field', 'Add' etc...
The funny thing is - when I copy the template to the FieldEditor.ss (from where it was included) and alter the lang to $lang['FieldEditor.ss'][..] it translates fine...
I'm clueless... Even tried renaming the AddField.ss, adding other translations to it... This particular piece of code just won't translate... ????
Wasn't sure the best place to suggest a few features. Hope this is an acceptable spot.
- Ability to right click and copy fields (similar to the site tree)
- The ability to set col on multi row text fields
- The ability to set size on single row text fields
- Validation Rules
- A Text Field Group would be handy
- The ability to add hint text or a secondary label (ex: (###) ###-####)
- The ability to specify that a field be inline with the previous field
The best place to post feature requests is here: http://open.silverstripe.com/newticket.
Make a new ticket for every feature - the devs like that.
I like your suggestions about hinttext/secondary label and inline fields - so please at least post these...
Thanks theAlien! I haven't had time to create the tickets yet, but I have been working on a custom Field that adds:
- RightTitle Support
- Default Value Support
- Inlineing of fields
The problem is that this will be for a TextField, and I'll have to create one for each field type. Also important to note that inlineing is supported by CSS classes being added, it is up to your CSS to properly inline the fields.
If anyone is interested I will upload the code here after I have some more miles on it.
One other feature I thought of (but think it would be somewhat difficult) is to be able to modify the field type of an existing field.
They should just be options on the default editable form field - well they would be good options to have. For inlining of fields a checkbox in the configuration options which adds a class to the form field would be enough.
Default value support that would be slightly tricky (as to work with dropdowns, check boxes etc), then getting it to work with checkboxs then you have to get dynamic updating etc as well working so when people add an option it updates the default option list. Its quite a bit of work but I think it would make it would be pretty cool to have.
No, Not Better Reporting is built in. We attempted to use complextablefields to display the submissions but we ran into too many issues getting that to work. A overhaul of the Submission report would defiantly on the cards though, if you have any suggestions feel free to post them.