Error related to date filter/argument and views

Hi, is the issue you are describing similar to http://drupal.org/node/784084 ?

I'm having the same issue. Disabling Date fixes the problem. Help please.

Yes, it's the exact same, except (perhaps it's like this for you) it repeats many times. I am totally unable to use filters or arguments with date. Does anyone else have this issue? Question for maintainer: do you think this is NOT a date issue, but a problem with another module's interaction? I got this error after upgrading Drupal to the latest code base (6.16)-Edit-Whoops, I meant 6.17.

I was hoping you did ;) I'm going to test it on a new site and see if the issue continues. If it works, the next step is to make a development version of my production site and disable modules one by one, possibly uninstalling one by one as well until it starts to work again. If you get to it before me, let me know what causes the error! (And I'll do the same)

I'm having the same issue. Whenever I use a date filter, I get PHP errors. I get

"Fatal error: Call to a member function use_count_query() on a non-object drupal"

when I try to use an exposed date filter.

I can't reproduce this in the latest code. I fixed a few bugs and maybe this got fixed at the same time. Please try again with the latest code (either a fresh -dev checkout from cvs or wait for tomorrow's -dev tarball).

Thanks for the update cerup, it sounds like I have a similar problem and finding the conflicting module will fix it.

I have the same errors when a calendar block is displayed.
Cerup, Beifler could you please name the conflicting modules.
I have 200 modules enabled, it will take ages for me to discover the culprit.
Thanks

In my case it was something related to the table wizard module. I disabled the node table to be managed with tw and the error went away.

I think this is related to Date module.I faced this problem after upgrading from Drupal 6.19 to 6.2

Any way I found a solution to solve this problem.
Use the following code in views\includes\handlers.inc on line 17

if(is_array($definition['handler'])){
$definition['handler']='views_plugin_display_default';
}
I am not sure this is the right way.But if you want to eliminate the error then you can use this

I started seeing something exactly like this. The reason for me is that I'm trying to override the views_file_size_handler. But instead of overriding it, Views merges my class with it's own into an array. I'm creating an issue in the Views issue queue to address this type of situation.

Update:

I just noticed what it is. Looks like there might not be a way to do what I want which is to override an already set field.

I'm passing :

  // filesize
  $data['files']['filesize'] = array(
    'field' => array(
      'handler' => 'rb_handler_field_file_size',
      'click sortable' => TRUE,
     ),
    'sort' => array(
      'handler' => 'views_handler_sort',
    ),
    'filter' => array(
      'handler' => 'views_handler_filter_numeric',
    ),
  );

in my module, which because it's already defined in the Views module, I guess merges Views definition with my own. The only solution I see is to define my own field. Not as pretty as what I wanted to do but at least I wont get the error.

Update - 2:

Yeah, so what happened was that I introduced a bug by returning the above data def from a hook_views_data(), instead of altering the bits I needed using hook_views_data_alter(&$data):

#801694-4: warning: class_exists() expects parameter 1 to be string error - How to override a views handler

Hi - wanted to comment in support of seeing this in the TW module. I too get:
warning: class_exists() expects parameter 1 to be string, array given in E:\wamp\www\sites\all\modules\views\includes\handlers.inc on line 17.
warning: class_exists() expects parameter 1 to be string, array given in E:\wamp\www\sites\all\modules\views\includes\handlers.inc on line 37.
warning: Illegal offset type in isset or empty in E:\wamp\www\sites\all\modules\views\includes\handlers.inc on line 120.
warning: class_exists() expects parameter 1 to be string, array given in E:\wamp\www\sites\all\modules\views\includes\handlers.inc on line 81.

The configuration that was working for a year and a half was a 6.15 core with 15 add-on modules and some very minor customizations. The client asked me to 'make it green' ie; get all the modules uptodate for security purposes and I happily duped it to a development site and moved it to 6.20 - then the errors were there. I redid the work, step by step (6.20 upgrade with all other modules upgraded including date, views and schema modules) I isolated that if I left the TW module non-updated I got no errors. Only after applying the (table wizard) TW module update to this version did I get the problem. I also tried with the last non-devoplement version of the TW module, and the same problem occurs with it as well.
As TW was noted as being deprecated in favor of the Data module I'm at a quandry now about how to move forward.

And I now apologize, this post is in a closed bug marked as fixed. hmmm.

More info I'd like to share. Went back to my working 6.15 environ, and updated TW only. It failed saying Date module blah blah. Did the Date module first - no errors. then did the TW module. It failed with the above error. I'm convinced that what I've read about it being Date module related holds true since many if not all the referenced failures seem to have date functions involved. Google shows many sites with this error recently (searched "includes/handlers.inc on line 17"). I can't find true fix, code or patch that solves this and I want to since its a pre-step for 7.0 upgrade. Can anyone direct me towards a solve?

Disabling Table Wizard fixed it for me too.