Hi all,
As I'm still working on the new site, and implementing some of those great modules and more I encountered something with Drupal version 4.6.1.
When adding these modules (1 or all) : banner ecommerce flexinode Then I can't get into the modules activation page. Regardless of the browser I'm using. Anyone knows how come, would be much appreciated. Because these are really good modules not to miss. At least I thing ;-) since I did not have the chance to test them :-(
On my earlier post I spoke about blank screens. These have for sure something to do with the server configuration of your hosting. As I started to test other CMS's as well, to see if they have it to, I have found others with the same problem. And since I switched hosting I'm pretty much sure that's a relation between the server configuration and one or two lines of code. Don't worry, even if everything turns out white, I'll stick to Drupal. Eventually with the help of some more experienced friendly people we kill this thing to make Drupal even better to run smoothly on everything.
Where to start when it's server related you should say. The modules that always deliver blank screens and make your complete site go white are : event taxonomy_image Regardless of the browser I'm using. I would love to get my hands on those two for testing :-O I have to be careful with : image img_assist With the last two. If I change something, still don't know what, these two have the same problem. Only then on the browser family your are working with. So if you are using firefox, then all mozilla based browsers go blank.
In short. Why, or what code locked the module page with the first three modules ? Why, or what code conflicts with something to make the screen go blank within the last four modules ?
As I'm still new to Drupal, perhaps there is somebody who hacked into these modules or has had a more or less same problem.
Thanks in advance, William.
On Thu, 2005-06-09 at 08:52 +0200, William Meertens wrote:
Hi all,
snip
Why, or what code locked the module page with the first three modules ? Why, or what code conflicts with something to make the screen go blank within the last four modules ?
I had the same issue when I added a bunch of modules. For me, PHP was running out of memory. You should be able to verify this by going to the page again and then quickly checking your apache error log. It will probably say something like:
Fatal error: Allowed memory size of 8388608 bytes exhausted ........
I upped the amount of memory PHP is allowed to have by adding this directive:
ini_set("memory_limit","16");
Add that to your site configuration file (towards the bottom you will see a bunch of other ini_set's) and you should be good to go. If 16MB isn't enough, you might need even more, but I doubt it.
As for the screen going blank, I'm betting that is because you turned off the show errors on screen option, hence the blank page. I know that's what caused it for me.
Note: It is possible that your host doesn't allow you to increase the memory PHP can use yourself. You might have to correspond with their support department. And yes, making this change to the other CMS's you were using should fix the issue there too.
Hi all,
Thank you Brian for pushing me ;-)
I actually was playing with this before. Only not sure it helped. In some way it looked even worse. Only now I know why I did not get it the first time.
Your solution : ini_set("memory_limit","16"); Was the one I tried in some form within php.ini, .htaccess and vhosts.conf. Only setting this made everything go blank or nothing worked by clicking on it. Depending on the file and the form.
Yes indeed the form how you type is, is of importance. Your line did not work for me. But this line did : ini_set("memory_limit", "16M");
Do not tell me why, but for me it was needed to include the M and ... what troubled me the most ... the space. Silly but true, without the space between the two values it did not work. And that was the hard part, who would guess that. Where it not for you, I would have given up :-) on this line.
Your second statement about the log-setting. I had it on write to log-file and screen. Now I don't anymore, but it works both ways for me.
The only thing I had not was red lines or failures in my Drupal logs. So that was not bringing much. What I do have is everything put 3 times, and exactly, the same line in my log. Do you or anybody perhaps now why ? Not that it's bothering me, it only fills up the log at a triple speed.
All my best, William.
PS : now we are having real fun again :-)
On Thu, 09 Jun 2005 07:32:51 -0400 Brian Puccio brian@brianpuccio.net wrote Re: [drupal-support] Modules page is locked. :
On Thu, 2005-06-09 at 08:52 +0200, William Meertens wrote:
Hi all,
snip
Why, or what code locked the module page with the first three modules ? Why, or what code conflicts with something to make the screen go blank within the last four modules ?
I had the same issue when I added a bunch of modules. For me, PHP was running out of memory. You should be able to verify this by going to the page again and then quickly checking your apache error log. It will probably say something like:
Fatal error: Allowed memory size of 8388608 bytes exhausted ........I upped the amount of memory PHP is allowed to have by adding this directive:
ini_set("memory_limit","16");Add that to your site configuration file (towards the bottom you will see a bunch of other ini_set's) and you should be good to go. If 16MB isn't enough, you might need even more, but I doubt it.
As for the screen going blank, I'm betting that is because you turned off the show errors on screen option, hence the blank page. I know that's what caused it for me.
Note: It is possible that your host doesn't allow you to increase the memory PHP can use yourself. You might have to correspond with their support department. And yes, making this change to the other CMS's you were using should fix the issue there too.
-
Brian Puccio -
William Meertens