Hi All,
After a lengthy read of content on drupal.org, I bit the bullet and upgraded on of my older installs 4.6.5 to the latest 4.7 (4.7.4) While I was happy with the success of the upgrade, I am a bit concerned at how my use of non core modules has affected the site. For example in my 4.6.5 install I had modules such as aggregator2, aggregator2_autotaxonomy, aggregator2_logo, ajax, buddylist, dba, flexinode, news_page just to name a few. Now I find myself having trouble determining just how to regain functionality. This is not a complaint, nor is it a lazy approach to getting help upgrading my modules, rather I would think that it might be a good snapshot of the challenges that the current upgrade system pose to the average drupal user who might not be a programmer or who might be at the edge of the skillset with implementing modules and over their head in trying to figure out a good way to bring modules up to date, and keep them that way.
So with that all my drupal sites are 4.7.x or better and most wont have this issue. Might it be a good idea to have the Modules administration page list not only the module and its enabled/disbled status but to list its version number and perhaps a link to its upgradepath/home on drupal.org? At any rate, I dont post here often but since I am here I just want to add that Drupal is the best choice for me and my customers and I love the directions we are going with drupal. To all the people who make my websites rock, thank you so much....
Franco Nogarin
Comments
the approach to take, would
the approach to take, would be to upgrade and update all of your drupal 4.6 modules with with 4.7 versions that are attached to the projects page. Most of the modules that worked with 4.6 have been upgraded to work with the core of 4.7 provided the 4.7 version of the module is installed and enabled.