my findings after some experimentation:
content::item::new does only allow new items of content_type cr_revisions (or a subtype) to be created. if I understand correctly, it doesn't provide unrevisioned attributes to items on its own.
the easiest way I see at the moment to have unrevisioned attributes to an item is to manually create an unrevisioned table (with the unrevisioned attributes) and to insert a row there when creating the new item with content::item::new (and remove the row when deleting the item).
does anybody have to add something to this?
next I wonder about the x-view that is created when I create a new content-type (subtype of cr_revisions). it contains a row for every revision and some columns (amongst others):
creation_user
creation_date
creation_ip
last_modified
modifying_user
modifying_ip
publish_date
I kind of "expected" creation_* to reflect the initial creation of the item or the first revision of that item, and last_modified & modifying_* to reflect each revision itself.
however,
* creation_date and last_modified always seem to be the same and reflect the revision (while I thought creation_date would reflect the item),
* so are creation_ip and modifying_ip,
* creation_user reflects the revision not the item,
* modifying_user is always empty?
* publish_date -- don't know what this is
in the definition of the x-view, all above columns come from the row in the acs_objects table that provides the object for a particular revision, so this probably explains why.
So, am I correct when I say that creation_* in the x-view reflects the creation of a new revision, and last_modified & modifying_* for editing a particular revision afterwards? This seems strange as the whole point of revisions in the content-repository is not to edit them, but to create a new one when something changes.
greetz,
koen.
