I have just done a ULT install on a new drupal 6.28. Everything is installed accordingly. (manual install core functions before ULT). I assign timeslots and then when I try to view them I get,

user warning: Unknown column 'ult_timeslots.nid' in 'on clause' query: SELECT ult_timeslots.start AS ult_timeslots_start, ult_timeslots.end AS ult_timeslots_end, ult_timeslots.ts_id AS ult_timeslots_ts_id, ult_timeslots.fieldnid AS ult_timeslots_fieldnid, node_ult_timeslots.title AS node_ult_timeslots_title, ult_timeslots.fieldnum AS ult_timeslots_fieldnum, ult_timeslots.status AS ult_timeslots_status FROM node node LEFT JOIN ult_timeslots ult_timeslots ON node.nid = ult_timeslots.fieldnid LEFT JOIN node node_ult_timeslots ON ult_timeslots.nid = node_ult_timeslots.nid WHERE (node.type in ('ult_fieldsite')) AND (ult_timeslots.ts_id IS NOT NULL) ORDER BY ult_timeslots_start ASC in /var/www/D6/sites/all/modules/views/plugins/views_plugin_query_default.inc on line 1194.

I have tried with both the DEV version and the alpha 4 version, both give the same results. I can not find what I am doing wrong, any direction would be greatly appreciated.

Comments

jthorson’s picture

Hmmm ... I haven't seen that particular issue before ... but views is definately trying to access a database column that doesn't exist.

I suspect the culprit is that the default view definitions included in the module were for Views 6.x-2.x ... and anyone doing a fresh build now is probably using Views 6.x-3.x. Can you confirm whether you're using Views 2 or 3, and if the latter, see if you can reproduce the problem with Views 2?

Also, where specifically are you attempting to view the list of timeslots, so I know which specific view we're looking at?

tester1313’s picture

Yes, I am using 6.x-3.0, so I will try to drop back to 6.x-2.x.

The view that is causing the error is "site"/ult/field/1/timeslots.

Thanks for the direction and I will be watching for Drupal 7 and/or further improvements.

drupal_hack’s picture

Me (tester1313) again. So I dropped back to views-6.x-2.x. Now when I create timeslots, Firefox can not get to SITE/ult/fields/timeslots/create. Chrom says "The website encountered an error while retrieving http://SITE/ult/fields/timeslots/create. It may be down for maintenance or configured incorrectly."
For all the required modules I have used the latest production version (no devs & and views-6.x-2.x).
Any direction would be most helpful. Do you have a list of versions for the required modules? Have you ever thought about a Distribution version?

jthorson’s picture

Hmmm ... is the /ult/fields/timeslots/create page the only one you cannot access? (i.e. the rest of the pages load fine?)

The error you are getting is coming from the web server, rather than the code ... which suggests that there should be something in your apache error log which can help point us in the right direction. (Could be a php fatal or syntax error, for example).

drupal_hack’s picture

thanks for the direction. this was the same problem as http://drupal.org/node/1621360.
I did not see Date Repeat API as a required module, maybe it can be added to the timeslot required modules.
thanks again for your rapid replies.

jthorson’s picture

Ah ... that makes sense. I believe the date module was restructured a bit since I released ULT. Thanks for digging this up, I'll get a new commit pushed with the Date Repeat API requirement by the end of this week.

drupal_hack’s picture

Thanks again. Now that is have it working I will be trying it out on the basketball program I am part of.

The program is a Youth program with 10 Leagues (grades 4-8 boys and girls). Each league has its own commissioner. Each league also has about 5 divisions, 8 teams in each division. Games are played on the weekends in about 40 different locations.

My first question would be changing the term "Field" (ie. Field status, Field code,...) into "Gym" I should be able to knock this one out. It is complicated by the term "field" being used within Drupal.

Thanks again and I hope you don't mind all the questions.

jthorson’s picture

For the term change, I'd recommend trying the 'String Overrides' module ... hopefully, I've got all instances of 'Field' run through the t() translations function; feel free to open bugs against the module if you find instances which are not. (To be honest, I wrote ULT before I really knew better, and may have missed out on this best practice ... so if it doesn't work, I'll have to put in some time and correct it.)

jthorson’s picture

Status: Active » Fixed

This was already solved in 6.x-1.x-dev ... I'll create an -rc1 release which includes the fix.

Thanks for the report!

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.