Create a content type, "Document".
Create any number of any types of fields on it.
Create a second content type, "Bulletin".
Re-use the fields from document on this content type.

Create content of type "Document". Save it.
Update that content and save a revision.
View the current version -- everything's ok.
View the last version -- everything's ok.

Convert the "Document" to "Bulletin". Map all fields from one to the other.
View the current version -- everything looks ok.
View the last revision -- all the fields are missing.

It doesn't seem to matter what content types, types of fields, number of fields are involved.
What's really strange, is that if I do this to an "ubercart product class" node type, revisions seem to be just fine.

Comments

wjaspers’s picture

wjaspers commented

Noticed that if an "administrator" role is defined in the site, new permissions aren't automatically propagated for new content types to the "adminsitrator" role. This also goes for "convert to __node_type__" permissions. After updating the "administrator's role" to reflect all necessary and re-testing this, the problem is still present.
I thought the above might be a problem; but permissions propagating has to do with core...

Anywho:
I should note that the "Long Text" and "Long Text with Summary" and default "body" fields provided by basic content types are also lost on revisions.

Encarte’s picture

Encarte commented

I didn't understand the relation of #1 with the problem described, but I'm experiencing the same issue with 6.x-1.7

kerasai’s picture

kerasai commented

The difference between D6's CCK and D7's Fields is significant enough that I highly doubt the same issue is affecting both releases.

In D7 the tables that hold the field revision data have a bundle column and my guess is that when the node is converted to its new type, there is no process to cleanup the revision data. When the revisions are loaded, the records are likely not found due to them not having the proper value for the bundle (node type).

alcroito’s picture

alcroito commented
Version: 7.x-1.0 » 7.x-1.x-dev
Status: Active » Fixed

Field revisions support is added to the latest dev version of the 7.x module.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.