Just installed 7.x-3.x-dev. Went to "calendar/month" and got

Fatal error: Call to a member function use_pager() on a non-object in C:\wamp\www\drupal7\sites\all\modules\views\includes\view.inc on line 510


Status:Active» Fixed

If you bump up from 7.2 to 7.3 all the handlers have changed and you will have to clear the caches. After that you will find that you need to re-create any custom views you created because the handlers are different, so you will get a lot of messages about missing handlers.

This branch is still under development, but I'm happy to have as many people trying it out as possible because I want to switch to it soon. The code is much simpler and will be easier to maintain, which should mean it will work more reliably.

The downside of the new branch is that any existing views will need to be fixed to use the new handlers. In most cases it will be easier to just delete old views and start over.

So you won't want to jump back and forth between 7.2 and 7.3.

Status:Fixed» Active

This was a brand new install, so core should have cleared the cache, but I did it manually any way. The view I was trying is the standard one you provide. I deleted it and installed 7.2 - well, you see my other issues...

If you would prefer, I will delete 7.2 and re-install 7.3; the site is nowhere near ready yet.

Status:Active» Postponed (maintainer needs more info)

You will save yourself an update later if you just start out on 7.3. It is not ready for production, but if you're not either you might as well use it.

If you are using the tarball, there are lots of issues fixed today that are not in the tarball. You may want to wait and try again tomorrow with all the latest fixes in it.

Status:Postponed (maintainer needs more info)» Closed (cannot reproduce)

Okay, I disabled and uninstalled 7.2, with liberal cache flushing. Then I installed 7.3, with more cache flushing). I will update it again tomorrow.

This problem is gone now.

Status:Closed (cannot reproduce)» Active

Same problem here with both a clean install, and on an install that had Calendar 7.x-2.x-dev previously (which was uninstalled in favor of moving to 7.x-3.x-dev).

Calendar 7.x-3.x-dev (2011-Jul-18)
Date 7.x-2.0-alpha3
Views 7.x-3.0-rc1
Ctools 7.x-1.0-beta1

Could something in the updates between the 15th and the 18th be a variable in this issue?

Trying to edit the code calendar view (bundled with the module) leads to the error, and a white screen. From my php error log:
PHP Fatal error: Call to a member function use_pager() on a non-object in /[...]/htdocs/sites/all/modules/views/includes/view.inc on line 510

I've tried liberal cache clearing on both installs (via devel and the core Drupal performance options) but this same error results. Is there any other steps I should try, or any other info I can pass on? Once again, I'm seeing this same problem on a Drupal install that previously had Calendar 7.x-2.x-dev installed (and then fully uninstalled) and a clean Drupal install.

Ok, I spoke too soon. Sorry Karen, I forgot to heed your note on the project page about using the latest dev versions of all dependencies. The following module combinations have worked for me (no PHP Fatal error) upon further testing:

Calendar 7.x-3.x-dev (2011-Jul-18)
Date 7.x-2.x-dev (2011-Jul-18)
Views 7.x-3.x-dev (2011-Jul-18)
Ctools 7.x-1.x-dev (2011-Jul-18)


Calendar 7.x-3.x-dev (2011-Jul-18)
Date 7.x-2.x-dev (2011-Jul-18)
Views 7.x-3.0-rc1
Ctools 7.x-1.0-beta1

So it looks like the Date module version was the one that needed changing in my case.

Sorry that I missed this the first time, but I'm hoping that someone else encountering this problem may get some assistance by reading this.


Status:Active» Closed (works as designed)

Edit: Changing status (hopefully to the correct setting).

Priority:Normal» Major
Status:Closed (works as designed)» Needs review

Status:Needs review» Needs work

I haven't even used Calendar yet, nor I have enabled it in a view. It is inactive in the blocks as well.

I guess I will just have to uninstall it again.

And - yes, I do have 7.3; and - no, I haven't created any custom views of this module.

Priority:Major» Normal
Status:Needs work» Postponed (maintainer needs more info)

@connelic, I have no idea what you're saying by re-opening this issue, and 'needs review' means there is a patch to review. If you went from 7.2 to 7.3 you have to flush the caches several times even if you never used the views. If you're saying you have a bug with the latest dev version of all these modules, *after* flushing the caches and confirming that the default view doesn't need to be reverted, then you need to provide clear steps to reproduce your problem.

You also need to clarify if you are using the -dev version of all the related modules, Date, Calendar, Views and CTools. Saying you're using '7.3' does not tell me if you're using the dev version. There is also a 7.3 alpha version.

Priority:Normal» Major
Status:Postponed (maintainer needs more info)» Needs work

Also having problems with this module when using Calendar. Everything is up to date. Using Drupal 7.7, which might present a compatibility problem.

Fatal error: Call to a member function use_pager() on a non-object in /home/.../modules/views/includes/view.inc on line 510

Drupal Version: 7.7
Calendar: 7.x-3.0-alpha1
Views: 7.x-3.0-rc1
Date: 7.x-2.0-alpha3
Ctools: 7.x-1.0-rc1

Personally, I use the -dev version of all the above and it works fine for me.

