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
> ...........................................................
>
>
>
>
> 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