Comments on: Trying out Drupal 5 http://www.darcynorman.net/2006/10/30/trying-out-drupal-5/ apparently much happier in person Sat, 21 Nov 2009 05:03:04 -0700 http://wordpress.org/?v=2.8.6 hourly 1 By: Bill Fitzgerald http://www.darcynorman.net/2006/10/30/trying-out-drupal-5/#comment-82434 Bill Fitzgerald Wed, 31 Dec 1969 17:00:00 +0000 #comment-82434 I was just going to comment on the project module work, but then I saw that merlin had beaten me to it -- FWIW, some of the very cool features of the new 5.0 version (like the node access arbitrator) have been coded by merlin -- Also, D'arcy, have you seen the ACL module, or the nodeaccess modules? -- both offer the beginning of user-determined access to nodes. RE Dave's question on cvs -- overwrite the codebase, and run update.php, and you should be good to go. Or, if you want to get fully geeked out, set up a cvs repo, run your code from there, and upgrade periodically by syncing your codebase against the Drupal cvs repo. Cheers, Bill I was just going to comment on the project module work, but then I saw that merlin had beaten me to it —

FWIW, some of the very cool features of the new 5.0 version (like the node access arbitrator) have been coded by merlin —

Also, D’arcy, have you seen the ACL module, or the nodeaccess modules? — both offer the beginning of user-determined access to nodes.

RE Dave’s question on cvs — overwrite the codebase, and run update.php, and you should be good to go. Or, if you want to get fully geeked out, set up a cvs repo, run your code from there, and upgrade periodically by syncing your codebase against the Drupal cvs repo.

Cheers,

Bill

]]> By: merlinofchaos http://www.darcynorman.net/2006/10/30/trying-out-drupal-5/#comment-82480 merlinofchaos Wed, 31 Dec 1969 17:00:00 +0000 #comment-82480 <i>That's one area I'd really like to see get some loving. Tagging a module as "4.7" and then making changes to it that break things depending on exactly which version of the 4.7 module you're running (or have run). Very confusing and frustrating.</i> This area is, in fact, getting a great deal of attention. Derek Wright is basically done with the coding and is doing testing and making sure everything is right; I'd say by end of November at the latest we'll have a real release system in place, and modules will get *gasp* version numbers. That’s one area I’d really like to see get some loving. Tagging a module as “4.7″ and then making changes to it that break things depending on exactly which version of the 4.7 module you’re running (or have run). Very confusing and frustrating.

This area is, in fact, getting a great deal of attention. Derek Wright is basically done with the coding and is doing testing and making sure everything is right; I’d say by end of November at the latest we’ll have a real release system in place, and modules will get *gasp* version numbers.

]]> By: dave cormier http://www.darcynorman.net/2006/10/30/trying-out-drupal-5/#comment-82533 dave cormier Wed, 31 Dec 1969 17:00:00 +0000 #comment-82533 Hey D'Arcy, I'm been having great fun poking around 5.0... The one thing about all of this that I"m not sure about is how upgrading CVSs works. Can i keep playing around and uploading new CVSs over and over again? I'm also loving the organic groups... or at least, I think I will once i understand how to use them better. We'd love to have you drop by the CMS Academy Drupal sessions sometime... (completely free, collaborative drupal learning community) http://www.cmsacademy.net/drupal/ cheers. dave. Hey D’Arcy,

I’m been having great fun poking around 5.0… The one thing about all of this that I”m not sure about is how upgrading CVSs works. Can i keep playing around and uploading new CVSs over and over again? I’m also loving the organic groups… or at least, I think I will once i understand how to use them better. We’d love to have you drop by the CMS Academy Drupal sessions sometime… (completely free, collaborative drupal learning community) http://www.cmsacademy.net/drupal/
cheers. dave.

]]> By: dnorman http://www.darcynorman.net/2006/10/30/trying-out-drupal-5/#comment-82542 dnorman Wed, 31 Dec 1969 17:00:00 +0000 #comment-82542 Merlin - thanks for the clarification. That's awesome. It will make working with various contributed modules much cleaner. Having modules with their own version numbers, and a compatible Drupal version reference (i.e., Organic Groups 2.3, compatible with Drupal 4.7, etc...) will be nice. Dave - Bill's got the answer. As long as the module developers carefully maintain the .install file, updating the code and running update.php will keep you good to go. Bill - I've looked at NA Arbitrator and Nodeaccess, but haven't seen ACL. I'll check it out ASAP. Thanks! Merlin – thanks for the clarification. That’s awesome. It will make working with various contributed modules much cleaner. Having modules with their own version numbers, and a compatible Drupal version reference (i.e., Organic Groups 2.3, compatible with Drupal 4.7, etc…) will be nice.

Dave – Bill’s got the answer. As long as the module developers carefully maintain the .install file, updating the code and running update.php will keep you good to go.

Bill – I’ve looked at NA Arbitrator and Nodeaccess, but haven’t seen ACL. I’ll check it out ASAP. Thanks!

]]> By: greggles http://www.darcynorman.net/2006/10/30/trying-out-drupal-5/#comment-82574 greggles Wed, 31 Dec 1969 17:00:00 +0000 #comment-82574 The advice on CVS is almost right with two distinctions. 1. you don't always need to run update.php, but that should be clear when you visit the page whether or not you need to do it. 2. upgrades are not supported between CVS revisions and definitely not in TRUNK-HEAD. If you are using a CVS head checkout from today and then update it in a week there may be changes that are in code, and in the new database.mysql file but which aren't in an update. That's just the nature of Drupal development. Doing otherwise would be overly restrictive. That said, you're tracking TRUNK-HEAD then you are likely savvy enough to fix any problems that you notice as a result of that, or you can drop in #drupal and ask other devs for help. The advice on CVS is almost right with two distinctions.

1. you don’t always need to run update.php, but that should be clear when you visit the page whether or not you need to do it.

2. upgrades are not supported between CVS revisions and definitely not in TRUNK-HEAD. If you are using a CVS head checkout from today and then update it in a week there may be changes that are in code, and in the new database.mysql file but which aren’t in an update. That’s just the nature of Drupal development. Doing otherwise would be overly restrictive.

That said, you’re tracking TRUNK-HEAD then you are likely savvy enough to fix any problems that you notice as a result of that, or you can drop in #drupal and ask other devs for help.

]]>