I found this bug trying to disable the 'body' field of image node type.

As I translated the 'body' field label with i18n content type, the module switch back to the previous translation each time I try to modify it.

This is a pretty bad bug, because of the i18ncontent_node_info() method, which rewrites my previously translated content types enabling their bodies, even if I disabled it meantime, so it breaks behavior of _node_types_build() method, which does not take care of real data in table node_type anymore.

The simple way to fix may be to add a check in this method, first check if body is enabled or not in database, and if it is, override the infos, else not.

I'm not sure for the fix, must be something like that I think.

Comments

Anonymous’s picture

Anonymous (not verified) commented

Here is a way to reproduce a possibly related bug :

1- Start with a fresh Drupal 5.12 installation
2- Create a new content type with any Name, Types and Description.
3- Download the modules i18n and CCK in sites/all/modules
4- Sequentially, respecting the dependencies (it takes a few steps), activate i18n - content types
5- Try to edit the new content type. It won't work

I will post it separatly as well, not just as a comment on a possibly related bug.

jose reyero’s picture

jose reyero commented
Status: Active » Closed (won't fix)

These experimental modules won't be supported anymore for 5.x

Upgrade to 6.x if you want these features working.

pounard’s picture

pounard
Primary language French
commented

May a simple patch be commited for this issue, even in -dev version?

If, someday, you release a security release for drupal 5 it may be nice to have those sort of bugs fixed as bonus with it (as the bug is reproductible and it's cause is found, it won't cost more than 5 minutes to resolve it and put in HEAD).