By kiwibytes on
This is what I learned after trying for 2 weeks to create a website with specific features, something I can do in 2-3 days using Drupal 6.
First, most modules are in "dev" state and need special configurations not mentioned in any documents to make them work. Then there are some simple features in Drupal 6 (like embedding Youtube videos) that are not available in Drupal 7. If you are thinking Media Youtube is the module for that, try making it work and you will know.
Oh yes you can definitely make a text-only blog with Drupal 7 :)
Comments
D7 ready?
Thank you for your assessment on D7. I am trying to figure out whether or not to go D7 for a new client's site. I think I'll go with D6 and review D7 feasibility for a client site in a couple of months.
Thanks again,
-Frederico Garza
I like the core features and
I like the core features and many of the best mods are built in.
Since I am relatively new, I figure D7 is the place to start.
You're right, it isn't ready
You're right, it isn't ready for production for point-and-click users, in many scenarios. But I do know people who are building and deploying D7 sites already and with success. But since it is newly released, it requires that you are a little more capable of doing things your own way.
I've been wondering about
I've been wondering about this. I'm on the verge of building a pretty big site with some fairly common functionality (business directory) but almost every module I want to use is in dev or alpha.
So for me it's going to be D6 and try as hard as I can to keep a clear upgrade path. Thanks for the post.
Not ready for Prime Time Time
I am a newbee and have only tried Joomla and a few others. I simply loaded them to see what they could do. Last fall and found that Drupal 6 was the CMS for me and when D7 comes out it will be that much better. I decided to wait until Late Feb 2011 so I could use D7. I am now thinking that my wait was for naught. I think I'm going to use D6 because, from the comments, D7 is Not Ready For Prime Time.
it really depends on the
it really depends on the requirements...for example for building slideshows you're not bound to views and views_slideshow. there is also field_slideshow which makes building slideshows even simpler. But, for a lot of tasks you will need to have views working. since it is still in dev you will run into a lot of problems.
Another no-go for d7 is that token (required by path_auto) does not yet support term_path/menu_path (see: http://drupal.org/node/860082).
So, in most cases, unfortunately, you will have to stick to d6.
Newbie to Drupal
I am very much a newbie to Drupal. Having used CMS' like Joomla and Zikula. While I liked both, Joomla is getting a little complicated with how things are done in admin and Zikula has nowhere neat the addon's they use to have pack when they were PostNuke.
I am really liking Drupal but have found that D7 doesn't have many modules available as of yet either. So I guess I will need to go to D6 for now. The information in this post was very helpful and I just wanted to say thank you. :-)
Yes... maybe
Yes, I remember that I've thinked the same thing upgrading from D4 to D5, from D5 to D6 and now that I've a clear install of D7 to start developing something with it. It's only a matter of time :) as always. But the text only blog I've seen, it's a very powerful one! Some of the core modules in D7 are just great (CCK in core for example). We just have to wait and to contribute with our experiences.
And I'm still using D6 for my sites :)
Ace
Before Deciding on D7
If you're plans include a lot of ajax, I highly recommend doing many test cases before deciding on D7.
Use New Version 7 for New Drupal Site.
I just went through an incredibly painful migration in moving an established site from Moodle 1.9 to Moodle 2.02 where many of the truly wonderful improvements required that I move much of the content little chunk by little chunk. I am newish (first year) to Drupal and I have just launched a new Drupal site. I love the greater simplicity and ease of implementation of Drupal version 7 over version 6. I decided that I would rather begin the learning curve of Drupal 7 now than climb Drupal 6 now, then learn the differences of Drupal 7 later, and then also later struggle with the inevitable pains of migrating my new site from Drupal 6 to Drupal 7. I plan to grow with Drupal 7 as the Drupal community migrates the "rest of the best" of Drupal 6 into Drupal 7. It is a different calculus for those with established production sites; there it does seem to make sense to plan migration for "later" when many of the initial wrinkles have been ironed out.