Enabling Block Bar causes drupal site crash

I have also seen this and in my case it turned out that I had enabled 3 containers originally and had the 3 defined in my theme regions (which worked) but then changed the settings back to 2 *without* changing the number defined in my theme. 500 error occurred.

I just installed BlockBar, told it to make one block, enabled that block, and now all I get is the white screen for my site. I don't know how to tell if I'm getting an apache error as I'm hosted. I'm on RC3, btw. I'm going to delete the module and hope my site comes back.

Hopefully this will get fix as I was really hoping to use this module. :(

Michelle

Shouldn't have hit submit so fast. I went and renamed my module to blockbar.module.bad and instantly my site was fine, so it's definitely this module that did it.

Michelle

Same thing here. 4.7 RC3. I had to delete the module to get my site back. Argh.

Here's what I did:

1. installed blockbar.module.
2. Added the 'blockbar_container_1' and the 'blockbar_container_2' regions to Blue Marine's theme .engine file.
3. Enabled the Module in Admin > Modules.
4. Enabled 1 blockbar in Admin > Settings > Blockbar
5. Enabled the new Blockbar to show in the left sidebar region, and added three regular blocks to it in Admin > Blocks.
6. Clicked "Updated Blocks" and the screen went white. No text. No error message. Nothing.
7. Deleted the blockbar module folder in Modules and the site came back.

This looks like a wonderful module. I hope my info helps you figure out what went wrong!

Using RC4...

I think I figured out the problem. Block Bar 1 defaults to the left region and to show the left region blocks within the Block Bar (source region in configure>block bar 1). For whatever reason Block Bar works if the source region specifies another region (ie- block bar shows in left region, the source region is the stuff in the right region) but not when both the block placement and the source region are the same.

When doing a fresh install and enabling the module it just appeared to not work. I then changed the source region to "right" which gave me a block bar in the left region with the right region contents and the same contents in the right region. When I changed the source region back to "left" it produced an 500 error message.

I experience the same.

When I examined the Apache log, it told me, that:

[Wed May 3 21:20:56 2006] [error] PHP Fatal error: Allowed memory size of 16777216 bytes exhausted...

ok, I said, let's give more memory to this. The new limit was 24M.

The new error message:

[Wed May 3 21:26:08 2006] [error] PHP Fatal error: Allowed memory size of 25165824 bytes exhausted...

So there is sth very wrong with it... :(

Okay, As the author of this module I tought I would chime in here. I have not had time to dig into this lately. My plan was to wait until the 4.7 release and then reseach and fix this bug. That's still the plan but it may be a week or two until I can get to it. My guess is that if configured incorrectly the module (or Drupal itself) could be in an infite loop.

In the mean time, patches are welcome if anyone wants to take a stab at this. If not then expect a fix in the next few weeks.

Common guys, there should ba HUGE red warning on that page:
http://drupal.org/node/36373
Make this warning signt happen, or hear more and more ppl complaining about it !

Hi der,

pls ignore my previous writings. I did not take enough care to read your documentation and I put the blockbar in a conventional region.

I hope this memory-consuption description will help you in the future. It is working very nicely, a big thx for it!

This diagram may help those that are having trouble understanding how to configure this module.

fixed