By Charles-2 on
I've downloaded Drupal 4.3.1 to my local Win2k machine with newly installed Apache 2.0.48, MySQL 3.23.49 and php 4.3.4.
I have Drupal up and running and have been able to enter some test posts. I downloaded a couple of modules (bbcode and composition tips) have tried to install them. Logging in as admin I go to administer/configuration/modules but nothing appears on the screen except for the menu - and then only if the menu is set to appear on the left side of the screen. If I set the menu for the right everything disappears with the exception of the header.
I'm very much a noob to all of this, and I'm sure it's something simple, but it's over my head!
Thanks.
Comments
Sorry, I need to clarify
the following - neither the bbcodes module or the composetips module show up as being available in the list of available modules.
And yes, I did spend four hours
searching through the manual and going through the forums, using both the search function and manually looking through messages, before I posted this question.
Thanks.
Which version of bbcode and c
Which version of bbcode and compose tips did have you downloaded? If they don't show up in the available module list, it is probably because they are too old to work with drupal 4.3.1 (BTW, 4.3.2 is the current version).
Try first to remove these extra modules from the module directory one at a time to see if you can return to a working state.
In that case, you can try the 'cvs' version of the faulty module or contact the module maintainer (see README file).
The versions were
4.3.0 of bbcode and 4.2.0 of compose tips. I've removed both modules from the modules folder but I'm still not seeing any difference. I suppose I'll download the 4.3.2 version of Drupal and try again. And I'll send a gentle message to the folks who wrote those modules to see how they are coming with their upgrades.
As a side note, I am not a programmer so getting under the hood is a rather messy proposition for me. Installing a cms, such as Drupal, is about as far under the hood as I care to get.
I'll let you know more after.
Thanks Bruno
If by removing the two extra
If by removing the two extra module, you are not back to a normal behavior, i.e. administer>>configuration>>module show the list of modules, there must be something wrong with your configuration.
You may have a look to the Apache log file to see if an error is reported there.
Regarding the module, you should use only the module available for a version of drupal. So if a module is not listed with 4.3.0, it might not work with drupal 4.3.x. In your case 4.2.0 compose tips module is not supposed to work with drupal 4.3.0.
Module installation
I decided to wipeout the existing installation of drupal and completely reinstall - with new databases. This time I downloaded 4.3.0 and only the modules that were listed as 4.3.0 compatible.
The first module I attempted to install was the bbcode module. I followed the directions explicitly -
Installation
-------------------------
Required:
- Copy bbcode.module to modules/
- Enable the module as usual from Drupal's admin pages.
Optional:
- Install the compose_tips module to inform your users about BBCode usage.
Configuration
-------------------------
This module needs no configuration. When enabled it filters all text
displayed - you can turn it off by disabling the module. If you would
like to use BBCode as a replacement for HTML, you should set Drupal to
use the "Escape HTML" filter such that no HTML tags are allowed in posts,
only BBCode tags.
Still the same problem - a blank admin-config-modules page. However, I had copied the bbcode folder (the one created when I unzipped the module) to the 'modules' subdirectory (i.e. drupal/modules/bbcode). After seeing that the admin-config-modules page looked just as it had in the previous install I deleted the 'bbcode.module' file from the drupal/modules directory but >left< the bbcode subdirectory in the drupal/modules folder. I went back into drupal to the admin-config-modules page and, lo-and-behold, there was the modules table, and bbcode was listed as a choice.
As you can see above, the readme file that was included only stated to copy the bbcode.module to the modules/ folder. There is no statement directing you to copy the module to a subfolder of drupal/modules. It seems that this is a common assumption within many these module directions - that the user should automatically know to put the folder under the modules directory and >not< put the actual module file into the module/ directory itself. I don't recall reading anything to that effect in the online documentation. I'll take a look there and see what I can find.
I also suspect that it would be wise not to upgrade until all of the modules you need have been upgraded as well.
Thanks for your help.
modules directory vs. subdir
On the subject of modules directory vs. subdir... either will work, so don't worry about the difference. When I have a module that requires supporting files -- maybe a .inc include file or some images -- then I prefer to put them all in a bundle together in a subdirectory. Otherwise, I just place the .module file in the modules directory. Your choice.
Sorry, but that's not my experience
The only way I could get some of these modules to work was by having them in a subdirectory. Perhaps it has something to do with Apache 2. I am a noob at all of this, so I am certainly open to the idea that something in my setup may be askew. :?
Now if I could just get my brain wrapped around this taxonomy concept... :jawdrop:
You could try Apache 1.3.29
I've had bad luck getting Apache 2.0.X working with some combinations, and with PHP (esp. on Win2K) I would recommend using the 1.3.29 release. Yes, I know Apache 2 is officially released and stable, but if you are having weird problems this is a possible solution.
I know that's asking a lot, but I think its worth mentioning as a potential problem, if not in your current situation, then possibly further down the road.
PHP Memory Limit
I had the same problem with a few modules. So I was looking in my apache-log (/var/log/httpd/error_log under Fedora Core 4) and found this message:
The only thing to do was to change the memory_limit in php.ini (/etc/php.ini under FC 4):
For me this works. Thanks to bruno!
PHP Memory Limit
Upping the memory limit worked for me too. I changed the limit to 12M.
Make sure you are root or use sudo to edit php.ini. I also had to restart Apache. ('/etc/rc.d/init.d/httpd restart' with Fedora Core 4)