My comment:
provided step-by-step instructions for setting up and applying a patch (supplied by @bangpound - thanks) to get media_gallery-7.x-1.x-dev (as of 2012-Oct-30) WORKING SUCCESSFULLY with media 2.x.

I am now attempting to get the recently created media_gallery-7.x-2.x-dev working with media-2.x. However my first attempt has been unsuccessful, as described in:

So what I want to know is: what significant differences are there between the current media_gallery-7x-2.x-dev and the working media_gallery-7.x-2.x-dev (as of 2012-Oct-30) with patch support_media_2.x-1244204-90.patch applied (from @bangpound here: and using my steps to set it up here: as already mentioned)

Sure, there are API differences - i.e. between the 1.x and 2.x versions but I'm interested in missing features that prevent media_gallery-7.x-2.x-dev from working.

What's different between mg 7.x-2.x-dev & media-2.x compatible *working* m.g. 7.x-*1.x*-dev (2012Oct30) + 1244204-90.patch?


Moloc’s picture

Currently there are no new features in the 2.x branch in media_gallery (except, that you can delete a file, if it is in use).
We just created the branch, to be compatible to media 2.x.

The only change, you might get in touch is, that the field has a new name. In media_gallery 7.x-1.x the images are stored in the field media_gallery_media. In media_gallery 7.x-2.x the images are stored in media_gallery_file. (The reason for this is, that media 7.x-1.x users can (in a future version) upgrade to the 2.x branch.)

But this should not have any effect on your new issue. I can install the current dev version of media_gallery 7.x-2.x without problems.

Moloc’s picture

Issue summary: View changes
Status: Active » Fixed

media_gallery 2.x is needed for media 2.x, as there are a lot of interface changes in the media / file_entity module.

Status: Fixed » Closed (fixed)

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