Posted by Wim Leers on August 10, 2011 at 9:04am
10 followers
Jump to:
| Project: | Drupal.org webmasters |
| Component: | Project/Git problem |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
In my Hierarchical Select module, some submodules have not yet been ported to Drupal 7. Hence, I've explicitly disabled them, by stating that in hierarchical_select/modules/hs_menu.info (as well as in another submodule).
In git, HS 7.x-3.x:
name = Hierarchical Select Menu
description = Use Hierarchical Select for menu parent selection.
dependencies[] = hierarchical_select
dependencies[] = menu
package = Form Elements
core = 6.xIn the tarball:
name = Hierarchical Select Menu
description = Use Hierarchical Select for menu parent selection.
dependencies[] = hierarchical_select
dependencies[] = menu
package = Form Elements
core = 6.x
; Information added by drupal.org packaging script on 2011-07-11
version = "7.x-3.0-alpha2"
core = "7.x"
project = "hierarchical_select"
datestamp = "1310423216"Hence, d.o's packaging scripts are to blame for the ability to enable the module.
The solution is simple: if a core = something line is detected in a .info file, don't override it.
Comments
#1
Subscribe, I have the same problem with http://drupal.org/project/userpoints_contrib
That project is a collection of separate but userpoints related modules, I haven't ported all of them yet, but I'm getting regular bug reports about them being broken.
Since the core = x.x is pretty much required, as you need it to be able to install the module from git, it would really make sense if this is supported.
#2
Another issue related to util module was raised against core #1730866: D7.14 allowed modules marked as "core = 6.x" to be enabled