ChiliProject is not maintained anymore. Please be advised that there will be no more updates.
We do not recommend that you setup new ChiliProject instances and we urge all existing users to migrate their data to a maintained system, e.g. Redmine. We will provide a migration script later. In the meantime, you can use the instructions by Christian Daehn.
Document category is not saved properly (Bug #1087)
| Status: | Closed | Start date: | 2012-07-22 |
|---|---|---|---|
| Priority: | Normal | Due date: | |
| Assignee: |  Holger Just |
% Done: | 0% |
| Category: | Documents module | ||
| Target version: | 3.4.0 | ||
| Remote issue URL: | Affected version: | 3.1.0 |
Description
Not sure if this is not a duplicate, but I could't find it reported yet.
When you do create a document, and you use custom categories for them, always the first category is saved for the document. When you update it later, it works normally.
I am experiencing this on ChiliProject 3.1.0.99614354a, it's possible that in newer version it is already fixed?
Associated revisions
Set default category_id instead of the object #1087
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.
History
Updated by Tomáš Jukin at 2012-08-15 05:32 pm
Any update fot this bug? It is really annoying. And it is in the latest version. Confirmed.
- Target version set to 3.4.0
Updated by Andrew Smith at 2012-08-16 02:27 am
Just confirmed this.
It happens when there is a default value selected for the enum.
Updated by Holger Just at 2012-08-20 06:50 pm
This should be fixed in 7a4b664 for Rails 2.3. With Rails 3, it should have worked right away. Time we updated...
- Assignee set to Holger Just
- Status changed from Open to Closed