Defect #11665
New document category is not saved properly
| Status: | Closed | Start date: | ||
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | Documentation | |||
| Target version: | 1.4.5 | |||
| Resolution: | Fixed | Affected version: | 1.4.4 |
Related issues
Associated revisions
add functional test to create non default document category (#11665)
add unit test to get default document category defined on database (#11665)
force set default document category if it is not set on database (#11665)
add position to DocumentCategory in enumerations fixture (#11665)
set default category_id instead of the object (#11665)
Rails 2.3 still has issues with synchronizing the association_id
and association attributes of an object. That means, if you set the
association with an object first and then just set the id afterwards,
the object wins and the setting of the id gets lost.
This is not an issue in Rails >= 3.1 anymore.
Contributed by Holger Just.
add check default document category is not defined on database in tests (#11665)
History
#1
Updated by Toshi MARUYAMA over 9 years ago
- Status changed from Confirmed to Closed
- Resolution set to Fixed
Fixed in 1.4-stable(Rails2) r10233.
2.0-stable(Rails3) has no defect.
#2
Updated by Toshi MARUYAMA over 9 years ago
- Subject changed from Document category is not saved properly to New document category is not saved properly