Closed (duplicate)
Project:
Masonry API
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
4 Feb 2013 at 11:23 UTC
Updated:
3 Nov 2014 at 14:54 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
trigdog commentedThis is what I did to get this to work. I used the masonry destroy method in the masonry api module masonry.js file if the context of the request was not equal to the whole html document. So I changed the lines:
to:
Maybe this will help someone else come up with a better solution but it works for now. Tried using the reloadItems method but couldn't get it to work.
Comment #2
johankasperi commentedHi trigdog! Thanks for your solution, it solved my problem! But I changed to "reload" instead of "destroy", that will prevent jumping up to the top of the page.
Comment #3
bsarchive commentedThank you!
Comment #4
LuxianThis is my solution based on #2 (reload instead of destroy):
masonry.js (from masonry module):
Comment #5
aaronbaumanThis is an issue with Masonry Views module, not Views Load More.
Load More pager is doing the right thing by calling attachBehaviors after its done executing.
Masonry Views needs to re-attach itself.
Comment #6
aaronbaumanAnd actually this is a bug with Masonry API, and a duplicate of this issue:
#1808018: Make work with Views Infinite Scroll
Comment #7
aaronbaumanComment #8
sebastiendan commentedThis a patch with #4 solution, since it's the only solution that worked for me.
Comment #9
sebastiendan commentedWorks with masonry 2.0.
Comment #10
davidneedhamThis patch works for me if leave this alone. What's the reason for changing this to jq17?