Steps to reproduce:
- Install/enable Entity Pager module version 1.0.0-beta2
- Enable Entity Pager example View at Structure > Views
- Go to Structure > Block layout; place Entity pager example block in a region (Content, Sidebar, etc). Apply Content type visibility (aka Only show the block on Content pages). Save blocks layout.
- Visit Content.
- < prev link is plain text, not linked
- next > link points to a node, click it.
- When you get to the next node, it's the same pager. No link in prev, next links to same node. Clicking it will just reload that node again.
I had a working Entity pager that was rather complex and took me days to get working. I updated via COmposer, yesterday, and today realized the pager no longer worked. I spent hours, today, thinking I had done something to it and forgot, but eventually I gave up and re-tested the Example pager and realized that it is no longer working, either.
Has anyone else experienced this with "beta2" which came out, yesterday?
Thanks.
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | 3043003-issue-with-class.diff | 389 bytes | ddiestra |
Comments
Comment #2
sproets commentedYep, here the same issues :(
Comment #3
zebda commented+1, I replaced beta 2 with beta 1 and everything is working again.
Comment #4
ddiestra commentedI found the issue, this line is missing use Drupal\Core\Entity\ContentEntityInterface. Added a patch with the fix.
Comment #5
ccshannon commentedThanks, @ddiestra! This fixes the issue for me.
Comment #6
zebda commentedThanks, that did the trick.
Comment #7
zanvidmar commentedI can also confirm that #4 fixed the issue. Thank you.
Comment #8
afschThe fix in #4 should be applied as soon as possible. Thanks.
Comment #9
marassa commentedAfter update to beta2 my pager's prev link was pointing to the last record and the next link to the first record, and the log was full of
Notice: Undefined variable: entity in Drupal\entity_pager\EntityPager->getEntity() (line 108 of /home/ibeoomaj/public_html/modules/entity_pager/src/EntityPager.php)errors. The patch #4 fixed that, thanks a ton!
Comment #10
marassa commentedComment #11
stevieb commentedPatch in #4 works
Comment #12
paperscenery commentedThanks @ccshannon for posting this question—I thought I was losing my mind too. Patch in #4 fixed it. Thank you @ddiestra!
Comment #13
replicaobscuraThanks for catching this issue, and posting the patch! Sorry for introducing this in the last update, I'll get this patch committed now.
Comment #14
replicaobscuraComment #16
replicaobscuraI'm making a bug fix release for this issue now as well.
Comment #17
replicaobscura