Hi Experts I am planning to make a site, where anybody can register his/her resume for free. Potential employers can search the resume and contact the job seeker.
For that which one is suitable Drupal6 or Drupal7.
In my view Drupal6 is well tested by this time, whereas Drupal7 is quite new. May be number of modules/themes might not be 7.x compliant.
Still as I have very limited knowledge on Drupal, I need your extert advice/recommondation which one I should use for site development D6 or D7.
Thanks - Austin
Austin: I'm also a newbie and want to learn Drupal well before I get into a situation where there might be bugs and compatibility issues. So, I went with Drupal 6. Also, there are many books to support Drupal 6, and few for 7. I do expect that by the time I learn enough to start building my own modules, I will want to be in Drupal 7, but for now, I want consistency and strong documentation.
Others may disagree, but that was my choice. Bill
William A. Prothero http://earthednet.org/
On Feb 19, 2011, at 6:23 PM, Austin Einter wrote:
Hi Experts I am planning to make a site, where anybody can register his/her resume for free. Potential employers can search the resume and contact the job seeker.
For that which one is suitable Drupal6 or Drupal7.
In my view Drupal6 is well tested by this time, whereas Drupal7 is quite new. May be number of modules/themes might not be 7.x compliant.
Still as I have very limited knowledge on Drupal, I need your extert advice/recommondation which one I should use for site development D6 or D7.
Thanks - Austin -- [ Drupal support list | http://lists.drupal.org/ ]
Hello,
We are using D6 and D7, and our customer said D7 is good user interface for make, edit content at administrator backend environment. I think customer's voice is important for community site. Also many modules does not support D7 now, however, new modules will be develop at D7. Just my information.
Cheers,
Kazu Hodota
On Feb 19, 2011, at 6:23 PM, Austin Einter wrote:
Hi Experts I am planning to make a site, where anybody can register his/her resume for free. Potential employers can search the resume and contact the job seeker.
For that which one is suitable Drupal6 or Drupal7.
In my view Drupal6 is well tested by this time, whereas Drupal7 is quite new. May be number of modules/themes might not be 7.x compliant.
Still as I have very limited knowledge on Drupal, I need your extert advice/recommondation which one I should use for site development D6 or D7.
Thanks - Austin -- [ Drupal support list | http://lists.drupal.org/ ]
Check out www.lynda.com. They have training videos on both D6 and D7. Also www.lullabot.com has a lot of information on both.
Pro Drupal Development 2nd edition for D6 by John K. VanDyk, ISBN 978-1-4302-0989-8. Pro Drupal Development 3rd edition for D7 by John K. VanDyk & Todd Tomlinson, ISBN 978-1-432-2838-7
Cory
There are also some basic Drupal 7 screencasts at http://drupaltherapy.com/date_d7
D7 is much simpler to install and maintain with many features in built into core such as CCK and Image.
Neil
On Sun, Feb 20, 2011 at 1:42 PM, Cory Gilliam imaaxa@gmail.com wrote:
Check out www.lynda.com. They have training videos on both D6 and D7. Also www.lullabot.com has a lot of information on both.
Pro Drupal Development 2nd edition for D6 by John K. VanDyk, ISBN 978-1-4302-0989-8. Pro Drupal Development 3rd edition for D7 by John K. VanDyk & Todd Tomlinson, ISBN 978-1-432-2838-7
Cory
-- [ Drupal support list | http://lists.drupal.org/ ]
Re Drupal 7 books, when I went to Amazon, I read some of the reviews of
"Pro Drupal Development 3rd edition for D7 by John K. VanDyk & Todd Tomlinson"
and the book was written before Drupal 7 was released. That gave me pause. BUT, there was a suppor web site for updates, so that may have solved the problems. It will take awhile for the incredibly rich module library to be updated to D7, but maybe only the best supported will be updated early and that will make it easier to select the most robust ones for the very huge selection of modules.
Good luck,
Bill
William A. Prothero http://earthednet.org/
On Feb 20, 2011, at 11:47 AM, Neil Adair wrote:
There are also some basic Drupal 7 screencasts at http://drupaltherapy.com/date_d7
D7 is much simpler to install and maintain with many features in built into core such as CCK and Image.
Neil
On Sun, Feb 20, 2011 at 1:42 PM, Cory Gilliam imaaxa@gmail.com wrote: Check out www.lynda.com. They have training videos on both D6 and D7. Also www.lullabot.com has a lot of information on both.
Pro Drupal Development 2nd edition for D6 by John K. VanDyk, ISBN 978-1-4302-0989-8. Pro Drupal Development 3rd edition for D7 by John K. VanDyk & Todd Tomlinson, ISBN 978-1-432-2838-7
Cory
-- [ Drupal support list | http://lists.drupal.org/ ]
-- [ Drupal support list | http://lists.drupal.org/ ]
Austin: I'm not meaning to recommend that you start with Drupal 6. Eventually, we will all want to change to version 7. I just wanted to warn of some potential difficulties for 6 mo or so, and it is hard enough to get up to speed with Drupal, without having to deal with bugs and limited documentation. Bill
William A. Prothero http://earthednet.org/
On Feb 20, 2011, at 12:43 PM, prothero wrote:
Re Drupal 7 books, when I went to Amazon, I read some of the reviews of
"Pro Drupal Development 3rd edition for D7 by John K. VanDyk & Todd Tomlinson"
and the book was written before Drupal 7 was released. That gave me pause. BUT, there was a suppor web site for updates, so that may have solved the problems. It will take awhile for the incredibly rich module library to be updated to D7, but maybe only the best supported will be updated early and that will make it easier to select the most robust ones for the very huge selection of modules.
Good luck,
Bill
William A. Prothero http://earthednet.org/
On Feb 20, 2011, at 11:47 AM, Neil Adair wrote:
There are also some basic Drupal 7 screencasts at http://drupaltherapy.com/date_d7
D7 is much simpler to install and maintain with many features in built into core such as CCK and Image.
Neil
On Sun, Feb 20, 2011 at 1:42 PM, Cory Gilliam imaaxa@gmail.com wrote: Check out www.lynda.com. They have training videos on both D6 and D7. Also www.lullabot.com has a lot of information on both.
Pro Drupal Development 2nd edition for D6 by John K. VanDyk, ISBN 978-1-4302-0989-8. Pro Drupal Development 3rd edition for D7 by John K. VanDyk & Todd Tomlinson, ISBN 978-1-432-2838-7
Cory
-- [ Drupal support list | http://lists.drupal.org/ ]
-- [ Drupal support list | http://lists.drupal.org/ ]
-- [ Drupal support list | http://lists.drupal.org/ ]
I host better than a dozen Drupal sites, and while I am planning to switch my dev site to D7 in about 6 mos, if that goes well, I'll begin to move my client sites when I discover the support for D7 (newer and better modules) is better than D6. I don't want to expose my clients to "The Bleeding Edge".
Warren Vail
_____
From: support-bounces@drupal.org [mailto:support-bounces@drupal.org] On Behalf Of prothero Sent: Sunday, February 20, 2011 1:01 PM To: support@drupal.org Subject: Re: [support] Which one is preferable - Drupal 6 OR Drupal 7
Austin:
I'm not meaning to recommend that you start with Drupal 6. Eventually, we will all want to change to version 7. I just wanted to warn of some potential difficulties for 6 mo or so, and it is hard enough to get up to speed with Drupal, without having to deal with bugs and limited documentation.
Bill
William A. Prothero
On Feb 20, 2011, at 12:43 PM, prothero wrote:
Re Drupal 7 books, when I went to Amazon, I read some of the reviews of
"Pro Drupal Development 3rd edition for D7 by John K. VanDyk & Todd Tomlinson"
and the book was written before Drupal 7 was released. That gave me pause. BUT, there was a suppor web site for updates, so that may have solved the problems. It will take awhile for the incredibly rich module library to be updated to D7, but maybe only the best supported will be updated early and that will make it easier to select the most robust ones for the very huge selection of modules.
Good luck,
Bill
William A. Prothero
On Feb 20, 2011, at 11:47 AM, Neil Adair wrote:
There are also some basic Drupal 7 screencasts at http://drupaltherapy.com/date_d7
D7 is much simpler to install and maintain with many features in built into core such as CCK and Image.
Neil
On Sun, Feb 20, 2011 at 1:42 PM, Cory Gilliam imaaxa@gmail.com wrote:
Check out www.lynda.com. They have training videos on both D6 and D7. Also www.lullabot.com has a lot of information on both.
Pro Drupal Development 2nd edition for D6 by John K. VanDyk, ISBN 978-1-4302-0989-8. Pro Drupal Development 3rd edition for D7 by John K. VanDyk & Todd Tomlinson, ISBN 978-1-432-2838-7
Cory
-- [ Drupal support list | http://lists.drupal.org/ ]
Hi,
I am using d6 for now until d7 is "mature" enough. This would be about 6 months to one year after launch.
All the best.
On 2/21/11, Warren Vail warren@vailtech.net wrote:
I host better than a dozen Drupal sites, and while I am planning to switch my dev site to D7 in about 6 mos, if that goes well, I'll begin to move my client sites when I discover the support for D7 (newer and better modules) is better than D6. I don't want to expose my clients to "The Bleeding Edge".
Warren Vail
From: support-bounces@drupal.org [mailto:support-bounces@drupal.org] On Behalf Of prothero Sent: Sunday, February 20, 2011 1:01 PM To: support@drupal.org Subject: Re: [support] Which one is preferable - Drupal 6 OR Drupal 7
Austin:
I'm not meaning to recommend that you start with Drupal 6. Eventually, we will all want to change to version 7. I just wanted to warn of some potential difficulties for 6 mo or so, and it is hard enough to get up to speed with Drupal, without having to deal with bugs and limited documentation.
Bill
William A. Prothero
On Feb 20, 2011, at 12:43 PM, prothero wrote:
Re Drupal 7 books, when I went to Amazon, I read some of the reviews of
"Pro Drupal Development 3rd edition for D7 by John K. VanDyk & Todd Tomlinson"
and the book was written before Drupal 7 was released. That gave me pause. BUT, there was a suppor web site for updates, so that may have solved the problems. It will take awhile for the incredibly rich module library to be updated to D7, but maybe only the best supported will be updated early and that will make it easier to select the most robust ones for the very huge selection of modules.
Good luck,
Bill
William A. Prothero
On Feb 20, 2011, at 11:47 AM, Neil Adair wrote:
There are also some basic Drupal 7 screencasts at http://drupaltherapy.com/date_d7
D7 is much simpler to install and maintain with many features in built into core such as CCK and Image.
Neil
On Sun, Feb 20, 2011 at 1:42 PM, Cory Gilliam imaaxa@gmail.com wrote:
Check out www.lynda.com. They have training videos on both D6 and D7. Also www.lullabot.com has a lot of information on both.
Pro Drupal Development 2nd edition for D6 by John K. VanDyk, ISBN 978-1-4302-0989-8. Pro Drupal Development 3rd edition for D7 by John K. VanDyk & Todd Tomlinson, ISBN 978-1-432-2838-7
Cory
-- [ Drupal support list | http://lists.drupal.org/ ]
-- [ Drupal support list | http://lists.drupal.org/ ]
-- [ Drupal support list | http://lists.drupal.org/ ]
Drupal 7's "maturity period" will be far shorter than it was for D6. Drupal 6 had a very long lag time while contrib caught up. For Drupal 7, we have Fields in core, tons of additional functionality in core, VIews is already usable on D7, there's hundreds of modules with stable or beta versions for D7...
My company (Palantir.net) has been building Drupal 7 sites for over six months now. If you know what you're doing, it's ready *today*. There are some significant contribs that arent ready, but that's a great opportunity for you to jump in and help get them ready. And the knowledge you gain in so doing is worth gold to clients looking for someone who can show they really know their Drupal.
Unless you need a specific module that's not already ready, and you have a tight deadline, Drupal 7 is already mature enough, I'd argue. Drupal 6 was an anomaly in that regard.
--Larry Garfield
On Monday, February 21, 2011 12:20:22 am Mutuku Ndeti wrote:
Hi,
I am using d6 for now until d7 is "mature" enough. This would be about 6 months to one year after launch.
All the best.
On 2/21/11, Warren Vail warren@vailtech.net wrote:
I host better than a dozen Drupal sites, and while I am planning to switch my dev site to D7 in about 6 mos, if that goes well, I'll begin to move my client sites when I discover the support for D7 (newer and better modules) is better than D6. I don't want to expose my clients to "The Bleeding Edge".
Warren Vail
I agree with Larry, especially if you are doing a site for a client. It's best to put them on the latest version so that they enjoy a longer support cycle on it, and considering the Drupal 6 support will be dropped in a couple of years (hopefully), it will keep them happier.
The only real problem you might have with Drupal 7 is if you are just starting out in Drupal. You won't find as much information out there on it like you can for Drupal 6, especially if you are doing any custom development in it. True Drupal has great support lists, so if you run into a snag you can always get excellent help.
Jamie Holly http://www.intoxination.net http://www.hollyit.net
On 2/21/2011 1:38 AM, Larry Garfield wrote:
Drupal 7's "maturity period" will be far shorter than it was for D6. Drupal 6 had a very long lag time while contrib caught up. For Drupal 7, we have Fields in core, tons of additional functionality in core, VIews is already usable on D7, there's hundreds of modules with stable or beta versions for D7...
My company (Palantir.net) has been building Drupal 7 sites for over six months now. If you know what you're doing, it's ready *today*. There are some significant contribs that arent ready, but that's a great opportunity for you to jump in and help get them ready. And the knowledge you gain in so doing is worth gold to clients looking for someone who can show they really know their Drupal.
Unless you need a specific module that's not already ready, and you have a tight deadline, Drupal 7 is already mature enough, I'd argue. Drupal 6 was an anomaly in that regard.
--Larry Garfield
On Monday, February 21, 2011 12:20:22 am Mutuku Ndeti wrote:
Hi,
I am using d6 for now until d7 is "mature" enough. This would be about 6 months to one year after launch.
All the best.
On 2/21/11, Warren Vailwarren@vailtech.net wrote:
I host better than a dozen Drupal sites, and while I am planning to switch my dev site to D7 in about 6 mos, if that goes well, I'll begin to move my client sites when I discover the support for D7 (newer and better modules) is better than D6. I don't want to expose my clients to "The Bleeding Edge".
Warren Vail
I agree with Larry and Jamie,
I just finished taking Webchick's Drupal 7 Tour in Washington, DC. on Saturday and Sunday.
Here are just a few of the points I learned that make D7 a great choice:
- Many of the features of Pressflow built into core - Huge initial release stability improvements due to using SimpleTest php testing suite (over 30,000 tests). - Taxonomies/vocabularies can be added to entities (users, comments, taxonomy terms, one more I didn't note) - Entities (fieldable objects), bundles (entity subsets) and instances (fields attached to entities) - Files are now objects: document storage possibilities unlocked - http://upgrade.boombatower.com/ and/or coder module help automate module upgrading from D6 to D7 - Database abstraction layer: huge improvements. Ability to use any database that php supports. - Dynamic jquery form-building without the pain: don't need to code the javascript - Theming easier and more powerful (with field-able entities giving much finer-grained control) -
http://drupal.org/update/theme/6/7 for guide to upgrade themes from D6 to D7 - Better media handling: built into core - Usability and accessibility improvements make content administration much easier, more intuitive. Admin overlay keeps the page open where you initiated it (can be disabled if preferred) - Modules can be installed via user interface.
And that's just a sampling of the things I learned. Why do a site in D6 now if you can do it in D7? It's ready, though many modules aren't. Best thing we can all do is help the effort to move more modules to D7 asap.
ultimately, D7 will be the good choice but not till spring at least...5 criticals and 200+ majors (many of which would have been critical under old system) tells you it isn't ready (and, maybe controversially, I don't think it was launch ready in Jan either)
On 21/02/2011 13:12, Marilyn Langfeld wrote:
I agree with Larry and Jamie,
I just finished taking Webchick's Drupal 7 Tour in Washington, DC. on Saturday and Sunday.
Here are just a few of the points I learned that make D7 a great choice:
* Many of the features of Pressflow built into core * Huge initial release stability improvements due to using SimpleTest php testing suite (over 30,000 tests). * Taxonomies/vocabularies can be added to entities (users, comments, taxonomy terms, one more I didn't note) * Entities (fieldable objects), bundles (entity subsets) and instances (fields attached to entities) * Files are now objects: document storage possibilities unlocked * http://upgrade.boombatower.com/ and/or coder module help automate module upgrading from D6 to D7 * Database abstraction layer: huge improvements. Ability to use any database that php supports. * Dynamic jquery form-building without the pain: don't need to code the javascript * Theming easier and more powerful (with field-able entities giving much finer-grained control)
http://drupal.org/update/theme/6/7 for guide to upgrade themes from D6 to D7
Better media handling: built into core
Usability and accessibility improvements make content administration much easier, more intuitive. Admin overlay keeps the page open where you initiated it (can be disabled if preferred)
Modules can be installed via user interface.
And that's just a sampling of the things I learned. Why do a site in D6 now if you can do it in D7? It's ready, though many modules aren't. Best thing we can all do is help the effort to move more modules to D7 asap. -- Best, Marilyn
http://twitter.com/MarilynsView
On Mon, Feb 21, 2011 at 8:24 AM, Jamie Holly <hovercrafter@earthlink.net mailto:hovercrafter@earthlink.net> wrote:
I agree with Larry, especially if you are doing a site for a client. It's best to put them on the latest version so that they enjoy a longer support cycle on it, and considering the Drupal 6 support will be dropped in a couple of years (hopefully), it will keep them happier. The only real problem you might have with Drupal 7 is if you are just starting out in Drupal. You won't find as much information out there on it like you can for Drupal 6, especially if you are doing any custom development in it. True Drupal has great support lists, so if you run into a snag you can always get excellent help. Jamie Holly http://www.intoxination.net http://www.hollyit.net On 2/21/2011 1:38 AM, Larry Garfield wrote: > Drupal 7's "maturity period" will be far shorter than it was for D6. Drupal 6 > had a very long lag time while contrib caught up. For Drupal 7, we have > Fields in core, tons of additional functionality in core, VIews is already > usable on D7, there's hundreds of modules with stable or beta versions for > D7... > > My company (Palantir.net) has been building Drupal 7 sites for over six months > now. If you know what you're doing, it's ready *today*. There are some > significant contribs that arent ready, but that's a great opportunity for you > to jump in and help get them ready. And the knowledge you gain in so doing is > worth gold to clients looking for someone who can show they really know their > Drupal. > > Unless you need a specific module that's not already ready, and you have a > tight deadline, Drupal 7 is already mature enough, I'd argue. Drupal 6 was an > anomaly in that regard. > > --Larry Garfield > > On Monday, February 21, 2011 12:20:22 am Mutuku Ndeti wrote: > > Hi, > > > > I am using d6 for now until d7 is "mature" enough. This would be about > > 6 months to one year after launch. > > > > All the best. > > > > On 2/21/11, Warren Vail<warren@vailtech.net <mailto:warren@vailtech.net>> wrote: > > > I host better than a dozen Drupal sites, and while I am planning to > > > switch my dev site to D7 in about 6 mos, if that goes well, I'll begin > > > to move my client sites when I discover the support for D7 (newer and > > > better modules) is better than D6. I don't want to expose my clients to > > > "The Bleeding Edge". > > > > > > > > > > > > Warren Vail > -- [ Drupal support list | http://lists.drupal.org/ ]
The choice of whether to use Drupal 7 now will depend on whether you already have Drupal experience, and your tolerance for pain. Drupal 7 sounds really great, but every one of the folks recommending Drupal 7 be used now, have stated that you will be helping debug and contributing to the community. This is great if you have the relevant skills, but for a newby using mostly modules and standard capabilities, will probably have a more satisfying experience by going to D6 now and upgrading in 6 mo. For example, I notice that ubercart is in beta1. For some, this is an important module. The issue of the availability of documentation and help books is also critical, especially for newbies. Drupal is somewhat complicated and a newby isn't going to know whether an issue is a bug, or a feature. Also, it sounds like there is plenty of help for upgrading to D7 from D6.
So, that said, it seems that the options are laid out pretty clearly by the replies to the initial question. Also, I'm very much looking forward to upgrading my D6 site to 7. The features listed below sound really nice.
Regards, Bill
William A. Prothero http://earthednet.org/
On Feb 21, 2011, at 8:24 AM, Neil Coghlan wrote:
ultimately, D7 will be the good choice but not till spring at least...5 criticals and 200+ majors (many of which would have been critical under old system) tells you it isn't ready (and, maybe controversially, I don't think it was launch ready in Jan either)
On 21/02/2011 13:12, Marilyn Langfeld wrote:
I agree with Larry and Jamie,
I just finished taking Webchick's Drupal 7 Tour in Washington, DC. on Saturday and Sunday.
Here are just a few of the points I learned that make D7 a great choice: Many of the features of Pressflow built into core Huge initial release stability improvements due to using SimpleTest php testing suite (over 30,000 tests). Taxonomies/vocabularies can be added to entities (users, comments, taxonomy terms, one more I didn't note) Entities (fieldable objects), bundles (entity subsets) and instances (fields attached to entities) Files are now objects: document storage possibilities unlocked http://upgrade.boombatower.com/ and/or coder module help automate module upgrading from D6 to D7 Database abstraction layer: huge improvements. Ability to use any database that php supports. Dynamic jquery form-building without the pain: don't need to code the javascript Theming easier and more powerful (with field-able entities giving much finer-grained control) http://drupal.org/update/theme/6/7 for guide to upgrade themes from D6 to D7 Better media handling: built into core Usability and accessibility improvements make content administration much easier, more intuitive. Admin overlay keeps the page open where you initiated it (can be disabled if preferred) Modules can be installed via user interface. And that's just a sampling of the things I learned. Why do a site in D6 now if you can do it in D7? It's ready, though many modules aren't. Best thing we can all do is help the effort to move more modules to D7 asap. -- Best, Marilyn
http://twitter.com/MarilynsView
On Mon, Feb 21, 2011 at 8:24 AM, Jamie Holly <hovercrafter@earthlink.net
wrote:
I agree with Larry, especially if you are doing a site for a client. It's best to put them on the latest version so that they enjoy a longer support cycle on it, and considering the Drupal 6 support will be dropped in a couple of years (hopefully), it will keep them happier.
The only real problem you might have with Drupal 7 is if you are just starting out in Drupal. You won't find as much information out there on it like you can for Drupal 6, especially if you are doing any custom development in it. True Drupal has great support lists, so if you run into a snag you can always get excellent help.
Jamie Holly http://www.intoxination.net http://www.hollyit.net
On 2/21/2011 1:38 AM, Larry Garfield wrote:
Drupal 7's "maturity period" will be far shorter than it was for
D6. Drupal 6
had a very long lag time while contrib caught up. For Drupal 7,
we have
Fields in core, tons of additional functionality in core, VIews
is already
usable on D7, there's hundreds of modules with stable or beta
versions for
D7...
My company (Palantir.net) has been building Drupal 7 sites for
over six months
now. If you know what you're doing, it's ready *today*. There
are some
significant contribs that arent ready, but that's a great
opportunity for you
to jump in and help get them ready. And the knowledge you gain
in so doing is
worth gold to clients looking for someone who can show they
really know their
Drupal.
Unless you need a specific module that's not already ready, and
you have a
tight deadline, Drupal 7 is already mature enough, I'd argue.
Drupal 6 was an
anomaly in that regard.
--Larry Garfield
On Monday, February 21, 2011 12:20:22 am Mutuku Ndeti wrote:
Hi,
I am using d6 for now until d7 is "mature" enough. This would
be about
6 months to one year after launch.
All the best.
On 2/21/11, Warren Vailwarren@vailtech.net wrote:
I host better than a dozen Drupal sites, and while I am
planning to
switch my dev site to D7 in about 6 mos, if that goes well,
I'll begin
to move my client sites when I discover the support for D7
(newer and
better modules) is better than D6. I don't want to expose
my clients to
"The Bleeding Edge".
Warren Vail
-- [ Drupal support list | http://lists.drupal.org/ ]
-- [ Drupal support list | http://lists.drupal.org/ ]
And almost everyone of those and more is present in Drupal 6. This is a terrible metric to measure Drupal 7's readiness for site building. There has been an increased tendency during the Drupal 7 cycle to fix bugs that have been in Drupal for many versions (delete/cancel user account anyone?) and we now have a testing framework (which is it's own source of bugs at times, even though those don't affect site builders).
I have yet to run into any issues at all with Drupal core while building sites on Drupal 7 and I'd say 95% of the contrib modules that I've been using are flawless as well.
What experiences have you run into that make you believe that Drupal 7 is not ready for site building?
-Mike
Neil Coghlan wrote:
ultimately, D7 will be the good choice but not till spring at least...5 criticals and 200+ majors (many of which would have been critical under old system) tells you it isn't ready (and, maybe controversially, I don't think it was launch ready in Jan either)
one of the big things that has frustrated me with Drupal 7, is that the custom menu system is broken.
By this, I mean that if you build/use a custom menu (anything other than the pre-defined menus of Primary/Secondary etc), then menus will not work as expected. The problem is that Drupal 7 does not assign the correct/necessary "active-trail" attribute to custom menu items, and therefore child items will not expand as you click through a menu.
IE: If you have a menu with parent items, you expect to be able to click on those parent items and have the children expand/display. This doesn't happen. It only happens for the menus that are part of a base install.
This is just one example, but a pretty major reason why Drupal 7 is not ready for prime-time. Sure, you could install a patch, or one of the few modules that fix or override this bug, but why should you have to install a module to do something that should work in the core? I'm not asking for new functionality, just make it work the same way as it did in Drupal 6.
I'm sure there are other examples of things that were ignored or downgraded in the rush to launch Drupal 7 in January, but this is the main one that is preventing me from rolling out any new Drupal sites. When the bugs are fixed that make the core functionality of Drupal 6 work in Drupal 7, then I'll be moving quickly to D7....because other than these bugs, it really is a very nice improvement, which i am very thankful for.
........................................................... *Nick Young* Outreach, Communications & Consulting Office of Information Technology North Carolina State University Box 7109, Raleigh 27695 Ph. 919.513.2716 | E-Mail: nick_young@ncsu.edu Web: oitdesign.ncsu.edu ...........................................................
On Mon, Feb 21, 2011 at 2:38 PM, Michael Prasuhn mike@mikeyp.net wrote:
And almost everyone of those and more is present in Drupal 6. This is a terrible metric to measure Drupal 7's readiness for site building. There has been an increased tendency during the Drupal 7 cycle to fix bugs that have been in Drupal for many versions (delete/cancel user account anyone?) and we now have a testing framework (which is it's own source of bugs at times, even though those don't affect site builders).
I have yet to run into any issues at all with Drupal core while building sites on Drupal 7 and I'd say 95% of the contrib modules that I've been using are flawless as well.
What experiences have you run into that make you believe that Drupal 7 is not ready for site building?
-Mike
Neil Coghlan wrote:
ultimately, D7 will be the good choice but not till spring at least...5 criticals and 200+ majors (many of which would have been critical under old system) tells you it isn't ready (and, maybe controversially, I don't think it was launch ready in Jan either)
-- __________________ Michael Prasuhn 503.512.0822 office mike@mikeyp.net http://mikeyp.net -- [ Drupal support list | http://lists.drupal.org/ ]
The menu system was broken in the extreme in Drupal 6, too, just in different ways. :-) You should see the number of menu system hack modules that were still being developed even late in Drupal 6's lifecycle.
Is there an open issue for the bug you mention? If not, have you filed one? Bugs don't fix themselves. We need everyone's help to get a system as complex as Drupal really really polished.
--Larry Garfield
On 2/21/11 2:18 PM, Nick Young wrote:
one of the big things that has frustrated me with Drupal 7, is that the custom menu system is broken.
By this, I mean that if you build/use a custom menu (anything other than the pre-defined menus of Primary/Secondary etc), then menus will not work as expected. The problem is that Drupal 7 does not assign the correct/necessary "active-trail" attribute to custom menu items, and therefore child items will not expand as you click through a menu.
IE: If you have a menu with parent items, you expect to be able to click on those parent items and have the children expand/display. This doesn't happen. It only happens for the menus that are part of a base install.
This is just one example, but a pretty major reason why Drupal 7 is not ready for prime-time. Sure, you could install a patch, or one of the few modules that fix or override this bug, but why should you have to install a module to do something that should work in the core? I'm not asking for new functionality, just make it work the same way as it did in Drupal 6.
I'm sure there are other examples of things that were ignored or downgraded in the rush to launch Drupal 7 in January, but this is the main one that is preventing me from rolling out any new Drupal sites. When the bugs are fixed that make the core functionality of Drupal 6 work in Drupal 7, then I'll be moving quickly to D7....because other than these bugs, it really is a very nice improvement, which i am very thankful for.
........................................................... *Nick Young* Outreach, Communications & Consulting Office of Information Technology North Carolina State University Box 7109, Raleigh 27695 Ph. 919.513.2716 | E-Mail: nick_young@ncsu.edu mailto:nick_young@ncsu.edu Web: oitdesign.ncsu.edu http://oitdesign.ncsu.edu/ ...........................................................
On Mon, Feb 21, 2011 at 2:38 PM, Michael Prasuhn <mike@mikeyp.net mailto:mike@mikeyp.net> wrote:
And almost everyone of those and more is present in Drupal 6. This is a terrible metric to measure Drupal 7's readiness for site building. There has been an increased tendency during the Drupal 7 cycle to fix bugs that have been in Drupal for many versions (delete/cancel user account anyone?) and we now have a testing framework (which is it's own source of bugs at times, even though those don't affect site builders). I have yet to run into any issues at all with Drupal core while building sites on Drupal 7 and I'd say 95% of the contrib modules that I've been using are flawless as well. What experiences have you run into that make you believe that Drupal 7 is not ready for site building? -Mike Neil Coghlan wrote: > ultimately, D7 will be the good choice but not till spring at least...5 > criticals and 200+ majors (many of which would have been critical under > old system) tells you it isn't ready (and, maybe controversially, I > don't think it was launch ready in Jan either) > -- __________________ Michael Prasuhn 503.512.0822 office mike@mikeyp.net <mailto:mike@mikeyp.net> http://mikeyp.net -- [ Drupal support list | http://lists.drupal.org/ ]
The menu bug i mentioned is filed, and was actually listed as critical prior to the D7 launch. Due to the nature of it, there were a few concurrent bugs that were filed with this same symptom...it just took a while for the root cause to be identified. http://drupal.org/node/942782
My biggest concern about D7 though, is that in the lead-up to the January launch, critical bugs were downgraded, seemingly to meet the deadline. Instead of keeping to the "we'll release D7 when all critical bugs are fixed," it became "we'll reclassify critical bugs as major, which means we can now release D7." This was never more evident to me than the comment on that bug thread above which said "I can see this is nasty if you run into it, but I don't see how it is critical."
I don't want to hijack this thread though, as there is a good discussion to be had about what sites or projects are suited to D7's current state. I just think that this particular bug is representative of the larger issue surrounding how "ready" Drupal 7 is for production sites (ie: it's not).
--Nick
........................................................... *Nick Young* Outreach, Communications & Consulting Office of Information Technology North Carolina State University Box 7109, Raleigh 27695 Ph. 919.513.2716 | E-Mail: nick_young@ncsu.edu Web: oitdesign.ncsu.edu ...........................................................
On Mon, Feb 21, 2011 at 3:30 PM, larry@garfieldtech.com < larry@garfieldtech.com> wrote:
The menu system was broken in the extreme in Drupal 6, too, just in different ways. :-) You should see the number of menu system hack modules that were still being developed even late in Drupal 6's lifecycle.
Is there an open issue for the bug you mention? If not, have you filed one? Bugs don't fix themselves. We need everyone's help to get a system as complex as Drupal really really polished.
--Larry Garfield
On 2/21/11 2:18 PM, Nick Young wrote:
one of the big things that has frustrated me with Drupal 7, is that the custom menu system is broken.
By this, I mean that if you build/use a custom menu (anything other than the pre-defined menus of Primary/Secondary etc), then menus will not work as expected. The problem is that Drupal 7 does not assign the correct/necessary "active-trail" attribute to custom menu items, and therefore child items will not expand as you click through a menu.
IE: If you have a menu with parent items, you expect to be able to click on those parent items and have the children expand/display. This doesn't happen. It only happens for the menus that are part of a base install.
This is just one example, but a pretty major reason why Drupal 7 is not ready for prime-time. Sure, you could install a patch, or one of the few modules that fix or override this bug, but why should you have to install a module to do something that should work in the core? I'm not asking for new functionality, just make it work the same way as it did in Drupal 6.
I'm sure there are other examples of things that were ignored or downgraded in the rush to launch Drupal 7 in January, but this is the main one that is preventing me from rolling out any new Drupal sites. When the bugs are fixed that make the core functionality of Drupal 6 work in Drupal 7, then I'll be moving quickly to D7....because other than these bugs, it really is a very nice improvement, which i am very thankful for.
........................................................... *Nick Young* Outreach, Communications & Consulting Office of Information Technology North Carolina State University Box 7109, Raleigh 27695 Ph. 919.513.2716 | E-Mail: nick_young@ncsu.edu <mailto:
nick_young@ncsu.edu>
Web: oitdesign.ncsu.edu http://oitdesign.ncsu.edu/ ...........................................................
On Mon, Feb 21, 2011 at 2:38 PM, Michael Prasuhn <mike@mikeyp.net mailto:mike@mikeyp.net> wrote:
And almost everyone of those and more is present in Drupal 6. This isa
terrible metric to measure Drupal 7's readiness for site building.There
has been an increased tendency during the Drupal 7 cycle to fix bugs that have been in Drupal for many versions (delete/cancel useraccount
anyone?) and we now have a testing framework (which is it's ownsource
of bugs at times, even though those don't affect site builders). I have yet to run into any issues at all with Drupal core whilebuilding
sites on Drupal 7 and I'd say 95% of the contrib modules that I'vebeen
using are flawless as well. What experiences have you run into that make you believe that Drupal7
is not ready for site building? -Mike Neil Coghlan wrote: > ultimately, D7 will be the good choice but not till spring at least...5 > criticals and 200+ majors (many of which would have been critical under > old system) tells you it isn't ready (and, maybe controversially,I
> don't think it was launch ready in Jan either) > -- __________________ Michael Prasuhn 503.512.0822 office mike@mikeyp.net <mailto:mike@mikeyp.net> http://mikeyp.net -- [ Drupal support list | http://lists.drupal.org/ ]-- [ Drupal support list | http://lists.drupal.org/ ]
Again, I have to disagree. A lot of bugs were downgraded from critical because critical was being abused for "really bad" rather than "Drupal doesn't work at all if this isn't fixed", which is what it is supposed to be for.
Eg, an issue that affects installation of the database under certain configurations of Mac OS X due to a misconfiguration bug in OS X is certainly bad, and prevents people in those configurations from installing Drupal without fixing the configuration bug first. However, it doesn't mean that Drupal breaks in all or even most circumstances. (That's an actual bug that was downgraded from critical at one point.)
Consider too that Drupal 6 as of right now has over 350 critical issues filed against it:
http://drupal.org/project/issues/drupal?priorities=1&version=6.x
So I guess Drupal 6 isn't ready for production either. ;-)
I'm not saying that Drupal 7 is bug-free. It's not. It is, however, the most "ready" .0 release of Drupal, both for core and contrib, in many many years. People have been launching sites on it large and small for six months, including the US government.
--Larry Garfield
On 2/21/11 2:48 PM, Nick Young wrote:
The menu bug i mentioned is filed, and was actually listed as critical prior to the D7 launch. Due to the nature of it, there were a few concurrent bugs that were filed with this same symptom...it just took a while for the root cause to be identified. http://drupal.org/node/942782
My biggest concern about D7 though, is that in the lead-up to the January launch, critical bugs were downgraded, seemingly to meet the deadline. Instead of keeping to the "we'll release D7 when all critical bugs are fixed," it became "we'll reclassify critical bugs as major, which means we can now release D7." This was never more evident to me than the comment on that bug thread above which said "I can see this is nasty if you run into it, but I don't see how it is critical."
I don't want to hijack this thread though, as there is a good discussion to be had about what sites or projects are suited to D7's current state. I just think that this particular bug is representative of the larger issue surrounding how "ready" Drupal 7 is for production sites (ie: it's not).
--Nick
........................................................... *Nick Young* Outreach, Communications & Consulting Office of Information Technology North Carolina State University Box 7109, Raleigh 27695 Ph. 919.513.2716 | E-Mail: nick_young@ncsu.edu mailto:nick_young@ncsu.edu Web: oitdesign.ncsu.edu http://oitdesign.ncsu.edu/ ...........................................................
On Mon, Feb 21, 2011 at 3:30 PM, larry@garfieldtech.com mailto:larry@garfieldtech.com <larry@garfieldtech.com mailto:larry@garfieldtech.com> wrote:
The menu system was broken in the extreme in Drupal 6, too, just in different ways. :-) You should see the number of menu system hack modules that were still being developed even late in Drupal 6's lifecycle. Is there an open issue for the bug you mention? If not, have you filed one? Bugs don't fix themselves. We need everyone's help to get a system as complex as Drupal really really polished. --Larry Garfield On 2/21/11 2:18 PM, Nick Young wrote: > one of the big things that has frustrated me with Drupal 7, is that the > custom menu system is broken. > > By this, I mean that if you build/use a custom menu (anything other than > the pre-defined menus of Primary/Secondary etc), then menus will not > work as expected. The problem is that Drupal 7 does not assign the > correct/necessary "active-trail" attribute to custom menu items, and > therefore child items will not expand as you click through a menu. > > IE: If you have a menu with parent items, you expect to be able to click > on those parent items and have the children expand/display. This doesn't > happen. It only happens for the menus that are part of a base install. > > This is just one example, but a pretty major reason why Drupal 7 is not > ready for prime-time. Sure, you could install a patch, or one of the few > modules that fix or override this bug, but why should you have to > install a module to do something that should work in the core? I'm not > asking for new functionality, just make it work the same way as it did > in Drupal 6. > > I'm sure there are other examples of things that were ignored or > downgraded in the rush to launch Drupal 7 in January, but this is the > main one that is preventing me from rolling out any new Drupal sites. > When the bugs are fixed that make the core functionality of Drupal 6 > work in Drupal 7, then I'll be moving quickly to D7....because other > than these bugs, it really is a very nice improvement, which i am very > thankful for. > > ........................................................... > *Nick Young* > Outreach, Communications & Consulting > Office of Information Technology > North Carolina State University > Box 7109, Raleigh 27695 > Ph. 919.513.2716 | E-Mail: nick_young@ncsu.edu <mailto:nick_young@ncsu.edu> <mailto:nick_young@ncsu.edu <mailto:nick_young@ncsu.edu>> > Web: oitdesign.ncsu.edu <http://oitdesign.ncsu.edu> <http://oitdesign.ncsu.edu/> > ...........................................................
Larry, I think you misunderstand the point. The point is not whether Drupal 7 is ready for hot shot Drupal agencies to use for high-end clients using a team of rocket scientists.
Or whether Drupal 7 was hurried out the door to satisfy the business models of some companies.
The point is whether regular people, site builders with no special core experience, would be able to find Drupal 7 usable, just as when WordPress comes out and is generally usable as advertised.
Nick isn't even saying it's the only valid approach, he's saying that's the one he is following; and I certainly agree with him.
Victor Kane http://awebfactory.com.ar
On Mon, Feb 21, 2011 at 5:58 PM, larry@garfieldtech.com < larry@garfieldtech.com> wrote:
Again, I have to disagree. A lot of bugs were downgraded from critical because critical was being abused for "really bad" rather than "Drupal doesn't work at all if this isn't fixed", which is what it is supposed to be for.
Eg, an issue that affects installation of the database under certain configurations of Mac OS X due to a misconfiguration bug in OS X is certainly bad, and prevents people in those configurations from installing Drupal without fixing the configuration bug first. However, it doesn't mean that Drupal breaks in all or even most circumstances. (That's an actual bug that was downgraded from critical at one point.)
Consider too that Drupal 6 as of right now has over 350 critical issues filed against it:
http://drupal.org/project/issues/drupal?priorities=1&version=6.x
So I guess Drupal 6 isn't ready for production either. ;-)
I'm not saying that Drupal 7 is bug-free. It's not. It is, however, the most "ready" .0 release of Drupal, both for core and contrib, in many many years. People have been launching sites on it large and small for six months, including the US government.
--Larry Garfield
On 2/21/11 2:48 PM, Nick Young wrote:
The menu bug i mentioned is filed, and was actually listed as critical prior to the D7 launch. Due to the nature of it, there were a few concurrent bugs that were filed with this same symptom...it just took a while for the root cause to be identified. http://drupal.org/node/942782
My biggest concern about D7 though, is that in the lead-up to the January launch, critical bugs were downgraded, seemingly to meet the deadline. Instead of keeping to the "we'll release D7 when all critical bugs are fixed," it became "we'll reclassify critical bugs as major, which means we can now release D7." This was never more evident to me than the comment on that bug thread above which said "I can see this is nasty if you run into it, but I don't see how it is critical."
I don't want to hijack this thread though, as there is a good discussion to be had about what sites or projects are suited to D7's current state. I just think that this particular bug is representative of the larger issue surrounding how "ready" Drupal 7 is for production sites (ie: it's not).
--Nick
........................................................... *Nick Young* Outreach, Communications & Consulting Office of Information Technology North Carolina State University Box 7109, Raleigh 27695 Ph. 919.513.2716 | E-Mail: nick_young@ncsu.edu <mailto:
nick_young@ncsu.edu>
Web: oitdesign.ncsu.edu http://oitdesign.ncsu.edu/ ...........................................................
On Mon, Feb 21, 2011 at 3:30 PM, larry@garfieldtech.com mailto:larry@garfieldtech.com <larry@garfieldtech.com mailto:larry@garfieldtech.com> wrote:
The menu system was broken in the extreme in Drupal 6, too, just in different ways. :-) You should see the number of menu system hack modules that were still being developed even late in Drupal 6's lifecycle. Is there an open issue for the bug you mention? If not, have youfiled
one? Bugs don't fix themselves. We need everyone's help to get a system as complex as Drupal really really polished. --Larry Garfield On 2/21/11 2:18 PM, Nick Young wrote: > one of the big things that has frustrated me with Drupal 7, is that the > custom menu system is broken. > > By this, I mean that if you build/use a custom menu (anything other than > the pre-defined menus of Primary/Secondary etc), then menus willnot
> work as expected. The problem is that Drupal 7 does not assign the > correct/necessary "active-trail" attribute to custom menu items,and
> therefore child items will not expand as you click through a menu. > > IE: If you have a menu with parent items, you expect to be able to click > on those parent items and have the children expand/display. This doesn't > happen. It only happens for the menus that are part of a base install. > > This is just one example, but a pretty major reason why Drupal 7 is not > ready for prime-time. Sure, you could install a patch, or one of the few > modules that fix or override this bug, but why should you have to > install a module to do something that should work in the core? I'm not > asking for new functionality, just make it work the same way as it did > in Drupal 6. > > I'm sure there are other examples of things that were ignored or > downgraded in the rush to launch Drupal 7 in January, but this isthe
> main one that is preventing me from rolling out any new Drupalsites.
> When the bugs are fixed that make the core functionality of Drupal6
> work in Drupal 7, then I'll be moving quickly to D7....becauseother
> than these bugs, it really is a very nice improvement, which i am very > thankful for. > > ........................................................... > *Nick Young* > Outreach, Communications & Consulting > Office of Information Technology > North Carolina State University > Box 7109, Raleigh 27695 > Ph. 919.513.2716 | E-Mail: nick_young@ncsu.edu <mailto:nick_young@ncsu.edu> <mailto:nick_young@ncsu.edu <mailto:nick_young@ncsu.edu>> > Web: oitdesign.ncsu.edu <http://oitdesign.ncsu.edu> <http://oitdesign.ncsu.edu/> > ...........................................................-- [ Drupal support list | http://lists.drupal.org/ ]
thought this was relevant to our discussions the other day:
http://www.drupalmill.com/blog/tsvenson/2011/02/23/drupal-7-not-ready-produc...
On 21/02/2011 18:22, Victor Kane wrote:
Larry, I think you misunderstand the point. The point is not whether Drupal 7 is ready for hot shot Drupal agencies to use for high-end clients using a team of rocket scientists.
Or whether Drupal 7 was hurried out the door to satisfy the business models of some companies.
The point is whether regular people, site builders with no special core experience, would be able to find Drupal 7 usable, just as when WordPress comes out and is generally usable as advertised.
Nick isn't even saying it's the only valid approach, he's saying that's the one he is following; and I certainly agree with him.
Victor Kane http://awebfactory.com.ar
On Mon, Feb 21, 2011 at 5:58 PM, larry@garfieldtech.com mailto:larry@garfieldtech.com <larry@garfieldtech.com mailto:larry@garfieldtech.com> wrote:
Again, I have to disagree. A lot of bugs were downgraded from critical because critical was being abused for "really bad" rather than "Drupal doesn't work at all if this isn't fixed", which is what it is supposed to be for. Eg, an issue that affects installation of the database under certain configurations of Mac OS X due to a misconfiguration bug in OS X is certainly bad, and prevents people in those configurations from installing Drupal without fixing the configuration bug first. However, it doesn't mean that Drupal breaks in all or even most circumstances. (That's an actual bug that was downgraded from critical at one point.) Consider too that Drupal 6 as of right now has over 350 critical issues filed against it: http://drupal.org/project/issues/drupal?priorities=1&version=6.x <http://drupal.org/project/issues/drupal?priorities=1&version=6.x> So I guess Drupal 6 isn't ready for production either. ;-) I'm not saying that Drupal 7 is bug-free. It's not. It is, however, the most "ready" .0 release of Drupal, both for core and contrib, in many many years. People have been launching sites on it large and small for six months, including the US government. --Larry Garfield On 2/21/11 2:48 PM, Nick Young wrote: > The menu bug i mentioned is filed, and was actually listed as critical > prior to the D7 launch. Due to the nature of it, there were a few > concurrent bugs that were filed with this same symptom...it just took a > while for the root cause to be identified. http://drupal.org/node/942782 > > My biggest concern about D7 though, is that in the lead-up to the > January launch, critical bugs were downgraded, seemingly to meet the > deadline. Instead of keeping to the "we'll release D7 when all critical > bugs are fixed," it became "we'll reclassify critical bugs as major, > which means we can now release D7." This was never more evident to me > than the comment on that bug thread above which said "I can see this is > nasty if you run into it, but I don't see how it is critical." > > I don't want to hijack this thread though, as there is a good discussion > to be had about what sites or projects are suited to D7's current state. > I just think that this particular bug is representative of the larger > issue surrounding how "ready" Drupal 7 is for production sites (ie: it's > not). > > --Nick > > ........................................................... > *Nick Young* > Outreach, Communications & Consulting > Office of Information Technology > North Carolina State University > Box 7109, Raleigh 27695 > Ph. 919.513.2716 | E-Mail: nick_young@ncsu.edu <mailto:nick_young@ncsu.edu> <mailto:nick_young@ncsu.edu <mailto:nick_young@ncsu.edu>> > Web: oitdesign.ncsu.edu <http://oitdesign.ncsu.edu> <http://oitdesign.ncsu.edu/> > ........................................................... > > > > > On Mon, Feb 21, 2011 at 3:30 PM, larry@garfieldtech.com <mailto:larry@garfieldtech.com> > <mailto:larry@garfieldtech.com <mailto:larry@garfieldtech.com>> <larry@garfieldtech.com <mailto:larry@garfieldtech.com> > <mailto:larry@garfieldtech.com <mailto:larry@garfieldtech.com>>> wrote: > > The menu system was broken in the extreme in Drupal 6, too, just in > different ways. :-) You should see the number of menu system hack > modules that were still being developed even late in Drupal 6's > lifecycle. > > Is there an open issue for the bug you mention? If not, have you filed > one? Bugs don't fix themselves. We need everyone's help to get a > system as complex as Drupal really really polished. > > --Larry Garfield > > On 2/21/11 2:18 PM, Nick Young wrote: > > one of the big things that has frustrated me with Drupal 7, is > that the > > custom menu system is broken. > > > > By this, I mean that if you build/use a custom menu (anything > other than > > the pre-defined menus of Primary/Secondary etc), then menus will not > > work as expected. The problem is that Drupal 7 does not assign the > > correct/necessary "active-trail" attribute to custom menu items, and > > therefore child items will not expand as you click through a menu. > > > > IE: If you have a menu with parent items, you expect to be able > to click > > on those parent items and have the children expand/display. This > doesn't > > happen. It only happens for the menus that are part of a base > install. > > > > This is just one example, but a pretty major reason why Drupal 7 > is not > > ready for prime-time. Sure, you could install a patch, or one of > the few > > modules that fix or override this bug, but why should you have to > > install a module to do something that should work in the core? > I'm not > > asking for new functionality, just make it work the same way as > it did > > in Drupal 6. > > > > I'm sure there are other examples of things that were ignored or > > downgraded in the rush to launch Drupal 7 in January, but this is the > > main one that is preventing me from rolling out any new Drupal sites. > > When the bugs are fixed that make the core functionality of Drupal 6 > > work in Drupal 7, then I'll be moving quickly to D7....because other > > than these bugs, it really is a very nice improvement, which i am > very > > thankful for. > > > > ........................................................... > > *Nick Young* > > Outreach, Communications & Consulting > > Office of Information Technology > > North Carolina State University > > Box 7109, Raleigh 27695 > > Ph. 919.513.2716 | E-Mail: nick_young@ncsu.edu <mailto:nick_young@ncsu.edu> > <mailto:nick_young@ncsu.edu <mailto:nick_young@ncsu.edu>> <mailto:nick_young@ncsu.edu <mailto:nick_young@ncsu.edu> > <mailto:nick_young@ncsu.edu <mailto:nick_young@ncsu.edu>>> > > Web: oitdesign.ncsu.edu <http://oitdesign.ncsu.edu> <http://oitdesign.ncsu.edu> > <http://oitdesign.ncsu.edu/> > > ........................................................... -- [ Drupal support list | http://lists.drupal.org/ ]
Nick, took the words out of my mouth. The menu bug is horrible and as you put it, one of the reasons it's not "ready for prime time". But it soon will be...april/may at a guess. In all the huge list of "major" bugs that still exist, there's a good few that I personally consider deal breakers for me ....YMMV.
this is a serious one too: http://drupal.org/node/1017672
On 21/02/2011 17:18, Nick Young wrote:
one of the big things that has frustrated me with Drupal 7, is that the custom menu system is broken.
By this, I mean that if you build/use a custom menu (anything other than the pre-defined menus of Primary/Secondary etc), then menus will not work as expected. The problem is that Drupal 7 does not assign the correct/necessary "active-trail" attribute to custom menu items, and therefore child items will not expand as you click through a menu.
IE: If you have a menu with parent items, you expect to be able to click on those parent items and have the children expand/display. This doesn't happen. It only happens for the menus that are part of a base install.
This is just one example, but a pretty major reason why Drupal 7 is not ready for prime-time. Sure, you could install a patch, or one of the few modules that fix or override this bug, but why should you have to install a module to do something that should work in the core? I'm not asking for new functionality, just make it work the same way as it did in Drupal 6.
I'm sure there are other examples of things that were ignored or downgraded in the rush to launch Drupal 7 in January, but this is the main one that is preventing me from rolling out any new Drupal sites. When the bugs are fixed that make the core functionality of Drupal 6 work in Drupal 7, then I'll be moving quickly to D7....because other than these bugs, it really is a very nice improvement, which i am very thankful for.
........................................................... *Nick Young* Outreach, Communications & Consulting Office of Information Technology North Carolina State University Box 7109, Raleigh 27695 Ph. 919.513.2716 | E-Mail: nick_young@ncsu.edu mailto:nick_young@ncsu.edu Web: oitdesign.ncsu.edu http://oitdesign.ncsu.edu/ ...........................................................
On Mon, Feb 21, 2011 at 2:38 PM, Michael Prasuhn <mike@mikeyp.net mailto:mike@mikeyp.net> wrote:
And almost everyone of those and more is present in Drupal 6. This is a terrible metric to measure Drupal 7's readiness for site building. There has been an increased tendency during the Drupal 7 cycle to fix bugs that have been in Drupal for many versions (delete/cancel user account anyone?) and we now have a testing framework (which is it's own source of bugs at times, even though those don't affect site builders). I have yet to run into any issues at all with Drupal core while building sites on Drupal 7 and I'd say 95% of the contrib modules that I've been using are flawless as well. What experiences have you run into that make you believe that Drupal 7 is not ready for site building? -Mike Neil Coghlan wrote: > ultimately, D7 will be the good choice but not till spring at least...5 > criticals and 200+ majors (many of which would have been critical under > old system) tells you it isn't ready (and, maybe controversially, I > don't think it was launch ready in Jan either) > -- __________________ Michael Prasuhn 503.512.0822 office mike@mikeyp.net <mailto:mike@mikeyp.net> http://mikeyp.net -- [ Drupal support list | http://lists.drupal.org/ ]
-
Austin Einter -
Cory Gilliam -
Gennai3 Hodota -
Jamie Holly -
Larry Garfield -
larry＠garfieldtech.com
-
Marilyn Langfeld -
Michael Prasuhn -
Mutuku Ndeti -
Neil Adair -
Neil Coghlan -
Nick Young -
prothero -
Victor Kane -
Warren Vail