Can't install because of newer version of multiforn (incompatible with version 7.x-1.0)

Hi,

I've my web stuck because of this as I've upgraded Multiform to the latest and it fails to complete the installation.
Could you please provide the patch here?

I'll try to search for the hardcoded string and change it to non beta.

Thanks,

Francesco

!!!This is just hacking!!!

I worked around the issue going to media_gallery.info and removing the "-beta2" from this line: dependencies[] = multiform (1.0-beta2).

thx FrancescoUK

- dependencies[] = multiform (1.0-beta2)
+ dependencies[] = multiform

It works :)

Thankyou Francesco

my website got stuck too, just did #3 manually and it is working again

Yep, probably a better and safer work around.

Worked a treat, Thank you

This is a simple change and is working as expected, so setting to needs review.

Excellent fix!

For those who might get confused with the + and - symbols, it simply means delete one line of code and add the other. At first I thought they were both lines of code that both needed to exist along with the + and - symbols.

Thanks again!
Joe

Definitely. This should have been done earlier.

Do you need a patch to fix this? Or it has already been committed?

It has not been committed in beta7. Dear maintainers - please commit it!

Yes please commit since it is a must to use this module now.

This is a temporary workaround without hacking the .info file:

/**
 * Implements hook_system_info_alter().
 */
function CUSTOM_MODULE_system_info_alter(&$info, $file, $type) {
  if ($type == 'module' && $file->name == 'media_gallery') {
    $key = array_search('multiform (1.0-beta2)', $info['dependencies']);
    if ($key !== FALSE) {
      $info['dependencies'][$key] = 'multiform';
    }
  }
}

Actually guys this has been done a while ago:
View the commit.
http://drupalcode.org/project/media_gallery.git/commit/a15b003

Looks like the latest changes were not included in the latest package.

@webadpro You are right. Multiform dependency is fixed in development snapshot. Unfortunately this commit is the only change since 5 months ago.

After applying fix I get this:

EntityFieldQueryException: Unknown field: media_gallery_expose_block in EntityFieldQuery->addFieldCondition() (line 767 of ../newdrupal/includes/entity.inc).

Setting this to fixed, as it has been committed to dev.

Is the dev version available? I only see beta7. I tried both changes...
dependencies[] = multiform (>=1.0-beta2)
dependencies[] = multiform
clearing cache both times, but the modules page still lists beta2 as requirement which is still incompatible so I can't enable it.

Should I even be using this module if I don't know how to do this? The directions seemed simple enough. I'd like try this module out and maybe use it on production site... which could tolerate bugs as long as it generally works. Any advice? Thanks!!!

believe you only need to change the one line in your media_gallery.info file, then it works a treat in any production site (though only once you have run the 'update script' in modules)... I gladly confess I am very grateful indeed to these 'sanity-saviour' folk in forums!
dependencies[] = multiform (>=1.0-beta2)

My sites are on a multi-site setup with media modules shared by all sites. Changing the dependency as described above and running update script allows some of the sites to enable Media Gallery. But one site is already using Media and Mediafront and this one cannot enable Media Gallery. I've tried disabling and re-enabling these (though mediafront couldn't be disabled because it's being used by a content field) and then running update again but it didn't help. Any ideas?

Changing the dependency to dependencies[] = multiform (>=1.0-beta2) definitely works in multisite - but having the module redundantly installed in a sites/specificsite.com/module folder will override the shared module (fellow newbies take note). And grateful for Simon Fraser's reminder about update script!

Please Create beta 8 simply to create a new release with this fix.

I realize that this topic is a bit old but this solution worked like a charm! Thanks.

@webadpro Too many changes has happened for us to release just now. We need to make sure that it works. You can help by getting your hands dirty with git and test out all the new bugfixes.

Can't you simply checkout the release version rather than the dev version, and apply the patch on it, and rollout a new beta?