I'm using the latest non-dev release of views (5.x-1.6) and upgrading to date 5.x-2.7 (with PHP upgraded to 5.2) breaks views that use "now" as a filter argument for CCK date fields.
The problem may be the same as experiences by Drupal 6 users in this issue: http://drupal.org/node/426990.
Comments
Comment #1
mcantelon commentedComment #2
deshilachado commentedWell then, did you try the soultions discussed for 6.x-2.2 ?
Did you try updating to the latest -dev?
Did you flush all caches?
If all this doesn't help, could you attach an export of you date field and of you view as well to help KarenS with debugging?
Comment #3
mikeybusiness commentedI was having the same issue with testing an upgrade from date 5.x-1.8 to date-5.x-2.7 on a test box. I flushed my cache after updating to date-5.x-2.x-dev. This is not time sensitive for me, I thought it might help though.
The PHP Error in the log
Watchdog
Unknown column 'node_data_.field_date_s_value' in 'where clause' query: SELECT node.nid, node_data_field_date_s.field_date_s_value AS node_data_field_date_s_field_date_s_value FROM node node LEFT JOIN term_node term_node ON node.nid = term_node.nid LEFT JOIN term_hierarchy term_hierarchy ON term_node.tid = term_hierarchy.tid LEFT JOIN content_field_date_s node_data_field_date_s ON node.vid = node_data_field_date_s.vid WHERE (node.type IN ('events')) AND (node.status = '1') AND (term_node.tid = '8') AND (DATE_FORMAT(ADDTIME(node_data_.field_date_s_value, SEC_TO_TIME(-18000)), '') >= '') ORDER BY node_data_field_date_s_field_date_s_value ASC LIMIT 0, 10 in /Applications/MAMP/htdocs/hooverlibrary/public_html/includes/database.mysql.inc on line 174.View Export:
This view works fine when I remove the date field from the view
MySql Export
From PhpMyadmin
Comment #4
mikeybusiness commentedNumber 2 of the Troubleshooting guide on the main page states:
For some reason if the updating the database gets botched and you go mucking around for a while without finishing ALL of the updates (like I did) you can get an error with the NOW feature in views. I wasn't even getting the value filed in views, just the option field.
I don't know why but even after I tried to go back and run update.php it no updates were happening. So what I did was restored from a backup to the last state before the update and re-ran the updates again. I caught this error.
If you see this, run update again. It fixed the offending table entry in the database for me. All is well as far as I can tell - the view looks good for me. Maybe you could try this mcantelon.
Comment #5
mikeybusiness commentedUpdate:
If I upgrade to version 2.7 following all of the troubleshooting guidelines views with filter date NOW will work properly. However, if I go to the content type and click "edit" then "save" without changing anything all views using the filter by date for that field will break. When I navigate to the view setup, the "Value" field will be missing.
What would be the best information to present so that I could get some ideas on what to do?
Comment #6
lias commentedI'm getting this same error message in my logs for the date, a bunch of them, using the latest dev version of date, dateapi although I am not having problems displaying the date in my views. It does show up correctly although the actual date is off.
Comment #7
arlinsandbulte commentedVersion 5.2 is critical bugfix only, no other support, no new features.