Closed (won't fix)
Project:
Category
Version:
master
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
7 Feb 2007 at 02:00 UTC
Updated:
3 Nov 2011 at 15:24 UTC
I ask myself, "Why are we messing around with replacing module files anyway?" (regarding the wrappers)
Why not just change the filename in the system table for taxonomy and book?
Comments
Comment #1
Jaza commentedThis is something that I'd like to see happen, but that I've never really bothered to look into a great deal. IIRC, people have experimented with this in the past, and have had mixed results. See these past threads:
http://drupal.org/node/66897
http://drupal.org/node/105859
I'm all for a solution that eliminates the need for the '.copyme' files, and the messing with original copies of core modules. But remember that the current solution works (for most setups - it's problematic with some complex multisite setups). And a new solution needs to be tested to make sure that it also works.
E.g. we'd need to check that when you re-save or re-load the 'admin/build/modules' page, Drupal doesn't rewrite its module paths and ignore the wrapper modules.
Comment #2
bdragon commentedDrupal 5 actually will *automatically* override modules...
http://api.drupal.org/api/5/function/module_rebuild_cache
http://api.drupal.org/api/5/function/drupal_system_listing
I just renamed the wrapper module and info files *in place,* and when I visited the module admin page, it picked them up and used *their* info files automatically!
So that kinda changes the problem from how to enable them to how to disable them. ;-)
Comment #3
bdragon commentedHmm, it doesn't make it possible to do wrappers without having to copy files, but it does make it possible to do wrappers without having to copy files outside of the wrapper directory!
Simply rename the wrappers in-place.
This would fix the multi-site problems easily.
Of course, Drupal 4.7's very likely to be not as helpful here.
Comment #4
bdragon commentedOr maybe not. It appears 4.7's mechanism also does this.
This system of course assumes people are installing their modules in sites/* and not directly in modules/* (which is a bad idea, especially now that we have sites/all to use.)
Comment #5
bdragon commented