When trying to edit calendar view there is unhandled exception resulting in blank screen in the browser and error message in the apache's log

[Thu Aug 11 09:28:17 2011] [error] [client 193.178.166.2] PHP Fatal error: Call to a member function use_pager() on a non-object in /var/www/drupal7/sites/all/modules/views/includes/view.inc on line 510, referer: http://whatta-whatta.com/admin/structure/views

CommentFileSizeAuthor
#7 after_update.pdf137.39 KBpdeclarens

Comments

dawehner’s picture

Status: Active » Postponed (maintainer needs more info)

Did you upgraded to calendar 3.x?

smoldovansky’s picture

Yes

equinox’s picture

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

I also receive this error message since applying the 3.0-rc1 update to Views. I also updated the 3.0 version of Calendar at the same time. This error prevents my entire site from loading, as I have a calendar displayed on the home page. The error disappears when I deactivate Calendar in the modules list, yet leave Views activated. Should I also mention this on the Calendar bug reports? Although the error response comes from your module, the problem vanishes when deactivating Calendar (and Date Views along with it.)

EmpireNM’s picture

subscribing

bokabu’s picture

Ah! Look at http://drupal.org/node/1220544
For me, it was either upgrading Date to 2.x-dev or flushing the caches.

pdeclarens’s picture

Assigned: Unassigned » pdeclarens

Hello,

I do not know if theese informations will helps, but I think problem is not in line 510..

Like many others I experienced the use_parser problem...
Reading the various answers, I upgraded to the latest versions dev of the invilved modules (ctools, calendar, date, views)

I curently use the 7.8 drupal version

In first place each time I wanted to activate views module, I had an "out of memory" message. I got round this problem with increasing the php memory_limit to 60M

During new installation, I had some messages "site ha temporary problems"... but at the end it was installed.

Then I got the calendar working for a few days... and suddenly the theme went back to the blue lagoon color...calendar disapears... and the header repeats in place of the footer...

I was unable to disable the views module.. I had to remove it completely

At this second the site turned back to normal...

Bizare: I work on 3 sites, one is local and works, the 2 others are hosted by 1and1, one had the problem, not the second one although I have exactly the same configuration, same modules etc.

I hope it can help!

pdeclarens’s picture

StatusFileSize
new137.39 KB

On my local I made the update recomanded...

as a result I have the use-parser error

details on attached file

agatlin’s picture

Ditto. I have latest D7.7 and the latest everything else and am getting the same error.

dawehner’s picture

Some of you seem to update to calendar 3.x

Version 7.x-3.x is a complete rewrite of the code. Note that it is a major change, the plugins and handlers are changed, so views created in 7.2 won't work in 7.3 and vice versa. The new code is 1/10th the size of the older code so it will be far easier to maintain and more likely to work reliably.

This is a quote from calendar project page.

pdeclarens’s picture

Hello,

I am aware of this. However in this case I used directly the calendar 3.x version and the views3 version I use is http://ftp.drupal.org/files/projects/views-7.x-3.x-dev.tar.gz (downloaded on august, 19th)

I can see the enormous amount of work for you to debug the latest views module, but because it is needed for several other modules it is critical if we want to go in production ...

I have only web-designer skills, but if this is helpful, I can try as many solutions that you could suggest and make you a full report of whatever happens...

As said in a previous post, the strange for me is that the module combination dos work on one of the sites I work on and not (www.ffconcept.eu/drupal-7.7) on the others...

I hope I can be helpful,
MFG

agatlin’s picture

I have tried the 7.3-dev and 7.3-alpha versions of Calendar. Neither appear to be working. Both give the error
Fatal error: Call to a member function use_pager() on a non-object in ... on line 510

Basically, any calendar-related view fails.

How would I update the views which are installed with calendar to the latest versions from 7.2-7.3 other than by upgrading? Should I completely remove the Calendar, delete the Calendar-related views, and reinstall the module? Is that necessary?

In the meantime, until this bug is fixed, does anyone have any idea of a workaround?

dawehner’s picture

Status: Postponed (maintainer needs more info) » Fixed

Remove the existing view and rebuild the view or reuse the existing one provided by calendar module.
As the page said, there is no upgrade path yet.

Update status as it seems to be clear.

larowlan’s picture

Updating to latest -dev versions of views (7.x-3.x-dev)/date (7.x-2.x-dev) and clearing caches got rid of this error for me. Note that I was editing the default views provided by calendar and had not installed the 7.x-2.x version of calendar (ie not an upgrade path issue).

v.zhakov’s picture

I have same issue. Subscribe.
I update Date to last version (7.x-2.0-alpha4 - 2011-Aug-23), but problem was saved for me.

Status: Fixed » Closed (fixed)

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

hrpo’s picture

Installed 7.x-3.x-dev. Still getting error: Fatal error: Call to a member function use_pager() on a non-object in /var/www/html/sites/all/modules/views/includes/view.inc on line 690

Subscribing

Pratiksha patil’s picture

Issue summary: View changes

Installed 7.x-3.x-dev. Still getting error: Fatal error: Call to a member function use_pager() on a non-object in /var/www/html/sites/all/modules/views/includes/view.inc on line 690 still site crash

okokokok’s picture

I just encountered the same problem. Views 7.x-3.11

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

I resolved it by disabling the custom taxonomy term view. Good enough for me but it's not a real solution.

bennos’s picture

Maybe this happens, because you have a module installed that acts on the pager.

Think in Views.3.11 there were a lot of changes in the pager proccessing. callback and structure changed. related functions need to be updated.

Check if you have a module installed that modifies the pager.

golubovicm’s picture

Confirming that bug Kasper Souren reported is still present. I have latest core and all the modules and tried to import a view from a bit older project.

golubovicm’s picture

Found out what caused this issue for me, Bennos you was right - on site where I was doing export I had installed "Views load more" module and on site where I was importing that view I didn't. I think that's a bug in view import process. I didn't get any error during the import and it succeeded as everything was ok.