Closed (fixed)
Project:
Drupal core
Version:
7.x-dev
Component:
field system
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
4 Sep 2010 at 14:31 UTC
Updated:
3 Jan 2014 at 02:04 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
damien tournoud commentedThis should do it.
Comment #2
damien tournoud commentedOne hunk of the previous patch relied on #898520: Clean-up the upgrade path: comment, and chx noted that field.crud.inc now needs to load the install files too.
Comment #3
chx commentedThis is an important and trivial stepping stone.
Comment #4
dries commentedCommitted to CVS HEAD. One step closer to making the upgrade path work! :)
Comment #5
Crell commentedChanging where a hook must live is an API change, and should be announced as one.
Comment #6
rfayTrivial testing says to me that this does not affect the normal module workflow. I'm able to enable, uninstall, etc. a module with this in the wrong place.
So is the effect that if your module is in included in an install profile, it would fail on install of a new system?
One of the biggest problems I notice is that the various CCK modules have this in the .module.
Comment #7
damien tournoud commentedThis is more a best practice kind of thing. hook_field_schema() should, like hook_schema() live in
.install. It might work if place somewhere else, but we cannot make any guarantee.