By tvst on

I couldn't find an appropriate forum where I could ask this, hopefully it makes sense to post the question here:

I'm planning on upgrading from 4.7.0 to 4.7.2. Apparently there was a DB modification between 4.7.0 and 4.7.1. Were there any changes that could (theoretically) compromise the operation of any of the 4.7.0 modules?

I say "theoretically" because the operation of each module depends on its particular functionality (and how it was coded, etc). So, what I'm looking for is just a broad answer, such as "Modules that use 'system.module' may break" or something like that.

Thanks!

⋅ Categories: Drupal 4.7.x

Comments

Rosamunda’s picture

Rosamunda commented

I´ts a VERY interesting question! Thanks for asking!

Rosamunda
Buenos Aires | Argentina
www.ligadelconsorcista.org

robertdouglass’s picture

robertdouglass commented

With very few (and hopefully well documented) exceptions, all 4.7.* modules should work with any 4.7.* version of Drupal.

- Robert Douglass

-----
My Drupal book: Building Online Communities with Drupal, phpBB and WordPress

suydam’s picture

suydam commented

Has anyone confirmed this yet?

I have three live, 4.7.0 sites and in all cases, I don't have a real test environment to try 4.7.2 out prior to just "going live" at the drop of a hat.

I need to push 4.7.2 into production, but if it crashes things, I'm hosed.

MrEricSir’s picture

MrEricSir commented

Tell us which ones you're using, there's no way someone's going to confirm every single module.

sepeck’s picture

sepeck commented

on how the versioning goes for Drupal versions, core and contrib. 4.7.0 contrib modules should work with all 4.7.x Drupal core releases.

Any issue's would be if some module used a method that was later determined to be a security issue and changed. I don't know of any issue's at this point but based on the advisory text upload module was changed a bit so any contrib modules you are using related to uploading files would be something to test for just to be sure.

I would strongly suggest a test site for any of your production sites. I can't say that often enough. I do one for all the site's I maintain and so far it has been well worth the time invested in successful uptime.

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide

tvst’s picture

tvst commented

I'm using:

  • Graphstat
  • Taxonomy Access
  • Taxonomy DHTML
  • TinyMCE
  • Subscription
  • URL Filter

If I end up upgrading, I'll follow up on which of these is working. I suggest everyone do the same.

sepeck’s picture

sepeck commented

These releases are Security related. You have spent to much time on your site to NOT upgrade. Please upgrade soon, so you do not end up back asking how to deal with a hacked site.

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide

tvst’s picture

tvst commented

ok, not "if" but "when i end up upgrading" :)

MrEricSir’s picture

MrEricSir commented

Of those, I can tell you TinyMCE works fine.

kyouens’s picture

kyouens commented

taxomomy access works fine