Closed (fixed)
Project:
Relation
Version:
7.x-1.x-dev
Component:
Documentation
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
7 Dec 2011 at 12:49 UTC
Updated:
8 Mar 2012 at 18:15 UTC
After installing Relation I get incompatibility message on modules list with:
Chaos tools 7.x-1.0-rc1.
Can't turn Relation on.
Readme doesn't help with it. Project page neither.
Comments
Comment #1
macdee commentedYou need to use Chaos tools 7.x-1.x-dev. See the comment at http://drupal.org/node/1302788#comment-5237770
Comment #2
alexiswatson commentedI could've sworn this was on the project page at one point or another, perhaps one of the maintainers could update that. But yes, something should probably go in the README for now.
Comment #3
alexiswatson commentedChanging the title to more accurately reflect the issue at hand. This is the second issue in the past few days I've seen, which means there's probably several more who haven't said anything.
Comment #4
chx commentedI will remove ctools dependency.
Comment #5
ppc.coder commentedThe latest dev still requires "ctools (!=7.x-1.0-rc1)". Should I get the dev package or can I remove that dependency now?
Comment #6
jospBln commentedsubscribe
From drush:
Relation requires this module and version. Currently using Chaos tools version 1.0-rc1 (Currently using Unresolved[warning]
dependency Chaos tools (Version !=7.x-1.0-rc1 required))
Comment #7
alexiswatson commented@6: No need to post subscribe comments anymore; there's a follow button on the top-right of each issue now (see http://drupal.org/node/1306444).
Dependency still looks like it lives in the dev branch, though. Reopening.
Comment #8
naught101 commentedclosing in favour of #1361136: Roll back ctools dependency
Comment #9
alexiswatson commentedA bit confused by this being "won't fix," as it's clearly a documentation issue given the number of comments rolling in (as opposed to #1361136: Roll back ctools dependency, which resides in code). I realize that removing the ctools dependency for multiple load (and wrapping import/export functionality in module_exists(), etc) would render this moot, but does this mean the documentation couldn't be updated in the interim? And unless a new recommended release is slated for the very near future, the problem will remain in 7.x-1.x-beta3, anyway.
Not trying to be obnoxious; just trying to understand why this wouldn't be documented for the benefit of those trying to make use of Relation in the meantime.
Comment #10
Sahin commented@naught101, could you please edit the Readme and project page; it's only one sentence which will save wasted hours of the community. Then you can easily close this issue as fixed. Totally agree @davidwatson.
Comment #11
naught101 commentedBecause the documentation would then be irrelevant in a month or so, and would have to be changed again. There's no point. If you want this fixed quicker, feel free to post patches to #1361136: Roll back ctools dependency.
Comment #12
Sahin commentedIt's been a lot more than a month or so, and I sincerely can't see the reason why the maintainers are insisting not to write a description of a few words into the documentation. btw these are also suffering from this documentation hint:
Can't create a new relation type
Roll back ctools dependency
Call to undefined function ctools_export_crud_load_multiple() on line 453
Comment #13
chx commentedDo I need to lock this one as well? The ctools dependency has been rolled back.
Comment #14
Sahin commented"Don't lock me, please don't," said the poor little issue.
Brrr, how scary...
Comment #15
alexiswatson commentedNo reason we can't all be civil here... While I do respectfully (and strongly) disagree with the rationale behind not keeping the documentation up to date, there's no reason for anyone to engage in a revert war or be indignant about it, on either side. My hope is that by keeping the discussion constructive, such UX/DX concerns voiced by the community are given due consideration as this module matures.
chx, feel free to lock if that makes life easier. Cheers.