[support] Which one is preferable - Drupal 6 OR Drupal 7
Neil Coghlan
neil at esl-lounge.com
Wed Feb 23 15:08:25 UTC 2011
thought this was relevant to our discussions the other day:
http://www.drupalmill.com/blog/tsvenson/2011/02/23/drupal-7-not-ready-production-yet
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 at garfieldtech.com
> <mailto:larry at garfieldtech.com> <larry at garfieldtech.com
> <mailto:larry at 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 at ncsu.edu
> <mailto:nick_young at ncsu.edu> <mailto:nick_young at ncsu.edu
> <mailto:nick_young at ncsu.edu>>
> > Web: oitdesign.ncsu.edu <http://oitdesign.ncsu.edu>
> <http://oitdesign.ncsu.edu/>
> > ...........................................................
> >
> >
> >
> >
> > On Mon, Feb 21, 2011 at 3:30 PM, larry at garfieldtech.com
> <mailto:larry at garfieldtech.com>
> > <mailto:larry at garfieldtech.com <mailto:larry at garfieldtech.com>>
> <larry at garfieldtech.com <mailto:larry at garfieldtech.com>
> > <mailto:larry at garfieldtech.com <mailto:larry at 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 at ncsu.edu
> <mailto:nick_young at ncsu.edu>
> > <mailto:nick_young at ncsu.edu <mailto:nick_young at ncsu.edu>>
> <mailto:nick_young at ncsu.edu <mailto:nick_young at ncsu.edu>
> > <mailto:nick_young at ncsu.edu <mailto:nick_young at 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/ ]
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/support/attachments/20110223/1a92dfaf/attachment.html
More information about the support
mailing list