[MAGNOLIA-1734] Magnolia data corruption when entering content in Magnolia Created: 10/Sep/07 Updated: 17/Mar/09 Resolved: 11/Sep/07 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | 2.1.5 |
| Fix Version/s: | 3.0.3 |
| Type: | Bug | Priority: | Major |
| Reporter: | Rajesh Srinivasan | Assignee: | Philipp Bärfuss |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Date of First Response: |
| Description |
|
We have a problem of magnolia data corruption when we enter content in magnolia. We have large web site whose contents are maintained in magnolia. When we enter some content and expect it to be available it behaves randomly to have magnolia data corruption. We need to delete the node and recreate again |
| Comments |
| Comment by zam6ak [ 10/Sep/07 ] |
|
How about some more info? How is the repo getting corrupted?What was the usage scenario? |
| Comment by Boris Kraft [ 10/Sep/07 ] |
|
Please read this: Unless you explain how we can reproduce what you see, your issue report is worthless and wastes our time. |
| Comment by Philipp Bracher [ 11/Sep/07 ] |
|
Please migrate to 3.0 |