This idea is a bit complex but a really useful feature.
I wanted to rename the fields but found I needed to change the .php which I did but felt this was the wrong approach.
So how about a cusomised field names?
Page: 1
Author | Post |
---|---|
#1 Thu 24 April, 2008 18:51
|
|
Member
Registered: Apr 2008
Posts: 8
|
This idea is a bit complex but a really useful feature.
I wanted to rename the fields but found I needed to change the .php which I did but felt this was the wrong approach. So how about a cusomised field names? |
#2 Fri 25 April, 2008 7:39
|
|
Administrator
Registered: Apr 2008
Posts: 324
|
We'll certainly be looking at better language support in a future version, so that will help if you just want to change how a field is named.
We could go a little further and allow the user to add, edit, or remove their own set of fields. That does complicate the development and usage, though. _______________ AutoDirector administrator |
#3 Sun 27 April, 2008 14:57
|
|
Member
Registered: Apr 2008
Posts: 8
|
Brill!
Just needed to change a field name say from Model to Trailer Model. Also... is there a reason why some fields are number fields on the database? As it would be good to be able to store what you like in each field as well. Thanks |
#4 Tue 29 April, 2008 9:59
|
|
Administrator
Registered: Apr 2008
Posts: 324
|
You can change the model fieldname in /client/carlist.js - do a search for "model:" (without the quotes) and change it accordingly. You might need to alter your template to give the field more space - change the width setting for "#autodirector_list dt" and "#autodirector_vehicle dt" in the CSS file you're using.
With regard to the database fields, it's generally a good idea to use the right SQL type. It minimises the storage space required, adds an extra level of field validation, and makes searching more efficient. Most fields are strings, but some are obviously numeric, e.g. the mileage, price, number of views, etc. _______________ AutoDirector administrator |
Page: 1