Name:
module_install
Description:
Small but handy module that adds the ability to install a new module directly into a subfolder of sites/all/modules (contrib/custom/patched)
As far as I've searched, this functionality does not exist yet, so no other modules compare. It makes it a few steps faster to install modules during development and keeps your modules folder organized.
Project page:
http://drupal.org/sandbox/kriboogh/1962208
Sandbox git:
git clone --branch 7.x-1.x http://git.drupal.org/sandbox/kriboogh/1962208.git module_install
cd module_install
Drupal core:
7.x
Reviews of other projects:
- http://drupal.org/node/1987552#comment-7380694
- http://drupal.org/node/1909634#comment-7381094
- http://drupal.org/node/1266460#comment-7381606
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | 2013-04-05 23_39_23-Update manager _ localhost.jpg | 34.97 KB | d34dman |
Comments
Comment #1
dimitrov.adrian commentedLooks good. But I think that you should give ability to users manage the directories to install. Currently you have hardcoded
May be settings for edit them, or using alter hook will be good.
Comment #2
PA robot commentedWe are currently quite busy with all the project applications and we prefer projects with a review bonus. Please help reviewing and we will take a look at your project right away :-)
Also, you should get your friends, colleagues or other community members involved to review this application. Let them go through the review checklist and post a comment that sets this issue to "needs work" (they found some problems with the project) or "reviewed & tested by the community" (they found no major flaws).
I'm a robot and this is an automated message from Project Applications Scraper.
Comment #3
d34dman commentedHi,
The git link on project application page is your private link. Please tick the check box for non-maintainers and refresh the page to get the git commands that others can use.
I tried to install a module on my localhost into a contrib folder. But was met with an error. Seems more like some issue with my local setup.
Comment #3.0
d34dman commentedAdded project sandbox page link
Comment #4
kriboogh commented@dimitrov.adrian Thanks for the suggestion. I changed the code a bit, so it will list all non-module 1st level subfolders of sites/all/modules, sites//modules and module folders in profiles. This way no extra admin page is needed, you can just create the folders and be done.
@DD34dMan: The error seems to be some permission settings on your contrib folder, make sure it has the same rights and owner as your normal modules folder. Also check if you can upload a module without this module_install module, do you get the same error?
Thank you for reviewing my module.
I changed the git link as suggested.
Comment #5
dimitrov.adrian commentedSeem to be good now, but please note that features module use sites/all/modules/features for itself, so IMO will be good idea to exclude the 'features' subdir (just idea)
Comment #6
kriboogh commentedUpdated the code so features folder is excluded. I added two hooks so one can extend the list of excluded or included directories. I think with the suggestions you made it definitely is more flexible than before, thanks. I also want to avoid having extra admin settings for such a small module. It would just clutter up the admin menus. The idea was to just install and forget about it.
Comment #7
dimitrov.adrian commentedSeems to be a flexible, good and useful module now. Yea, you're right about the setting page.
Also I notice that module actually need from update_manager module to get working. I suggest you to add it as dependancie in the .info module_install.info
Comment #8
kriboogh commentedI updated the info file as requested.
Comment #9
kriboogh commentedComment #10
PA robot commentedThere are some errors reported by automated review tools, did you already check them? See http://ventral.org/pareview/httpgitdrupalorgsandboxkriboogh1962208git
I'm a robot and this is an automated message from Project Applications Scraper.
Comment #11
kriboogh commentedFixed coding style warnings.
Comment #12
kriboogh commentedso what's the next step in this process?
Comment #13
musicalvegan0 commented@kriboogh You'll need to participate in the Bonus Review program. You can get all the details you need from this post: http://drupal.org/node/1962318#comment-7262290
While the PA Robot suggests that approval of this project application will happen whether or not you participate in the review program, for all practical purposes, this project might not be approved for a very long time if you don't participate. Good luck!
Comment #14
musicalvegan0 commentedUpdating the status to needs work.
Comment #15
klausi@musicalvegan0: please set issues only to "needs work" if you did an actual review and found application blockers.
Comment #16
musicalvegan0 commented@klausi Sorry about that. Thanks for letting me know.
Comment #17
erez111 commentedHi,
Nice module.
However, please do following:
1. Seperate not-hook functions from "module_install.module".
Functions such as "_module_install_get_search_directories", "_module_install_get_destination_directories" should be in a different file.
2. There are at least 2 external files that load for each page. You can try to make files load only in dedicated page. e.g.: admin/modules/%
Good luck :)
Comment #18
kriboogh commentedThanks erez111.
I took your advice, and made a dedicated file for the internal functions. Also took out a bug which was caused by the sort function (had to use asort). File now also only load when needed.
I'll take a look at some other modules and enter the bonus program.
Comment #18.0
kriboogh commentedchanged the link to non maintainers
Comment #18.1
kriboogh commentedadded a review link
Comment #18.2
kriboogh commentedadded review link
Comment #19
kriboogh commentedadded PAReview: review bonustag
Comment #20
klausimanual review:
Although you should definitively fix those issues they don't seem to be critical application blockers, so I guess this is RTBC. Removing review bonus tag, you can add it again if you have done another 3 reviews of other projects.
Assigning to cweagans as he might have time to take a final look at this.
Comment #21
cweagansThanks for your contribution, kriboogh!
I updated your account to let you promote this to a full project and also create new projects as either a sandbox or a "full" project.
Here are some recommended readings to help with excellent maintainership:
You can find lots more contributors chatting on IRC in #drupal-contribute. So, come hang out and get involved!
Thanks, also, for your patience with the review process. Anyone is welcome to participate in the review process. Please consider reviewing other projects that are pending review. I encourage you to learn more about that process and join the group of reviewers.
Thanks to the dedicated reviewer(s) as well.
Comment #22
kriboogh commentedThank you guys. I also implemented the suggestions by klausi.
The module is now available as a full project.
Should I set this to closed or is this done automatically?
Comment #23
cweagansWhen issues are done, mark them as fixed. If there's no further activity for two weeks, they'll automatically be closed.
Thanks!
Comment #24.0
(not verified) commentedadded review link