Downloaded modules not showing up
noxel - May 26, 2007 - 19:30
I uploaded the ecommerce and token module folder into sites/all/modules, but i can't enable them in the site building -> modules list, as they are not there.
Can anyone help me out? :S What am i doing wrong?
Thanks
Wrong spot
put 'em in the /modules subdirectory of your drupal directory
Nope.
The recommended location for contributed modules in Drupal 5.x is sites/all/modules.
If the modules are not showing up, something else must be wrong --for example, the wrong versions of the modules. Drupal 5.x expects to find 5.x modules with .info files.
My bad!
It works, but I will look at that. Thanks!
A matter of permissions
Don't put the files into the /drupal/modules folder. They belong inside /drupal/sites/all/modules/.
I encountered this same exact problem too and after some tinkering with permissions settings, I found out that you must enable execute permissions on the /drupal/sites/all/modules folder. Once I changed the permissions for the modules folder, the modules were displayed inside Drupal Admin.
chmod -R 755 sites/all/modules
I seem to have the same
I seem to have the same issue. In the past I've just put the modules in the drupal/modules directory and it worked. I just did a fresh in stall of FC 7 and installed Drupal. I'm not sure if it is a known issue but I do have SELinux enabled.
I added a couple of modules I've used in the past and they would not display. I added a few more just to rule out there being a problem with the modules in question. I then searched the Drupal forums and found this post. I followed the above mentioned suggestions (moving the modules to sites/all/modules and setting th permissions to 755). I'm still not having any luck.
Does any one have any idea what the issue may be?
Ditto that
I'm having the same problem. I've tried putting modules in /modules, /sites/all/modules and /sites/default/modules, and they won't show up in the modules listing. Also tried resetting the cache, different modules - the works
Run Cron
had the same problem. run you cron and it will work.
Not working
I have followed the above and it is still not working.
Not sure what to do
I have tested this on three
I have tested this on three different drupal installations with this module http://drupal.org/project/pngfix
The accessrights were originally different from other modules in my /modules.
- Changing accessrights did not help
- Running cron did not help
- Reinstallation did not help
Modules NOT showing for me either...
I am having the same problem with trying to get downloaded modules to show up.
I am using XP/sp1. I installed Drupal 6-6 per intructions. I have the latest Xampp installed with the latest Apache, MySql, Filezilla and Mercury.
I have installed the downloaded modules in C:\xampp\htdocs\drupal-6.6\sites\all\modules. The downloaded modules which I cannot see in admin > site building > modules are the following:
cssedit 6.x-1.x-dev
e-card 6.x-1
footermap 6.x-1.2
i18n-6.x-1
language icons 6.x-1.0
simplenews 6.x-1.0-beta5
translation overview 6.x-1.0
views 6.x-2.1
views slideshow 6.x-1.0-beta
wp comments 6.x-1.0
I am using a Zen theme I customized with the Starter Kit. I tried switching over to Garland, but... still no joy. I have run cron, restarted, cleared the cache, even offered up a glass of wine sacrifice to the BOfH. (Sadly, since it is just me here, and I'm a chef not a programmer, I had to drink it.)
I have read ALL the relevant posts regarding this issue, which SEEMS to be fairly common, however... beyond the suggestions of suggesting the modules are placed in sites\all\modules (already there) or suggesting write permissions need to be granted (this isn't Unix) I cannot find anything that suggests how to fix this.
Help please? How am I screwing up?
=-=
ensure the folders you created at sites/all have the correct permissions.
Silly error
I had the same problem, non-standard themes weren't showing up either. Permissions all matched my other sites, 755. Finally figured out that I had dropped the standard drupal theme directory into /sites/all/themes. After I deleted it and uploaded custom themes, modules started working as well.
Loving and living.
Ironically I had the same problems exactly
***EDIT- "I didn't realize that this was in the Drupal 5.x I am actually only running 6.x so if this doesn't apply to you then you can kindly skip it. Hope it helps someone though..."
Funny I had this very same issue. Tried all the suggestions including changing file permissions on ftp.
Still to no avail, until at least the moment I re-read it all including the README.txt that is in the directory at /sites/all/
It reads and I quote quite simply;
"// $Id: README.txt,v 1.3 2006/12/23 15:35:51 dries Exp $
This directory should be used to place downloaded and custom modules
and themes which are common to all sites. This will allow you to
more easily update Drupal core files. These modules and themes should
be placed in subdirectories called modules and themes as follows:
sites/all/modules
sites/all/themes
MY Mistake was simply the Lower/Uppercase distinction in the /Modules and /Themes directory that are required to be completely lowercase. /sites/all/modules and /sites/all/themes
Funny I didn't remember having this problem on other installations. Good to go now! Hope it helps folks.
Be specific right down to capitalization...
-Just when you think you got it...
Fantastico the Culprit
I also had problems with modules not showing up, even after all of the above. Themes in tld/sites/all/themes worked fine but modules in tld/sites/all/modules would not show up. Placing the modules in tld/modules worked. This was with a Drupal 6.x installed via Fantastico via a host's Cpanel. Doing a fresh, manual install of Drupal did not have this problem and all works fine now. It is not the first time Fantastico's drupal install has messed me around, previously mixing table field colation types there by also rendering some modules unusable until all colations were matched up.
If you're using Fantastico to do the install and having problems, I suggest testing a manual Drupal install.
_
Yet another post on why drupal should never be installed with an installer.
_
Don't be a Help Vampire - read and abide the forum guidelines.
If you find my assistance useful, please pay it forward to your fellow drupalers.
=-=
a 3rd party installer. Using drupals native installer is best :)
I knew what you meant but felt a need to clarify for the newcomers who tend to learn this lesson far too late.
For the those who tend to use 3rd party installers:
3rd party installers like fantastico or some other provided by hosts are great for testing scripts and allowing you to quickly install. However once a decision is made on which script you want to use there are far fewer headaches when you install the script on its own. Beyond that you know by doing so that you are using the same exact system as the bulk of the people you are asking questions of. using a 3rd party installer adds a nuance that most won't be exposed to.
_
Thanks VM! Now the I see it, what I wrote makes no sense, lol. (edit: now with more english)
EDIT: ooohh... signatures are back. Can't wait for the link spam to start rolling in.
_
Don't be a Help Vampire - read and abide the forum guidelines.
If you find my assistance useful, please pay it forward to your fellow drupalers.
=-=
: ) to both.
If you're developing
Recently started learning Drupal development (again). The drupal handbook states, in reference to the .info file for a module: "... This file is required for the system to recognize the presence of a module..." After creating a .info file, my module would not show up on the module list page (Administer->Site Building->Modules). After searching the net for a few hours, and finally arriving at this post; and after trying all the suggestions here (755 permissions, re-installation, the works), I decided to create an empty .module file. One refresh later, I was smiling - it worked!
By the way this is a note for Drupal 6.x - am not sure if it applies to Drupal 5.x as well. I am using Drupal 6.14. I have only posted it here because this is what turned up when I search for "module not showing up.."