Anonymous | Login | Signup for a new account | 2024-03-28 06:40 CDT |
Main | My View | View Issues | Change Log | Roadmap | Docs | Wiki | Repositories |
Relationship Graph | [ View Issue ] [ Dependency Graph ] | |||
|
||||
|
Viewing Issue Simple Details | |||||
ID | Category | Type | Reproducibility | Date Submitted | Last Update |
0000580 | [In-Portal CMS] Data Management | bug report | always | 2010-02-24 02:32 | 2010-08-30 09:44 |
Reporter | alex | View Status | public | ||
Assigned To | Dmitry | ||||
Priority | normal | Resolution | fixed | ||
Status | closed | ||||
Summary | 0000580: Issues with change log section | ||||
Description |
There are a few issues with change log section: * warning message about missing Status field * only first letter of each changed field value is shown * there no way to delete session log or change log records * even if you manage to delete change log record, then new change log records will be created, indicating delete from change log :) ----------------- I've stumbled upon another issue yesterday: we have CachedRating field (in category items), that has "0.0000000000" value in database and "0.00" default value (format with 2 digits after comma). When value is submitted from form, then we have "0.0000000000" in original field and "0.00" as field value. They are compared as strings (to determine changes) and they differ resulting wrong change log record to be created. I propose for each changed field we compare it's formatted original field and normal field values to determine if they are really different. ----------------- When field has a really long value and it is changed, then all that value is displayed in grid makes it near to impossible to use it. I propose we add new format for "kChangesFormatter", like "auto_cut" or something similar and then it can cut each changed field value to normal size, when displayed in grid. When viewing change log record details, then no cutting should be made of course. |
||||
Additional Information | Also change log records are not optimized. For example when you open product editing page and change one field, then press on "General" tab and change that field again and again, then press Save. As a result you will get 3 change log records, but you've opened editing page only once, so we could merge all change log records together. |
Main | My View | View Issues | Change Log | Roadmap | Docs | Wiki | Repositories |
Web Development by Intechnic In-Portal Open Source CMS |