Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
After updating to Masonry API 3.0-beta1, I can no longer edit the Settings field or the Sort criteria for my Masonry view. Clicking "settings" does nothing. I can edit settings and sort criteria fields with no issues on all other views on the same site.
Masonry API 7.x-3.0-beta1
Drupal 7.38
jQuery Masonry 3.3.1
jQuery 1.8
Views 7.x-3.11
Comments
Comment #1
mfarineau CreditAttribution: mfarineau as a volunteer commentedComment #2
Dom. CreditAttribution: Dom. commentedHi !
Could you let me know from which Masonry version you did the upgrade ?
Comment #3
mfarineau CreditAttribution: mfarineau as a volunteer commentedHi Dom,
I had been using Masonry API version 7.x-2, which loads jQuery Masonry 2.1.08
Comment #4
Dom. CreditAttribution: Dom. commentedI will try reproducing. In the meanwhile :
- Can you confirmed you follow upgrade process ?
- Did you upgraded your libraries to the new necessary ones ? (see module description)
- Did you "clean all caches" at /admin/config/development/performance ?
- Are the new library versions recognized at /admin/reports/status ?
Dom.
Comment #5
mfarineau CreditAttribution: mfarineau as a volunteer commentedThe upgrade process I followed was to
-download the updated module
-manually put it in the correct directory
-download updated masonry library
-manually put it in the correct directory
-download new imagesLoaded library and put it in place
run update.php
clear all caches
all libraries appear to be loading correctly in the status report (see my separate issue about the imagesLoaded library https://www.drupal.org/node/2532204)
Comment #6
Dom. CreditAttribution: Dom. commentedI answered the other issue. You may have wrong masonry_views module. If your module is still in the masonry folder as it was in 7.x-1.x, then it's wrong, you need to install the new separate ones.
Comment #7
mfarineau CreditAttribution: mfarineau as a volunteer commentedSo I upgraded to Masonry Views 7.x-3.0-beta1 and am still seeing the same behavior where I can't click on settings when editing my view. Not the end of the world as I can get around it by copying the link and pasting into my browser window, but it is strange. If you can't duplicate it and no one else is having this issue, it is entirely possible something is wacky on my end.
Comment #8
Dom. CreditAttribution: Dom. commentedI can't replicate indeed... Do you have also remove the masonry_views folder that originally was in masonry module ?
Comment #9
andersju CreditAttribution: andersju commentedI had the exact same problem with 7.x-3.0-beta1. I looked in the console and noticed that an error occurred if I loaded a view edit page that had Masonry as its format:
TypeError: a.Deferred is not a constructor
I then realized that while jQuery 1.10 was used for the main site, the admin theme still used the Drupal default (1.4). Going to
/admin/config/development/jquery_update
and changing to 1.10 for "Seven (admin theme)" solved the issue.Comment #10
Dom. CreditAttribution: Dom. commented#9 solves the issue.
Thanks @andersju
Comment #12
squarecandy CreditAttribution: squarecandy commentedUsing the non-default jQuery on the admin end can occasionally cause other issues in my experience.
As another option you can go to /admin/structure/views/settings and uncheck Automatically update preview on changes.
Now views admin won't try to run the Masonry jQuery by default every time the views admin loads or anything changes.