If you folllow the instructions and download the lastest version of jQuery Masonry lib 'Make grid resizable' doesn't work.
Also, the patch for Views Infinite Scroll seems to have problems too.

I think it'd be advisable to inform users which version of jQuery Masonry is actually supported.

Comments

axbacon’s picture

axbacon commented

I had this problem too. This version lacks identifying info, but worked for me. http://code.google.com/p/nurulimaminfo/downloads/detail?name=jquery.maso...

Stathes’s picture

Stathes commented

I too have ran into trouble, I am currently using the version ending it 2.1.7 instead of .8.

I did notice however the resizable grid will still work once you turn jquery update on, however their is some errors that come which do not seem to affect anything.

Also I noticed the glitches with weird gaps appearing randomly which I am pretty sure is a masonry thing, perhaps this is the cause. I will do further investigation.

leschekfm’s picture

leschekfm commented

I can also confirm this issue. You get a javascript error with version 2.1.8 which isn't there with 2.1.7
Some advice on compatibility or a link to a working version of the file on the module page would be great.

scottrouse’s picture

scottrouse commented

I can confirm this behavior, as well. Using jQuery 1.5, 1.7 or 1.8 (with the help of the jQuery Update module) resolves the resizing issue (but introduces issues with other modules...such as Colorbox).

ericbobson’s picture

ericbobson commented

Just wanted to say thanks for posting this link - this problem was driving me round the bend until I tried the version of the plugin you linked to here (in comment #1). Many thanks!

pxlr’s picture

pxlr commented

I recommend using jQuery Multi instead of jQuery Update as it allows you to only load the newer jQuery for masonry while leaving core, Colorbox, etc on the lower version of jQuery. Worked great for me.

Anonymous’s picture

Anonymous (not verified) commented
Component: Code » Documentation
Category: bug » task
Status: Active » Fixed

Thanks for this.

I can't seem to find any information re. which version of jQuery each version of Masonry requires, all I can see is that Masonry in general requires jQuery v1.6 or greater (see here). As Drupal 7 uses jQuery v1.4.4, this is an issue.

Instead of recommending users use an older version of Masonry (which still doesn't guarantee compatibility with jQuery v1.4.4, at least without some official documentation), I'd prefer recommending users upgrade their version of jQuery (via jQuery Update or jQuery Multi) and stick with the latest version of Masonry.

I'll add a notice to the project page to that effect.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

jamesfk’s picture

jamesfk commented
Status: Closed (fixed) » Active

Hi there, are there any instructions on getting jquery multi correctly configured? I installed it with the latest jquery - and even though in the source I can see it active, masonry isn't using this library but the default and therefore errors.

Many thanks in advance,
James

PS Using jquery update for now - but as this breaks other things (including views) it would be great to get multi working - especially as this is the recommended option on the project page at the moment.

Anonymous’s picture

Anonymous (not verified) commented
Status: Active » Closed (fixed)

Did you try: http://drupalcode.org/project/jqmulti.git/blob/refs/heads/7.x-1.x:/READM...

If you still need help, please post to the jQuery Multi issue queue.

blackxylene’s picture

blackxylene commented

#10 worked for me (after searching for 2 days).

Here are the specifics:

In the README file linked in #10 above, item 4.D) reads:
"To use the provided jQuery alias in your custom scripts, reference
the alias in your script closure. The alias name is generated using
the jQuery version number, with the periods removed.

For instance, if you're loading jQuery-1.7.1, the alias will be jq171, and you can
use it in your scripts by wrapping your code as follows:

(function($){
// your code here, using jQuery 1.7.1
})(jq171)"

In my case I was using jquery-1.10.2.min.js (which I had previously manually placed in the /sites/all/libraries/jquery/ folder), so in masonry.js I substituted (jQuery); with (jq1102); at the end of the file.

Then masonry.js stopped referencing the incorrect version of jQuery set by jQuery Update, and now properly referenced the one used by jQuery Multi. That also allowed masonry to insert classes where needed, which it was previously not doing.

Hope this helps someone.