By ahashim on

Well,
After using Drupal for more than 2 weeks. i'd like to thank all contributers. Really it is more than gr8.
But i have a question.
Why the modules should use specific version?
for example module "Admin block" is for 4.5.0 and can not work with 4.6.2
why?
in my point of view the new version must support the old version. This cause a lost of efforts, prevent scalability.
In java programming the old java programs with java 1.1 still working with the last JDK 1.5 but the JDK till you that you are using a deprecated API, so try to use the latest API.
Can it be done in drupal?
Thank you.

Comments

micha_1977’s picture

micha_1977 commented

imho drupal is not an API but a framework
and if you change a framework, its not always possible to get old functions working with the new one..

-micha
work in progress with Drupal 4.6: langmi.de

Zen’s picture

Zen commented

Drupal releases seem to come with most important modules already converted over. The rest can be (or already are being) converted using guides like this one.

Either way, I'd much prefer to have a lean, mean and clean Drupal running on my server than one that's got bits and pieces sticking out :)

Hope that helps :)
-K

--------
Quillem.com

Steven’s picture

Steven commented

But of course, we think changing APIs is necessary in many cases. This has been discussed over and over again. Drupal is a moving target. We rewire the insides constantly. If you don't like it, stick to a single version, but don't complain if you miss out on new features.

--
If you have a problem, please search before posting a question.