View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003157 | Composr | core_fields | public | 2017-03-26 09:59 | 2017-11-26 15:20 |
| Reporter | Chris Graham | Assigned To | |||
| Severity | Feature-request | ||||
| Status | non-assigned | Resolution | open | ||
| Product Version | |||||
| Fixed in Version | |||||
| Summary | 0003157: Allow field hooks to self-categorise | ||||
| Description | We currently have this code in sources/fields.php: $orderings = array( do_lang_tempcode('FIELD_TYPES__TEXT'), 'short_trans', 'short_trans_multi', 'short_text', 'short_text_multi', 'long_trans', 'long_text', 'posting_field', 'codename', 'password', 'email', do_lang_tempcode('FIELD_TYPES__NUMBERS'), 'integer', 'float', do_lang_tempcode('FIELD_TYPES__CHOICES'), 'list', 'list_multi', 'state', 'country', 'region', 'tick', do_lang_tempcode('FIELD_TYPES__UPLOADSANDURLS'), 'upload', 'upload_multi', 'picture', 'picture_multi', 'video', 'video_multi', 'url', 'url_multi', 'page_link', 'theme_image', do_lang_tempcode('FIELD_TYPES__MAGIC'), 'guid', do_lang_tempcode('FIELD_TYPES__REFERENCES'), 'isbn', 'reference', 'reference_multi', 'content_link', 'content_link_multi', 'member', 'member_multi', 'author', //do_lang_tempcode('FIELD_TYPES__OTHER'), 'color', 'date', 'just_date', 'just_time', 'tel', Will go under OTHER automatically ); Ideally each hook would just define a category, and the code would automatically structure the selection list. That's more modular. | ||||
| Tags | Good for training | ||||
| Time estimation (hours) | 1 | ||||
| Sponsorship open | |||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2017-03-26 09:59 | Chris Graham | New Issue | |
| 2017-11-26 15:20 | Chris Graham | Tag Attached: Can implement during live chat | |
| 2019-06-27 19:42 | Chris Graham | Tag Renamed | Can implement during live chat => Good for training |