By sabbat on

I have to begin a new big poryect and i will use Drupal how support CORE. I love some features of 4.7. But I haven´t developer knowledges.

I will put in charge the proyect to a freelancer.. My doubt is if I have ask he for use 4.7 or is more safe use 4.6?

I need basically:
-PHPTemplate engine
-folksonomyes and tags categories
-submission queue promote
-ajax

⋅ Categories: Drupal 4.6.x, Drupal 4.7.x

Comments

dreed47’s picture

dreed47 commented

IMO your biggest risk is with contributed modules. Some have started to convert to 4.7 but it will take some time for all the maintainers to get them converted (and some may never convert). If you can stay pretty close to core drupal it may be worth the risk but if not then you're probably better off going with 4.6.3.

my 2 cents....

budda’s picture

budda
Primary language English
Location Cheshire
commented

Sabbat, I'm working on a site using HEAD/4.7 at the moment, the forms API has settled much now so things are good.

I've not had any major problems and free tagging works fine.

You should enable your contact capabilities on your drupal.org profile too ;-)

Sounds like you're doing a digg.com clone project :-p

--
www.bargainspy.co.uk | More Drupal modules

--
Ixis (UK): Drupal support, Drupal hosting.

sabbat’s picture

sabbat commented

Sure i do it ;) also I send you a contact mail

regards

----
si te aburres ya sabes
www.aburridos.info

Jaza’s picture

Jaza commented

All the four features that you listed as being needed are available for 4.6 in some shape or form:

  1. PHPTemplate engine for 4.6 (just download and install)
  2. Free tagging patch for 4.6 (requires some technical knowledge - make sure you back up before applying patch)
  3. Submission queue promote: not sure what you mean by this - the queue module is included in 4.6 core (but will not be in 4.7 core, is moving to contrib)
  4. Ajax: no 4.6 patch is currently available for the various AJAX developments, AFAIK (i.e. textfield autocomplete, upload progressbar, collapsible fieldsets). But the main addition is the actual JavaScript files, which can easily be imported - and a patch wouldn't be too hard to generate for the rest.

I would recommend sticking with Drupal 4.6 if your project demands stability over features. Drupal HEAD currently has quite a lot of bugs (some of them critical) that need to be fixed before 4.7 is ready. As a code freeze is not yet in place, there may even be changes to the functionality before 4.7 comes out (though this becomes less likely as release gets closer). I would seriously discourage using Drupal HEAD/4.7 for a live project, AT LEAST until 4.7RC (Release Candidate) is ready.

Jeremy Epstein - GreenAsh

Jeremy Epstein - GreenAsh

sami_k’s picture

sami_k commented

I would say other than the 4.7 specfic features, you will miss out on all the features that contributed modules provide, many of which will not be updated immediate... Some will never be updated but that's another story ;)
--
Please read the handbook, search the forums, then ask...
http://drupal.etopian.net (Drupal Support) | http://www.drupalshowcase.com

Wesley Tanaka’s picture

Wesley Tanaka commented

I'm running 4.7 here:

http://treehouse.ofb.net/go

but it's patched up to fix problems that it comes with out of the box.