Closed (duplicate)
Project:
Masonry Views
Version:
8.x-1.x-dev
Component:
Code
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
21 Oct 2016 at 01:48 UTC
Updated:
28 Feb 2018 at 10:25 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
dom. commentedPlease, tell me more
Comment #3
tancI'm also seeing this issue using a custom theme. In the views admin the masonry javascript targets the rows correctly but when viewing on the front end it displays as a single column.
I think its due to the custom theme using stable as its parent whereas the admin theme is using classy as its parent. Masonry appears to expect certain class names to target the javascript.
For example:

So I think the solution for a themer is to add the desired classes to the correct template. I will try this next and report back.
Comment #4
tancI can confirm this is the issue. To resolve I copied
views-view.html.twigfromcore/themes/classy/templates/viewsto the templates directory in my custom theme.Ideally the module wouldn't rely on specific classes provided by classy theme. Maybe a preprocess hook to add specific classes which can then be relied upon might be a solution?
Comment #5
tancLooks like this is a dupe of #2716399: Not working on themes based on "stable"