CCK field modules maintainers - D6 upgrade path
To all CCK field modules maintainers : please read http://drupal.org/node/304813 (also posted on g.d.o/cck) yched
On Saturday 06 September 2008, Yves Chedemois wrote:
To all CCK field modules maintainers : please read http://drupal.org/node/304813
It would make a lot of sense to also have this in the handbook, at http://drupal.org/node/191796 Of course, with inter-dependent module stacks getting popular, the nifty solution would be a solution in Drupal core, like, say, mymodule.install: ... /** * Implementation of hook_update_dependencies(). * Not necessary to implement if this module's update functions do not * depend on other module's updates. */ function mymodule_update_dependencies() { return array( 6000 => array( 'content' => 6000, // needs at least CCK 6.x 'filefield' => 6301, // and filefield-6.x-3.1 (made up the update no.) ), ); } ... Those upgrade dependencies are (still?) so much of an edge case that a lot of module developers are apt to ignore them, while with a centralized framework it would be easy to implement, with updates being less error prone. Plus instead of aborting the whole process like in the above CCK note, those updates could run correctly in one go. Seems easy enough, but I don't exactly feel strong enough about that idea to implement it :P
remove me plz Yosry SHADY
From: jpetso@gmx.at> To: development@drupal.org> Date: Sun, 7 Sep 2008 18:07:45 +0200> Subject: Re: [development] CCK field modules maintainers - D6 upgrade path> > On Saturday 06 September 2008, Yves Chedemois wrote:> > To all CCK field modules maintainers :> > please read http://drupal.org/node/304813> > It would make a lot of sense to also have this in the handbook, at > http://drupal.org/node/191796> > Of course, with inter-dependent module stacks getting popular, the nifty > solution would be a solution in Drupal core, like, say,> > mymodule.install:> ...> /**> * Implementation of hook_update_dependencies().> * Not necessary to implement if this module's update functions do not> * depend on other module's updates.> */> function mymodule_update_dependencies() {> return array(> 6000 => array(> 'content' => 6000, // needs at least CCK 6.x> 'filefield' => 6301, // and filefield-6.x-3.1 (made up the update no.)> ),> );> }> ...> > Those upgrade dependencies are (still?) so much of an edge case that a lot of > module developers are apt to ignore them, while with a centralized framework > it would be easy to implement, with updates being less error prone. Plus > instead of aborting the whole process like in the above CCK note, those > updates could run correctly in one go.> > Seems easy enough, but I don't exactly feel strong enough about that idea to > implement it :P>
Invite your mail contacts to join your friends list with Windows Live Spaces. It's easy! http://spaces.live.com/spacesapi.aspx?wx_action=create&wx_url=/friends.aspx&...
On Sunday 07 September 2008, yousry shady wrote:
remove me plz Yosry SHADY
herez ur link: http://lists.drupal.org/listinfo/development You need to unsubscribe yourself, in the same place where you subscribed yourself. Makes sense, doesn't it? In other news (hi infrastructure team), shouldn't there be the standard footer appended to each mail that links to the mailman page?
Quoting Jakob Petsovits <jpetso@gmx.at>:
In other news (hi infrastructure team), shouldn't there be the standard footer appended to each mail that links to the mailman page?
My experience is this is just ignored anyway. Why clutter the list mail when you'll just have to respond again anyway? Earnie -- http://for-my-kids.com/ -- http://give-me-an-offer.com/
Jakob Petsovits a ecrit le 07/09/2008 18:07:
On Saturday 06 September 2008, Yves Chedemois wrote:
To all CCK field modules maintainers : please read http://drupal.org/node/304813
It would make a lot of sense to also have this in the handbook, at http://drupal.org/node/191796 True - done.
participants (4)
-
Earnie Boyd -
Jakob Petsovits -
yousry shady -
Yves Chedemois