since a while, i became this error:
user warning: Unknown column 'node_data_field_url.field_url_value' in 'where clause' query: SELECT node.nid AS nid, node.title AS node_title, node_revisions.body AS node_revisions_body, node_revisions.format AS node_revisions_format FROM node node LEFT JOIN node_revisions node_revisions ON node.vid = node_revisions.vid WHERE node.type in ('hilfe') AND node.language = 'de' AND 'node' LIKE node_data_field_url.field_url_value in /var/www/web3/html/sites/all/modules/contexthelp/contexthelp.module on line 296.
Comments
Comment #1
darren.ferguson commentedIssue was for not checking if the user actually had permissions to view this. This issue has been resolved in the development branch for the module can you please update from that this evening. The code will be in there.
Comment #2
Babalu commentederror still there:
Unknown column 'node_data_field_url.field_url_value' in 'where clause' query: SELECT node.nid AS nid, node.title AS node_title, node_revisions.body AS node_revisions_body, node_revisions.format AS node_revisions_format FROM node node LEFT JOIN node_revisions node_revisions ON node.vid = node_revisions.vid WHERE node.type in ('hilfe') AND node.language = 'de' AND 'admin/reports/dblog' LIKE node_data_field_url.field_url_value in /var/www/web3/html/sites/all/modules/contexthelp/contexthelp.module in Zeile 296.
i have made update and cache clear after updating to the new dev branch
Comment #3
darren.ferguson commentedDid you add the cck node via node import or did you do something else?
The node type is normally context help
Comment #4
Babalu commentedi have made a content type (hilfe)
i don't do anything with cck node and node import
Comment #5
darren.ferguson commentedThat is the problem the CONTEXTHELPCCK file holds the CCK node for the contexthelp that the module utilizes and the FAQCCK holds the CCK definition for the FAQ type.
You need to use them in order for this to work since it is what the module was designed off.
Comment #6
Babalu commentedok fixed. it was my failure :)
i'm now using the rc2 version.
the dev has no help button on my site, right at the top
maybe my failure, too ?
Comment #7
darren.ferguson commentedYes the development version is missing the button, will be adding it in for tonight, the development version has a lot of fixes hence would advise switching too it tonight, will be updating rc2 tomorrow with probably rc3 for a final sanity check before 1.0 is released
Comment #8
darren.ferguson commentedComment #9
notebene commentedCan you explain this better? Are you saying that even though it 'appears' in the configuration that I can select Page or any other content type to use, what I 'really' need to do is create two content types, specifically called CONTEXTHELPCCK and FAQCCK and select each, respectively, in the configuration to get rid of this error (which I am also getting)?
Comment #10
darren.ferguson commentedThe reason they were not created automatically is until the latest Drupal release there was a bug which would not allow them to be created automatically.
For the module in its current state to work you need to import the two content types provided in the files CONTEXTHELPCCK and FAQCCK.
The module utilizes views to provide the information hence this is the reason it is needed otherwise the views would have to be configured by the user.
Comment #11
notebene commentedThanks for the reply.
Ok...uhm...how do I import them? :D
Comment #12
notebene commenteddoh!
nm :(
Comment #13
notebene commentedIt created the context help, but it didn't create the faq. I get an error that says "an illegal choice has been detected. please contact the site admin." Under that in green it says there was an error trying to create that content type.
Any thoughts?
Edit: I'm using rc4.
Comment #14
TechnoBuddhist commentedJust for anybody else who get's this issue; which I did for all users except admin
you need to enable permissions for 'field_url'.
Thanks for a nice module!!!
Comment #15
lelizondo commentedI'm still having this error, the module creates the content types by itself during the install process, the view is also created, but I still have the problem. I'm using a table prefix in my database and my guess is that it has something to do with it, since I've used this module on other sites with no table prefix and it works OK.
Maybe you could reproduce the problem using a table prefix.
Edit: I can confirm that this problem appears when using a table prefix in the DB.
Edit 2: I didn't try the dev version of this module since it appears that is older than the stable version (1.0)
Comment #16
Raf commentedGot the same problem, also using the default content type the module creates. I'm not using a db prefix, though.
Edit: The query giving the error is this:
SELECT node.nid AS nid, node.title AS node_title, node.language AS node_language, node_revisions.body AS node_revisions_body, node_revisions.format AS node_revisions_format FROM node node LEFT JOIN node_revisions node_revisions ON node.vid = node_revisions.vid WHERE node.type in ('contexthelp') AND node.language = 'en' AND 'user/register' LIKE node_data_field_url.field_url_valueThe part giving the problem, is this:
AND 'user/register' LIKE node_data_field_url.field_url_valueIt doesn't find node_data_field_url.field_url_value because node_data_field_url is not in any FROM... nor is it in the database at all.
Edit 2: Node_data_field_url isn't created in context_help.install, either.
Edit 3: Field_url_value is in the table content_type_contexthelp. Now I just gotta find where it creates that query...
Edit 4: Found it. When you haven't given permissions to view the field field_url, the module'll throw these errors. If the role has permissions to view field_url, things work just fine.