By jshock on

I am still developing new sites in D6. Every time I start a new site I ask myself if I should start using D7? The problem is that so many critical modules are still only stable in 6. I am dreading the day when I will have to start migrating legacy sites to D7. I started two simple sites with D7, but in both cases the clients added features (during the testing phase) that were simple using modules available only in D6. The most economical solution was to downgrade to D6 rather than find work-arounds or program a custom solution. What is the general consensus on using D7 for production sites?

Comments

pixelsweatshop’s picture

pixelsweatshop commented

We are a moderately-sized Drupal shop and every project (small-large) is being built and has been built on D7 since June, 2011. The only way D7 is going to get solid is if we use it, test it and allocate some of our client's project funds to help Drupal 7 core/contrib along. This means using dev versions of modules or even straight from git. This also requires having an open and honest conversation with your clients about how open source and Drupal works. Make them a part of the decision to choose 6 or 7. A few points of discussion with your clients:

1. They get excited to know that they are going to get a longer shelf life on their site, if it's built on D7.
2. It might take a bit longer to develop, but an extra month now, means a couple more years later.
3. They won't have to go through an expensive upgrade in the next few years.
4. Get them to understand that they are now a part of the open source/drupal community. They are investing in everyone succeeding (even if your not supplying patches, just testing, it's still contributing).
5. There might be one or two features that may have to wait until a module is ported or a bug is fixed. They can easily be added in a month or two after the site is live.

I hope this helps. I am sure others with chime in. But the only way were are all going to succeed is if we are all moving forward with D7.

WorldFallz’s picture

WorldFallz commented

Based on reported usage, d7 is catching up to d6 pretty fast. afaic, I assume d7 unless a critical module or functionality requires d6. imo it's best to avoid the pain of a major version upgrade whenever possible.

juan_g’s picture

juan_g commented

Based on reported usage, d7 is catching up to d6 pretty fast

That's right.

November 20th:

Drupal 5: 1.35%
Drupal 6: 57.86%
Drupal 7: 40.77%
Drupal 8: 0.01%

Codeblind’s picture

Codeblind commented

I do some stuff for a couple big universities and they only support D6, even on new sites. I'm trying to move smaller clients with straightforward needs to D7. This problem with much used modules not being ready for prime time in D7, or even abandoned to rot, is pretty much the same thing that happened with D5 to D6, and it will likely happen with D7 to D8. They were a little more on the ball with D7, especially with CCK and Views being more or less ready at rollout. A lot of people made a great effort, but there are only so many hours in the day and Core keeps rewriting large chunks of the API. It's hard to keep up.

bojanz’s picture

bojanz commented

The problem with teams developing with Drupal but not contributing to actual module development is that they often feel out of control ("modules not being ready for prime time in D7, or even abandoned to rot"). It is a sentiment I frequently see online.
I know many companies doing D7 only, and when they come across such a module, they put in resources to port or fix the module (took me a week to get VBO to a point where it can start moving and getting bugfixes fast. Sometimes it only takes a day to fix a glaring blocking problem), and move on with their project.
Of course, not everyone has the resources to do so, I'm writing this because of the companies that do have the resources, but are too scared, lazy, or unwilling to invest money (they exist).

aerconditionatshop’s picture

aerconditionatshop commented

I still use D6 for the same reason, stability, i have a lot of pain until i make all to work together and i don't like to make again the same job, end from some of the components i believe is still not have support for D7

john_b’s picture

john_b commented

I only use D7. I has given me some headaches, as has the upgrade path from D6. I can afford to because I am not working on very large sites, or answerable to big IT departments.

However the attitude of core ('we do our job properly, if contrib are behind the curve that is their problem'), is damaging for Drupal overall IMO. The idea that Drupal 7 is ready for the world just because core are doing a fantastic job (as they are), without Views, Panels, Rules etc is unrealistic. Fortunately these modules do now work. I would like to see a more holistic approach between development core and the major contrib modules. For most sites, even the relatively small sites I work on, Views and Ctools, and possibly a few others, are not in reality dispensable, or optional extras.

In some situations you need the latest version of ctools, which is labelled dev. Sure it works, and it maintainers, especially its main maintainer, deserve great respect & gratitude. Still, I can imagine that some big companies or government departments might be scared off by the dev label, and run back to Drupal 6 or commercial CMS, which is 'officially' supported, as a matter of policy? It would be easier to 'sell' Drupal 7 if it contrib and core development were more integrated. I fear this split will get wider with D8.

Digit Professionals specialising in Drupal, WordPress & CiviCRM support for publishers in non-profit and related sectors

WorldFallz’s picture

WorldFallz commented

'we do our job properly, if contrib are behind the curve that is their problem'

not sure where you got that idea, but that is sooooo not the case-- just google around for 'd7cx', 'drupal wtf', DrupalWTF, etc. See http://www.webchick.net/taxonomy/term/64, http://cyrve.com/d7cx, http://cyrve.com/d7cx2.

john_b’s picture

john_b commented

That was my interpretation of your post here http://drupal.org/node/1138306#comment-4645260

To be fair, what you say is

there's no reason to hold up the next core dev branch waiting for contrib to catch up.

What I thought I read (because I did not read carefully) was 'there is no reason to hold up a full release (e.g. D7, D8) waiting for contrib to catch up.'

Digit Professionals specialising in Drupal, WordPress & CiviCRM support for publishers in non-profit and related sectors

WorldFallz’s picture

WorldFallz commented

ah ok... I can sort of see where you might interpret it that way. But actually, my main point in that comment was that holding up core will not automatically make more resources available to work on contributed modules. Simply holding up (slowing down) core development will not redirect core developers to work on contributed modules if that's not something they want to do. And, in fact, core developers who do also maintain contributed modules tend to be among the first ones to upgrade their contribs-- in spite of their increased workload due to straddling both worlds.

To be sure-- the "the drop is always moving" philosophy and the core development schedule are definitely a challenge to contributed module maintainers (myself included), but it's a rather large, and invalid imo, jump from that challenge to "we do our job properly, if contrib are behind the curve that is their problem".

addylo’s picture

addylo commented

From the perspective of a long-time user (and huge fan) of Drupal...

I had my Drupal 6 site hacked recently and took the opportunity to start clean with a fresh 7 install. In hindsight this was a huge mistake. Despite the core being "stable" (which is questionable IMO) I do NOT consider 7 to be ready for prime-time due to the instability of most of the modules, even those that advertise as being 7-ready. I have yet to get most of the modules that I need for the full functionality of my website to work in 7.

I hate to return to 6 but it seems very likely at this stage. Security updates is a major concern after being hacked.

I'm seriously considering going with a different CMS. This is not a path I want to take but at this point it's probably my best option in order to have a fully functioning website. If driving users away from Drupal is the intention then keep up the good work.

juan_g’s picture

juan_g commented

And details on how you can help:

Drupal 7 contributed project porting status
http://drupalcontribstatus.com/

Hit-list for top Drupal 7 module stabilization
http://webchick.net/node/103

D7 stable release blockers (contrib)
http://drupal.org/project/issues/search?projects=&status[]=Open&issue_tags=D7+stable+release+blocker

thaistore’s picture

thaistore commented

i made the last site in Ubercart, but I opted for D6, D7 did not have supported modules, and there were still many bugs present

D6 ubercart works like a charm

risking the whole site with D7 might be a big problem

Drupal webdesign - regular sites and ubercart ecommerce sites
Drupal webdesign

drupal3013’s picture

drupal3013 commented

Drupal 6, I like it and less problem than D7
Drupal 7 look good, but a lot problem,
In my Opinion D6 : 90/100 ; D7 : 50/100