By aidanodr on

Hi Guys,

Im a recent user of Drupal. While I really like it, I am finding that most of the modules I require for my site are not yet upgraded to work under v4.7. Things like the Audio/ Playlist modules, Form, Survey Modules, and loads of others I have tried but not yet working with v4.7. Should I hang in there OR boldly downgrade to v4.6 for the moment? this based on it will probably take a while yet for alot of the modules to go 4.7. Am I being too pesimistic? What are the thoughts of those more experienced?

www.tidalsound.com/az

Cheers
Aidan

⋅ Categories: Drupal 4.7.x

Comments

erdemkose’s picture

erdemkose commented

We should wait for a while for all of the modules to be 4.7 compatible. I think it is worth it because 4.7 seems very good to me.

Ask module authors if they can rewrite their modules for 4.7
or
downgrade to 4.6
or
rewrite the modules you want for Drupal 4.7.

I would try to rewrite some small modules myself to learn how Drupal 4.7 works.

+Signature------------------------+
|____________erdemkose____________|
+---------------------------------+
liquidcms’s picture

liquidcms commented

ok.. here's my rant...

I have been trying to do a bit of work with 4.7: both setting up a 4.7 site as well as converting a couple modules over to 4.7... and my opinion is:

- 4.7 not yet ready for prime time

- many modules are not 4.7 ready; even some basic ones have bugs that didnt exist in 4.6
- there isn't even a list of module status to let you know where things are at - does drupal even have a project tracking module... mmm. most CMSes do?
- i think (because i have done a couple) there is a fair bit of work in converting many modules from 4.6 to 4.7 - which is why many haven't been converted yet
- and there a re things missing from the 4.6 to 4.7 conversion guide that are left up to converter to discover on his own

Modules i have had issues with related to 4.7:

- TinyMCE (some bugs in interface that worked in 4.6)
- i18N (not yet converted - I have done some, as has developer, but on hold till 4.7 stable - quote from developer)
- tellafriend (it works now cuz i converted it) but not sure developer has release my changes
- categories - well this is only available for 4.7 but i think there are still bugs (this was one of main reasons i wanted to use 4.7)

and i think a couple others as well

BUT!!!

that all being said.. 4.7 has a lot of nice new features... i think main draw back to using it at this point is simply module support.. soon... wait for Beta11 ... lol... jk..

Peter Lindstrom
LiquidCMS - Content Solution Experts

liquidcms’s picture

liquidcms commented

and i guess i missed my summary...

i am setting a new site of my own.. and i am using 4.7 because i need to figure out what is usable and what isn't..

but for the couple new sites i am doing for clients... i stick to 4.6

Peter Lindstrom
LiquidCMS - Content Solution Experts

TurboChef’s picture

TurboChef commented

I'm putting together a corporate intranet for my company, and I really want the new stuff in 4.7, but I really want all the interesting modules too... It's a tough call sometimes.

I also don't want things to get dicey if I launch this site with pre-final code, but I think 4.7 is "final" enough that you can at least work with it in a sandbox environment.

I'm going to take the latest CVS version (I'd take that over beta4), install it with a collection of modules, and play with it for a week. If nothing serious breaks, then I'll stick with 4.7 and upgrade to final when it's done. If not, I'll backtrack to 4.6.5 and not lose alot of sleep over it.

Just my $0.02,

John @ TurboChef

Zen’s picture

Zen commented

Best thing for you guys to do is to make sure that you request (by submitting an issue) the module owner to upgrade to 4.7. The more there are who request it, the more likely it will be that the maintainer will do something about it.

-K

heine’s picture

heine commented

For some module developers 4.7 feels like a moving target (and it is in a way). Many maintainers will update when a stable RC is available.

You can of course submit a feature request. Make sure to only submit one issue though, or you'll annoy the hell out of the maintainer (and that certainly won't help).

Submitting patches to update a module is (nearly) always encouraged of course.

--
Tips for posting to the forums.
When your problem is solved, please post a follow-up to the thread you started.

jbrauer’s picture

jbrauer commented

If you're dependent upon module X that isn't (yet) available for 4.7 it pays to check the CVS for that module. On more than one occasion I've found that the module is either working or close to working with 4.7 but hasn't yet been "released" as a 4.7 module pending either bug fixes or awaiting a 4.7 RC.

------------------------------
Adding Understanding

--