I have run and upgrade from 6.x-2.7 and a clean install of 6.x.2.8 and with both of them the majority of Commons modules have a cross against them with a message saying "This version is incompatible with the 6.26 version of Drupal core."

CommentFileSizeAuthor
#1 Errors with this drupal version185.43 KBfabianderijk
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

fabianderijk’s picture

I've got the same issue. Please fix!

ezra-g’s picture

Thanks for the bug report - I'm looking into this.

ezra-g’s picture

Assigned: Unassigned » ezra-g
ezra-g’s picture

Looks like 6.x-2.8 was packaged with the D7 branch of Views content cache module and that this is the underlying cause of this message. See the core bug #224643: Confusing message about incompatibility of a module for why that message is displayed.

I'm working on a new release to correct this. In the meantime, you can replace views_content_cache module with the latest 2.x dev.

ezra-g’s picture

Status: Active » Fixed

Commons 6.x-2.9 can now be downloaded http://network.acquia.com/downloads/drupal-commons .

Apologies for the error - Please let us know if you have any further issues with the latest release.

Andrew Searl’s picture

Thanks for the update. I am concerned that there are several modules running -dev versions, some of which were not present in 2.7.
Here is a list: Activity Log 6.x-2.0-beta1+60-dev (2012-Jul-13), Activity Log Email Digests 6.x-1.0+1-dev (2012-Jul-13), Ajax Load 6.x-1.3+5-dev (2012-Jul-13), Diff 6.x-2.3+1-dev (2012-Jul-13), Facebook-style Micropublisher 6.x-2.0+6-dev (2012-Jul-13), User Points Contributed modules 6.x-1.0-beta1+3-dev (2012-Jul-13), User Relationships 6.x-1.3+2-dev (2012-Jul-13), Views attach 6.x-2.2+8-dev (2012-Jul-13), Views content cache 35940a5de7e91782ec4363e8cd9bb0b5adfc50eb, Voting API 6.x-2.3+9-dev (2012-Jul-13), Wysiwyg 6.x-2.3+9-dev (2012-Jul-13)

ezra-g’s picture

Those modules are mostly the same versions as in previous releases of Commons - With Commons 2.8 and 2.9 we packaged the release using Drush 5, which provides more specific information about dev releases. For comparison, here , see the Drush make script for Commons 2.7..

Our goal is certainly to have all official releases of contributed modules. Commons 6.x is built on a large number of contributed modules, some of which have had signifigant development activity since their most recent official releases. In these cases, I've filed issues in the respective contributed module issue queues suggesting that a new release be rolled, and even volunteering to help with that process.

My goal for the 7.x-3.x version of Commons is to more carefully chose modules that are and seem likely to remain active in maintenance, and to avoid unnecessary contrib dependencies where possible.

Andrew Searl’s picture

Thanks for the clarification, much appreciated.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.