Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
the .info files should have a line to list modules with which the module conflicts with. that way if you have two modules that perform the same function and step on one another, they could be marked that way. The module admin page could tell you that you are enabling conflicting modules, and of course tell you that they conflict before you enable them.
Comments
Comment #1
simesorry, 5.0 is closed for feature requests
Comment #2
coreb CreditAttribution: coreb commentedmoving from x.y.z to 6.x-dev version queue
Comment #3
fax8 CreditAttribution: fax8 commented+1 for this. I would use if available in my video module.
Fabio Varesano
Comment #4
suydam CreditAttribution: suydam commentedWhat ever came of this? I'm working on a pricing level module that directly conflicts with Role Discounts. I'd love to be able to say that in my .info file.
Comment #5
ntroutman CreditAttribution: ntroutman commentedI would like this functionality to, mainly to prevent namespace conflicts.
Comment #6
xolotl CreditAttribution: xolotl commented+1 For example, the 5.x cck date field conflicts with the 5.x event module, with this feature, one could be prevented from installing the cck date module until the event module was disabled.
Comment #7
ugerhard CreditAttribution: ugerhard commentedComment #8
lilou CreditAttribution: lilou commentedMark #108458: Implement a system of module conflict detection as a duplicate of this issue.
See also : #211747: Allow specifying version information as part of module dependencies
Comment #9
fgmMarked #170424: .info file should support negative dependencies as a duplicate of this issue.
Comment #10
fgmWhile we're at the "dependencies feature" stage, it would also be nice to have a way to indicate when a module does not actually "need" an other module, but has added features when it is present. This would remove a burden from contrib module devs who need to add specific code for this to their module, while a core mechanism could allow refactoring all this contrib-specific code to just one standard way of having such optional dependencies expressed.
Comment #11
babbage CreditAttribution: babbage commentedSubscribing.
Comment #12
Dave ReidSee also #328932: Modules and partial dependencies - enhances[] and enhancedby[] field in modules' .info.yml files.
Comment #13
doq CreditAttribution: doq commentedSubscribing.
Comment #14
voxpelli CreditAttribution: voxpelli commentedAdded a patch to the issue mentioned in #12, #328932-66: Modules and partial dependencies - enhances[] and enhancedby[] field in modules' .info.yml files, which could be built upon to solve this issue. If that issue develops in the direction of my patches then this issue perhaps should be postponed until that issue has been solved.
Comment #15
sun.core CreditAttribution: sun.core commentedComment #16
shadcn CreditAttribution: shadcn commentedsubscribing
I think modules like admin_menu vs toolbar would benefit from this implementation
Comment #17
lpalgarvio CreditAttribution: lpalgarvio commentedwe need these:
* conflicts[] - module(s) that can NOT be enabled when enabling this module (ERROR)
* breaks[] - module(s) that will NOT work after enabling this module (WARNING)
* brokenby[] - module(s) that will make this module NOT work after being enabled (WARNING)
see:
#328932-153: Modules and partial dependencies - enhances[] and enhancedby[] field in modules' .info.yml files
#328932-139: Modules and partial dependencies - enhances[] and enhancedby[] field in modules' .info.yml files
#328932: Modules and partial dependencies - enhances[] and enhancedby[] field in modules' .info.yml files
Comment #18
lpalgarvio CreditAttribution: lpalgarvio commentedComment #19
lpalgarvio CreditAttribution: lpalgarvio commentedactually, we should use brokenby[] instead of breakedby[].
english lessons reminded me of broke/broken and simple past and past participle, so i read a bit to make sure:
http://en.wiktionary.org/wiki/break
http://en.wiktionary.org/wiki/breaks
http://en.wiktionary.org/wiki/broke
http://en.wiktionary.org/wiki/broken
http://en.wiktionary.org/wiki/enhance
http://en.wiktionary.org/wiki/replace
Comment #20
cafuego CreditAttribution: cafuego commentedThis has been open for half a decade and seems very useful. Can we get this into D8?
Comment #21
Andre-Bmaybe d9 it will be :(
Comment #22
DarrellDuane CreditAttribution: DarrellDuane commentedI think this is a better solution, and it could be implemented for d7 now, maybe even d6:
https://www.drupal.org/node/2478351
I am thinking it would be a very nice feature for each project listed on Drupal.org to have the ability to add a list of other projects that the given project conflicts with. This is a new solution to the problem noted above.
By maintaining this information on Drupal.org, rather than in .info files we can better track issues and allow Drupal Core to get the latest updates about problems and fixes to problems related to conflicts with another project/module. I know that there could be some themes that have conflicts with modules.
One way to do this would be to add another field on the issue tracker for the listing of a conflicting project. From here, details about what the bug is and whether its something that can be fixed, and a level of severity would be good to have. Another way to do it is to have an entirely new field for the project to add conflicting projects, and at that time also add any issues that have more details about the conflict. I'd suggest the former. If we do the former, I expect we will have some issued as won't fix.
It would be nice to get a quick report of conflicts with other projects, such that we might quickly identify other modules with similar functionality.
It would be nice to make an API to read this data from Drupal.org so that when someone enables two modules that conflict, a message can appear on the module page or elsewhere notifying the administrator and allowing them to quickly research the concern.
Thanks for your consideration, let me know how I can help with this.
Comment #23
fgmAs an interesting side effect of maintaining the info on d.o. instead of within each project, the info could be included in releases packaged by the distribution system, like other extensions to the *.info[.yml] files.
Comment #24
lpalgarvio CreditAttribution: lpalgarvio commentedComment #25
sime*cough* composer *cough*
Comment #26
ajay_reddyIs there any way to add conflicts in D8 .info.yml as like in D7. If any helpful links post it here or in this issue queue.
Comment #30
geek-merlinComment #34
slefevre@ccad.edu CreditAttribution: slefevre@ccad.edu commentedThis would be a very useful feature to have. Here's an issue thread for unpublished_node_permission, where a user notes that, within the thread, two modules are known to conflict with unpublished_node_permission (content_access and advanced_access).
Having a `conflicts` line would prevent waste of developers' time and creation of extraneous issues.