I am using Views 3.

When there are no cooments, there is no problem. But when there are comments, this error is shown. So I think this relates to nodecomments.

Comment structure: Content Type [main] -> Content Type 2 [review of ct 1] -> Content type 3 [reply to content type 2]

Comments

alimosavi’s picture

same problem ..

crea’s picture

Status: Active » Closed (won't fix)

Why do you think Node Comments should work with Views 3 ? It was never tested or ported.

crea’s picture

Title: Fatal error: Call to a member function init_pager() on a non-object in .....modules/views/includes/view.inc » Views 3 compatibility.
Version: 6.x-2.0-beta3 » 6.x-2.x-dev
Category: bug » feature
Priority: Critical » Normal
Status: Closed (won't fix) » Active

Opening as feature request for future uses.

jthomasbailey’s picture

Subscribing, I'm already running into modules that require Views 3 that I want to use, like Views Infinite Scroll.

aidanlis’s picture

Yep, it's time to start dealing with Views 3.x. There's roughly 5,000 sites using 3.x-alpha3 already, and that number will grow very quickly when it moves into beta (imminent).

Do you want to create a new major branch for Views 3.x? If you create the branch I'll start writing patches ...

aidanlis’s picture

Title: Views 3 compatibility. » [Views 3.x] Fatal error: Call to a member function init_pager() on a non-object

Adjusting the title, assigning a [Views 3.x] prefix for all Views 3.x related bugs.

crea’s picture

It would be best to find a way to be compatible both with Views 2 and Views 3. Some projects manage to do that. Can you please investigate this, aidanlis ? I don't like the idea to open a branch just for Views compatibility.

aidanlis’s picture

Hi crea, the other option is this:

if (views_api_version() == 3) {
  // get_plugin('cache');
} else {
  // get_plugin_cache();
}

You'll have to double check the views_api_version().

Let me know if I can help any further :)

crea’s picture

Ok good. Now let's wait for someone to create a patch. I don't use Views 3 yet ;)

imDhaval’s picture

hi! this is a great module & we knows views is also great .
so crea,why shouldn't you try to make this module compatible with Views 3.x..

please do something.............

gaele’s picture

Is this still a problem? Using
nodecomment 6.x-2.x-dev (2010-Jul-20)
views 6.x-3.x-dev (2010-Oct-14)
I cannot reproduce the error.

gaele’s picture

Status: Active » Fixed

Yes, this is a bug in views 3 alpha 3. Fixed in views 3 dev.

See also http://drupal.org/node/923132#comment-3495252

Status: Fixed » Closed (fixed)

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