This project is read-only.

Field storage inconsistency

Topics: Troubleshooting, Writing modules
Feb 6, 2012 at 3:55 PM

I'm not sure if this is intended or not:

If a content item is instantiated (ContentManager.New()) and its field(s) modified (I've used TextField specifically but this should be the same with all fields since their storage mechanism is the same) before the item is created, then the fields are stored in the ContentItemRecord table (Data column). This causes that the saved data is not accessible later, nor from the admin UI nor by fetching the item's field. However if the item is created prior to modifying the field the field data is stored as it happens when editing from the admin UI: in the ContentItemVersionRecord table (and is then accessible normally).

Is this by design?

Feb 6, 2012 at 6:25 PM

Sounds like a bug.

Feb 6, 2012 at 6:53 PM

Then I've opened one.

Feb 6, 2012 at 6:55 PM