[TYPO3-dev] feature suggestion ( show db_fieldnames in backend )
Martin Ficzel
martin.ficzel at gmx.de
Wed May 3 15:02:04 CEST 2006
when writing typoscript it's not alwas easy to find out wich values are
stored in wich db-field because the be-form is only displaying the
localized description. a nice feature but sometimes annoying when you
try to acess some of these records from ts.
currently i use these infosources
- examine the csc-template an others
- use the configuration module to view the tca configuration
- use phpMyAdmin to look into the table definition
- and in the worst case i create 2 records wich only differ in the field
i'm looking for and afterwards compare them with phpMyAdmin
that all works and i already know most of the fieldnames but i think
that's a common problem. it would be easier to work if the fieldname
would be displayed after the localized title of the field.
i imagine a change in the be-form field-labels like that
"Position:" >> "Position: [imageorient]"
of course that should not be displayed to all users i would suggest to
show these hints for admin users, for users with access to ts-templates
or for users wich have a special key set in the userTSConfig.
i think that could ease the writing of ts-templates a lot ... and the
needed changes will be quite easy.
Question:
1. what do you think about that idea? If you like the idea i will create
a feature request and try to create a patch.
2. Wich option sould be used to hide/show the extra informations.
regards, Martin
PS: a similar feature would be good in the be_user(enableFields)
selectbox. i sometimes have to use trial and error to find out wich
field is really effected by wich option. i think everyone here knows the
situation :-).
here are some examples of confusing items and common errors
Pagecontent:Align ( wich one is the align of the imagecaption ??? )
Pagecontent:Align
Pagecontent:Frames ( wich one is changing the wrapped div for the
content record)
Pagecontent:Frame
Pagecontent:Columns ( is that the numer of images in a row ??? )
but this problem can also be solved with more speaking titles
More information about the TYPO3-dev
mailing list