@ausj02, you are not using the dev version of Date or Calendar. You need to use the *dev* version of the code until I can cut a new release (which I can't do until a couple more critical bugs get fixed, and I can't confirm that the bugs are fixed when people who are not using the latest code keep reopening these bug reports to say the 'latest' code is still broken).

Well, I think you're doing a marvelous job, Karen. Everything I've run into has been fixed rather quickly.

Agreed with Nancy, I've had great results with Calendar on D7 ever since I started using the dev version of it and Date.


The latest 7.3 codes on git stall have this problem.

As you can see, I originally had this problem with v2. I disabled the module and cleared cache. Then I deleted all of the module code and downloaded version 3 (-dev) and enabled it. Then I cleared the cache again. After that the problem went away.

I have never used the calendar before and I get this error when trying to clone views with 7.x-3.0-alpha1 and 7.x-3.x-dev 2011-Aug-07.

Fatal error: Call to a member function use_pager() on a non-object in /www/htdocs/sites/all/modules/contrib/views/includes/view.inc on line 510

I have upgraded to the dev versions of date and calendar on a NEW install and I get:
Fatal error: Call to a member function use_pager() on a non-object in /www/htdocs/sites/all/modules/contrib/views/includes/view.inc on line 510 - actually after clearing caches, I got past this error....ED

Status:Needs work» Fixed

I'm going to call this fixed. It has turned into a thread where people report there is a problem using older versions and finally realize it works if you use the latest code and clear the caches.

Status:Fixed» Active

I still have this problem
It was a brand new install with :
Calendar : 7.x-3.0-alpha1 tar.gz (52.16 KB) | zip (68.4 KB) 2011-Aug-01 Notes
Date: 7.x-2.0-alpha3 tar.gz (165.58 KB) | zip (199.81 KB) 2011-Apr-26 Notes
views: 7.x-3.0-rc1 tar.gz (1.41 MB) | zip (1.6 MB) 2011-Jun-17 Notes
Chaos: 7.x-1.0-rc1 tar.gz (372.15 KB) | zip (562.7 KB) 2011-Jul-28 Notes

And I got this error:
"Fatal error: Call to a member function use_pager() on a non-object in /home/andreasa/mysite/sites/all/modules/views/includes/view.inc on line 510"

Then I moved to the latest greatest dev version of all of them , and same problem.

I did clear my cache

Clear it again. Clear the Views cache. Then clear the Drupal cache again.

Confirmed, the first set of module versions mentioned ad comment #6 worked for me too. I already had content and views listing nodes with date fields. I did not have to do anything extra to make it work. Updating date module to the dev version fixed the bug.

Appreciate it Karen! Thanks for all your work on the module.


Status:Active» Fixed

I will try one more time to mark this fixed.

Status:Fixed» Needs work

Note: all of my modules are up to date as of today, yet I started seeing this today. I've cleared cache, run cron, redid my calendar views. I'm definitely open to suggestions.

Disable the module (do NOT uninstall). Delete all the code, clear the cache. Re-download the code; clear the cache. Re-enable the module; clear the cache; clear Views cache. Try again.

If it's okay now, mark this issue fixed.

#6 confirmed
use the latest date module solve it.

i use the latest date module and I still get the error...

Use the latest Views, Ctools, Date, and Calendar together - all four have to be in synch. Then see #30.

Please note: As of this writing, you must be using the latest DEVELOPMENT version of Date (7.x-2.x-dev), not the latest release version (7.x-2.0-alpha3). At least, that's the only way I could get rid of this error.

Status:Needs work» Closed (won't fix)

I just stopped using the module altogether.

Status:Closed (won't fix)» Active

@connelc - you're not the only one with the problem.

It works just fine for me - see #30.

@Starminder, what version of everything are you using, Date, Calendar, Views, and CTools? "all of my modules are up to date as of today" does not tell me what version of everything you are using, which is the key question.

at the time I posted all were current dev versions. I have a multisite install and was able to fix this on the primary site, so for now I'm OK. When I try to go to one of the other sites I'm getting this no matter what i do, so it seems I'll need to delete the module which may play havoc on the site that's working, so for now, I'm leaving well enough alone.

Status:Active» Postponed (maintainer needs more info)

Then the important question is first, did you clear the caches repeatedly on the sites that are not working? And if that did not work, what is different on the sites that are not working from the one that is?

And, remember that the Views cache clearing is a separate function...

To me this issue may be due to date module, after updating to alpha4 (released yesterday), it is resolved.

Status:Postponed (maintainer needs more info)» Closed (cannot reproduce)

I was never able to replicate this issue and there have been lots of changes since it was reported. Check the very latest dev versions of both Date and Calendar, clear the caches, re-edit the view and re-save it. If there is still a problem in the latest code you can reopen.

Thanks Karen,

Its working smooth for me!

I have tried a bunch of different combinations of version, what are the exact versions I need to get rid of the use_pager() error?

I just came across this.
I had a view plugin for the page display
I remove the plugin
the view showed "display all" but when I clicked on the display widget, nothing was selected.
selecting one of the remaining option made the error go away