Closed (fixed)
Project:
Content Construction Kit (CCK)
Version:
6.x-1.x-dev
Component:
text.module
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
27 Mar 2006 at 12:10 UTC
Updated:
18 Apr 2006 at 00:15 UTC
The update method supplied with the recent db scheme change for text.module (v1.15) drops the tables but does not recreate the new ones.
Marked as critical since it breaks text.module functionality altogether :-)
Figuring out what the expected fields are by looking at the code in content_field function in content.module is not trivial. Maybe you could post the new db scheme here them so that we can at least manually create it ?
Comments
Comment #1
yched commentedIt seems that new text fields creation is also broken :
Unknown table 'node_data_' query: DROP TABLE node_data_ in (...)\includes\database.mysql.inc
Occurs after the first form page has been submitted (the one where you specify the field type)
Comment #2
jonbob commentedThe new db scheme is dynamic, so it will differ depending on which fields you have created. A node_data_(your field name here) table should be created each time you make a new text field. This is the first part of a two-step plan; eventually we will move fields that are used in only one content type into a single table for extra efficiency. Even this first step is a speed boost, though.
For each table, you'll have:
vid int unsigned NOT NULL default '0',
delta int unsigned NOT NULL default '0',
nid int unsigned NOT NULL default '0',
(your field name)_value varchar(255) NOT NULL default '',
(your field name)_format int unsigned NOT NULL default '0',
but the specifics will differ (delta and format will only be there if multiple values or filtering are allowed, respectively).
I just checked in a patch that I hope will solve this problem for you. It turns out there is some weird interaction between unset() and static variables.
Comment #3
yched commentedThe issues with text field creation are solved.
Which reveals other issues with node creation (and probably update) :-)
There probably is a missing implode on $column_placeholders in the lines
in function content_field('update' / 'insert')
Comment #4
yched commentedHum. Not very readable. And it seems preview is broken since drupal.org upgrade. Repost :
The issues with text field creation are solved.
Which reveals other issues with node creation (and probably update) :-)
There probably is a missing implode on $column_placeholders in the lines
in function content_field('update' / 'insert')
Comment #5
jonbob commentedCorrected. Thank you.
Comment #6
(not verified) commented