Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Here is a followup for issue: https://drupal.org/node/2067229
Patch is on its way.
Comment | File | Size | Author |
---|---|---|---|
#7 | 2081579-7-libraries-search-paths-alter.patch | 624 bytes | emarchak |
#2 | base_profile-2081579.patch | 698 bytes | umtj |
#1 | base_profile-2081579-1.patch | 670 bytes | umtj |
Comments
Comment #1
umtj CreditAttribution: umtj commentedComment #2
umtj CreditAttribution: umtj commentedPath corrected, sorry.
Comment #3
tstoecklerI'd surely love to add this feature. But I don't see much value in adding this until the Drupal core issue is in. So marking postponed, unless you can make a compelling case :-).
Comment #4
david.lukac CreditAttribution: david.lukac as a volunteer commentedDefinitely +1 for this one. We work with install profiles most of the time and having modules support 'base' profiles would be a great advantage.
Comment #5
tstoecklerSo I don't see this getting into core in any way, so closing this one.
What I would be open to is the following: If someone is able to implement this functionality as a *module* (no idea if that possible, but just assuming that it is for now), then I would totally be fine doing a
module_exists()
check inlibraries_get_libraries()
in order to support base profiles. If that happens, please do re-open this issue.I really think base profiles are a pretty cool feature and I would love to have them in core, but that's not something I can control, and since they currently aren't I don't think it makes sense for Libraries API to be "forward-supporting" of some very distant core feature.
Comment #6
tstoecklerMarked #2733787: Allow install profiles include libraries from their base profile as duplicate.
Comment #7
emarchak CreditAttribution: emarchak at Myplanet commentedRe-posting the patch from https://www.drupal.org/node/2733787 in case someone else is looking for a patch that isn't three years old.
Comment #8
scott shipman CreditAttribution: scott shipman as a volunteer commented@tstoeckler , I can understand your hesitation for this proposed patch, when viewed myopically from the perspective of the drupal core lack of progress on sub profiling. But this patch has wider reaching capabilities - such as allowing a developer to provide custom library locations via a hook, for any reason. It could also help to clear a way for a resolution on the sub-profiling issues in drupal core.
Its non-destructive, backwards compatible and trivial in processing costs. I vote to include it.
Comment #9
emarchak CreditAttribution: emarchak at Myplanet commented@tstoeckler, if we want to make progress on the
module_exists
approach, should we reopen this issue or create a new one?