Warning when trying to create a content type: News; the content type is not created.

Reference: Drupal cvs Aug 07, 2006; CCK cvs Aug 07, 2006; PHP 4.4.0; Mysql 4.1.11

* user warning: Unknown column 'type_name' in 'field list' query: INSERT INTO node_type (type_name, label, description, help, title_label) VALUES ('content-news', 'News', '', '', 'Title') in /usr/local/apache/htdocs/site.com/drupalcvs/includes/database.mysql.inc on line 128.
* user warning: Unknown column 'nt.type_name' in 'order clause' query: SELECT * FROM node_type nt ORDER BY nt.type_name ASC in /usr/local/apache/htdocs/site.com/drupalcvs/includes/database.mysql.inc on line 128.

Darly

Comments

JonBob’s picture

Title: content types - warning message » CCK incompatible with CVS HEAD due to configurable content type patch
Priority: Normal » Critical

CVS HEAD just added a "node_type" table that conflicts with the one used in CCK.

chx’s picture

Easy. In HEAD just change the table name. No need for an upgrade path. There are reasons why it's called developer version. There is a disclaimer on the module downloads page.

For 4.7, create a simple update that renames the table. The 4.8 version will use this table already and not clash.

tatere’s picture

sorry, trying to get this running for my own development - change WHICH table name? the one that CCK uses? or the new one created by system?

yched’s picture

I think he meant the module's table

drewish’s picture

i marked http://drupal.org/node/79137 a duplicate of this

dodorama’s picture

Since drupal 4.8 is still a moving target is normal to have issues.
But I think that, at least for the UI, as I wrote in the post mentioned by drewish, it seems that there's no place for CCK in the way custom content are created in the current drupal head. So the question is: are the plans for integrating them and let user have a smooth transition from CCK 4.7, drupal 4.8 custom content creation and the future CCK 4.8 release.
Cause I think that this module, that is gradually replacing Flexinode, is vital for drupal (and a lot of users).
So, how can we help you, developer, to keep an eye on code and in the meanwhile try to let user have a smooth experience using this features?

Dodo

... I know my english is ugly.

Robardi56’s picture

In fact, I think we should not worry that much.
I can't image the devs just releasing 4.8 with no way to migrate current cck to 4.8 cck.

Jonbob the creator of cck is the one maintaining head and 4.7 branch himself.... he will most certainly provide a way to upgrade.
4.7 cck is considered stable release, not cvs, developpers of stable core module DO provide migration to next version.

Of course, official word would be welcome.

Cordially,
Brakkar

JonBob’s picture

Status: Active » Fixed

The table has been renamed; this should avoid the upgrade conflict. There are still plenty of other compatibility tasks to perform, though.

As noted by chx above, users will need to upgrade to the latest 4.7 version of CCK before upgrading to Drupal CVS in order to avoid this conflict.

Robardi56’s picture

Thanks for the answer JonBob.

And thanks for the cck, you are doing a great job. This module is really great and will bring drupal a step further.

Brakkar

Anonymous’s picture

Status: Fixed » Closed (fixed)