After my latest cvs updates (date.module 1.7, content.module 1.56.2.10) my some of my views broke (SQL errors). Suspecting a problem with the filter on the date field, I deleted that filter and discovered the date fields are no longer listed in the Filter selector.

The view displays things fine with no errors with the date filter deleted (except it's not filtered by date, of course :-)

Tried resaving the date field configuration, clearing cache, creating a new view, creating new content with new date field ... all without success. I don't suppose this is related to this http://drupal.org/node/60384 getting committed to CCK?

CommentFileSizeAuthor
#14 date.module_0.patch613 bytesyched
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

KarenS’s picture

Yes, this is because of the change to the content module. I'll get a fix committed soon.

KarenS’s picture

Status: Active » Fixed

This fix has been committed.

FiNeX’s picture

Status: Fixed » Active

I've downloaded the fixed date.module, but the problem still remain. Need I to do something more for test the fix? I'm using the latest version of cck, views and date (directly from cvs).

KarenS’s picture

Status: Active » Fixed

You must clear the cache for this to work. Either empty the cache table or go to the modules page and save it. If you still have problems after that, reopen the issue.

FiNeX’s picture

I'm sorry, but the problem is the same after clearing the cache table and saving the module page. Should I test it with the 1.9 revision of the module?

How do the views module collect the data from the cck fields for constructing the combo box of the filter?

FiNeX’s picture

Status: Fixed » Active

I've forget to reassign the status :-)

KarenS’s picture

What version of the content module are you using? It must be at least 1.70 of the cvs version of content.module. Once I branch this module you will be able to use the 4.7 version of content.module, but for now you need the cvs version (because of one function that is named differently in that version).

KarenS’s picture

Just realized how confusing this sounds. Just to clarify on versions:

1) Both the cvs and 4.7 version of the cck content.module work with the 4.7 version of Drupal. My understanding is that neither will work at the moment with Drupal HEAD (this is true for many other modules as well). So you need to be running Drupal 4.7x.

2) The cvs version of the content module is slightly different than the 4.7 version of the content module (one function is named differently). I am using the naming convention used in the cvs version of the content module, so for now you should be using the cvs version of the content module. That function is only used in a couple places so you may not even see errors if you use the wrong one.

I will branch off a 4.7 version of this module in the next week or two that will match the 4.7 version of the content.module and keep the cvs version in synch with whatever changes are made to the cvs version of the content module as it's converted to work with Drupal HEAD. In other words, I am trying to match branches between the date module and the content module -- use the same branch for both.

RayZ’s picture

Both the cvs and 4.7 version of the cck content.module work with the 4.7 version of Drupal.

@KarenS: Are you sure this is still true? I was certain that sometime in the last month I saw that CCK HEAD was beginning to track Drupal HEAD was no longer compatible with Drupal 4.7. This comment is the closest thing I could find in a quick search ...

http://drupal.org/node/78543#comment-124139

Anyway, I switched over to from CCK HEAD to the 4.7 branch for my project on Aug 3rd, and IIRC it was due to some mismatch between CCK HEAD and Drupal 4.7.

RayZ’s picture

Actually, I just looked a the differences between the latest content.module from HEAD (1.71)and 4.7 branch (1.56.2.10) and it appears that the *only* difference right now is the paths to the help.

So hopefully this means the latest date.module *will* work with the latest 4.7 content.module. I'm off to test it ...

KarenS’s picture

agh! No, I'm not sure what works with what any more. I'm using Drupal 4.7 and the cvs version of the content module (but possibly not quite the latest version). It's getting to be hard to tell what combination to use.

I guess I just need to branch this for 4.7 to reduce the confusion...

RayZ’s picture

Yes, it can be confusing trying to keep everything in sync. FWIW, date.module 1.9 does not seem to work with content.module 1.56.2.10 (latest 4.7).

FiNeX’s picture

The tests I've made yesterday, were done with the latest version from CVS of both content and date module. Drupal itself is the 4.7.3.

yched’s picture

FileSize
613 bytes

This is because the op name for filters is now 'filters', and not 'filter operators' any more
Patch included, RTBC IMO :-)

yched’s picture

Status: Active » Reviewed & tested by the community

Er, as I said, RTBC IMO...

RayZ’s picture

I confirm, yched's patch brings the filter fields back.

KarenS’s picture

Status: Reviewed & tested by the community » Fixed

Applied, thanks yched.

FiNeX’s picture

Ok, now it works. date, cck and views modules are working correctly now, I've tested both cvs and 4.7 tagged versions. good work!

Anonymous’s picture

Status: Fixed » Closed (fixed)