Anonymous | Login | Signup for a new account | 2023-09-24 11:12 CDT | ![]() |
Main | My View | View Issues | Change Log | Roadmap | Docs | Wiki | Repositories |
Dependency Graph | [ View Issue ] [ Relation Graph ] [ Vertical ] | |||
|
||||
|
Viewing Issue Simple Details | |||||
ID | Category | Type | Reproducibility | Date Submitted | Last Update |
0000396 | [In-Portal CMS] Data Management | bug report | always | 2009-10-16 16:28 | 2010-01-11 22:05 |
Reporter | Dmitry | View Status | public | ||
Assigned To | alex | ||||
Priority | critical | Resolution | fixed | ||
Status | closed | ||||
Summary | 0000396: Issues after Editing "Root" of the Catalog | ||||
Description |
I have came across some issues when after Editing "Root" of the Catalog. In particular I tried changing the Permissions and when clicked Save saw some SQL errors results from not having (empty) a Parent Category Id (we know why - no parent exists for Root category). Thus no changes were saved or may be partially. All after lead to another issue with Semaphores LOCKING the saving process for ANY category changes. Issue was manually resolved when record from "Semaphores" table was removed. Conclusion, we need to: 1. Prevent any issues with Editing Root (or not allow it at all) 2. Need to think of the scenarios when issue with Semaphores can be repeated and how to resolved this. |
||||
Additional Information |
Main | My View | View Issues | Change Log | Roadmap | Docs | Wiki | Repositories |
Web Development by Intechnic![]() In-Portal Open Source CMS |