user warning: Unknown column [#255794]

It's awesome that someone created such a useful module. Unfortunately under my install of Drupal 5.7, Using Field Reference 5.x-1.0 it throws an SQL error

Here's my steps:
1) Installed CCK (and Field Reference 5.x-1.0)
2) Created two content types, one called speaker with four field (name, title, profile, and photo) and one called event with seven fields.
3) I added a Field Reference (by checking "Select List" for the field) to the event content type
4) Clicked Create Field Button

Page returned:

Created field Speaker.

and throws an SQL error, specifically:

user warning: Unknown column 'nt.type_name' in 'field list' query: SELECT nt.type_name, nfi.field_name, nt.label AS type_label, nfi.label AS field_label FROM node_type AS nt INNER JOIN node_field_instance AS nfi ON nt.type_name = nfi.type_name ORDER BY nt.label, nfi.label in /home/6999/domains/progressivedownload.com/html/projects/drupal/includes/database.mysql.inc on line 172.

It does display the selected Widget: Select List on configuration page (but NO configuration opinions)

When I Click Save Field settings, I taken to the Manage field tab within the Content Type, and get the following errors:




    * user warning: Unknown column 'nt.type_name' in 'field list' query: SELECT nt.type_name, nfi.field_name, nt.label AS type_label, nfi.label AS field_label FROM node_type AS nt INNER JOIN node_field_instance AS nfi ON nt.type_name = nfi.type_name ORDER BY nt.label, nfi.label in /home/6999/domains/progressivedownload.com/html/projects/drupal/includes/database.mysql.inc on line 172.

    * user warning: Unknown column 'nt.type_name' in 'field list' query: SELECT nt.type_name, nfi.field_name, nt.label AS type_label, nfi.label AS field_label FROM node_type AS nt INNER JOIN node_field_instance AS nfi ON nt.type_name = nfi.type_name ORDER BY nt.label, nfi.label in /home/6999/domains/progressivedownload.com/html/projects/drupal/includes/database.mysql.inc on line 172.

    * user warning: Unknown column 'nt.type_name' in 'field list' query: SELECT nt.type_name, nfi.field_name, nt.label AS type_label, nfi.label AS field_label FROM node_type AS nt INNER JOIN node_field_instance AS nfi ON nt.type_name = nfi.type_name ORDER BY nt.label, nfi.label in /home/6999/domains/progressivedownload.com/html/projects/drupal/includes/database.mysql.inc on line 172.

Comment	File	Size	Author
#2	fieldreference.patch	982 bytes	guardian

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

guardian CreditAttribution: guardian commented 13 May 2008 at 10:05

subscribing

Comment #2

guardian CreditAttribution: guardian commented 13 May 2008 at 11:34

File	Size
fieldreference.patch	982 bytes

i may have fixed it while trying to discover what this module actually does, see attached patch

however it seems that i completely miss the point of the module: i was using node reference to inject the content of "node A" inside "node B" by referencing "node A" from "node B" and using the appropriate teaser/full NodeReference's formatters

i thought fieldreference would enable me to do the same + only reference a portion of a node: "node B" references only the image field from "node A"

in the end, this isn't what your module seems to do :/

Comment #3

guardian CreditAttribution: guardian commented 13 May 2008 at 11:35

Component:	User interface	» Code
Assigned:	msheflin	» Unassigned
Status:	Active	» Needs review

Comment #4

deekayen CreditAttribution: deekayen commented 13 May 2008 at 14:18

Assigned:	Unassigned	» deekayen
Priority:	Normal	» Critical
Status:	Needs review	» Needs work

yep, seems to be pretty broken

Comment #5

deekayen CreditAttribution: deekayen commented 13 May 2008 at 21:38

I did some work on it today and committed what I did and #2 to CVS DRUPAL-5. I won't be working on it tomorrow, so that's a good window for someone else to work on a patch. I turned on -dev tarballs, but it hasn't packaged up yet for today.

Comment #6

guardian CreditAttribution: guardian commented 15 May 2008 at 23:01

Assigned:	deekayen	» guardian
Status:	Needs work	» Closed (won't fix)

this issue won't be fixed because it was reported against a non working version of the module
the 5.x-1.0 release shouldn't have been published since at the time even CVS HEAD was not functional

module is going under active development, please stay tuned for a future stable release