By ghostbuck on

Hello,

I am a rookie Drupal Developer but have been working with PHP and LAMP for sometime. I have been using drush for awhile on my first drupal site and last night setup a few more sandbox sites on my test server. I noticed with downloading and enabling modules on my new sites, the modules do not show in the modules list. I get success confirmation from drush, I can see them by listing the directory, and the reports of the site show anonymous user enabled the module. If I disable and uninstall, that also shows in the reports and drush returns success command but again, nothing in the modules list. I have tried clearing the cache as well and simulating the same actions on a local virtual server through vbox (same results as my test server), nothing allows it to show when configured through drush on a site that was not my initial site. If I manually ftp the modules and decompress them through CLI, they show as expected. drush also continues to work as expected on my initial site though, I just cant use it for my others. I have read about site aliases but see nothing around aliases related to this. I am sure other people have experience this issue but I am unable to find their post on this forum or others. Can someone point me to some reading on this or educate me as to what I am doing wrong with drush?

Thanks.

⋅ Categories: Drupal 7.x

Comments

ghostbuck’s picture

ghostbuck commented

Just figured it out working on something else. The problem was selinux. When drush installs the module the file content type is set to user_tmp_t and not httpd_sys_content. The initial site I installed I did through ftping the drupal tarball and decompressing manually. The file type set using that method was correct, httpd_sys_content. It appears drush follows suite and will set the file types of new downloads as the same as the core files. So on my initial site, it would continue to work because the type was configured correctly. The new sites were not, drush did everything it was suppose to but selinux prevent apache from displaying it. For anyone who runs into this issue and is not familiar with selinux:

http://docs.fedoraproject.org/en-US/Fedora/13/html/Security-Enhanced_Lin...

That will show you how to check the type and change it.

bdimaggio’s picture

bdimaggio
he/him
Location Boston, MA
commented

Thanks, Ghostbuck. I've encountered the problem of selinux preventing modules from being recognized before, but I'd forgotten to check on it this time. Your follow-up post saved me from more hours of hair-tearing.