I was struggling how exactly to upgrade a feature in my live site after I've created a new version on my dev site. Turned out to be a combination of CCK not listening very well (will install the patch found in http://drupal.org/node/508428) but also rather confusion terminology like "Update" and "Revert", that actually both don't perform as their names suggest.

* when creating a new version of a feature, I'm at my dev site & take action "update"
* when deploying this new version on my live site, I copy the module into the modules directory & go to the features page - and there I should take action "Revert"?
Well no, mentally I'm finishing my deployment, so some action named "deploy module" or "upgrade module to v1.2" would make a lot of sense. Not "revert", that's going back in time & has connotation "less functionality" or "I've made a mistake".

First I would inform the user about both the live version and the module found in modules dir.
How about really naming the actions what they mean, like:
* current Drupal version: is currently version x.x (as is now)
* current module version: the module installed has version x.x (might be higher, lower, at least we could see then)
* create new module version (instead of update, since you're not updating, you're creating then downloading a new module version)
* deploy version x.x - and here the module version should be higher than the deployed version in db

What do you think about it?

Greats,
Wim

Comments

pasqualle’s picture

pasqualle
Location 🇭🇺 Budapest
commented

Revert removes the custom changes.

As I know if you did not make any changes to the feature then you just upload the new version and clear the cache. So "deploy module" does not makes sense..

There is no live version and module version, after you clear the cache it is the same. If you made custom changes then you have a different version (without a version number)..

yhahn’s picture

yhahn commented
Status: Active » Fixed

As of this commit the language has been changed http://drupal.org/cvs?commit=270108:

- Update is now "Recreate"
- "Revert" remains "revert" but the logic for detecting component states is much cleaner now and hopefully will reduce the number of instances when "Revert" appears when in actuality the feature will update to the new code definitions.

Setting to fixed, but please reopen if there are any follow up adjustments/suggestions.

Status: Fixed » Closed (fixed)

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