Difference between revisions of "Talk:Club and Clinic Details"
From Charitylog Manual
| Line 11: | Line 11: | ||
3) Extension Databases should be one-per-section, so it looks more like the client record. Not exactly the same - we don't want a whole new UI for creating and reorganising the sections, just dynamically create a section for each ext db, and put the fields in it. | 3) Extension Databases should be one-per-section, so it looks more like the client record. Not exactly the same - we don't want a whole new UI for creating and reorganising the sections, just dynamically create a section for each ext db, and put the fields in it. | ||
| + | |||
| + | 4) Vertical alignment of content of columns in Incomplete Meetings differs | ||
| + | |||
| + | 5) "No schedules attendees on" mouseover in Incomplete Meetings section shows garbled PHP | ||
Latest revision as of 14:29, 15 March 2024
1) All these defaults should be no/zero
- Bring Forward Client Attendances? - Gap Between Client Attendance - Save Completed Non-Attendances Into Client History? - Record Notes in Completion? - Record Payments? - Record Donations?
2) Extension Database lozenge always visible even if there are no linked ext dbs.
3) Extension Databases should be one-per-section, so it looks more like the client record. Not exactly the same - we don't want a whole new UI for creating and reorganising the sections, just dynamically create a section for each ext db, and put the fields in it.
4) Vertical alignment of content of columns in Incomplete Meetings differs
5) "No schedules attendees on" mouseover in Incomplete Meetings section shows garbled PHP
