Closed (fixed)
Project:
EVA: Entity Views Attachment
Version:
7.x-1.2
Component:
Miscellaneous
Priority:
Major
Category:
Bug report
Assigned:
Reporter:
Created:
25 Feb 2013 at 11:36 UTC
Updated:
19 Aug 2014 at 15:41 UTC
Jump to comment: Most recent
Comments
Comment #1
amir.modarresi commentedI found my problem's reason :)
my main page's pager did not apeare beacause of enabling pager in views that i created as EVA.
excuse me for my very bad english
Comment #2
mkadin commentedThis isn't Eva's fault but I can help you out. Having multiple views pagers on the same page can cause conflicts. You can fix it by changing the 'pager id' in the views settings for the pagers. Each pager that appears on the same page must have a unique Id.
Comment #3
amir.modarresi commentedthanks
Comment #5
lovecookie commentedOn our default Search Results page (/search/node/, EVA was wiping out the $pager variable, resulting in missing page navigation at the bottom of the page. We were able to fix by making the following adjustment to the EVA module:
In the eva_get_views function, on or around line 115, after 'views_include('cache');', add:
$path = current_path();
$patharray = explode("/", $path);
if ($patharray[0] == 'search') {
return false;
}
This kills the function if the user is on the search page. Our page navigation has been magically restored!
I hope this helps someone... I spent 2 days (and an hour of my coworker's time) trying to resolve this issue.
Comment #6
dariogcode commentedHaving same issue. Removing pager from EVA view fixed my problem, in my case I only need a fixed number of elements (1), but probably other need display a pager as part of the content.
I didn't had time to review, but someone can try to put a different pager identifier in main view to see if that fixed the conflict.