500 error on Configuration for nice_menu/1

just to confirm.. i just installed latest version with Drupal 5.2 and i also get an Apache server error when i try to configure a nice menu block.

i am unable to reproduce this problem. please upgrade to the most recent 5.x dev release, and report back.

just installed latest - still crashes Apache when i try to configure block.

I try to dig a bit more into it.

Is it possibly a conflict with another module? Someone else has had that issue with audio module: http://drupal.org/node/170482.

i actually don't get a 500 error - Apache simply restarts. Pretty bad.

I do have it working on a couple sites and another couple that i get this issue - so it might be some sort of interaction with some other module (although that shouldnt really be possible) - and i don't use the audio module.

What do your apache error logs say?

they don't say much..

Parent: child process exited with status 3221225477 -- Restarting.

but i now seem to have fixed it :)

i WAS running Apache 2.0.59 and PHP 4.4.4 and i just flipped over to PHP 5.2.3 and the problem seems to have gone away.. very odd.

Ah, interesting! Well I have the same version of Apache but I don't have PHP 4.4.4 available to me, I have 4.4.6. When I test it on PHP 4.4.6 it still works fine for me and I can't get it to belly-up on me.

Glad you got it working, but it is still kinda weird. I'm marking this fixed.

blank page for me - not even getting a 500 error displayed - server info: Apache/1.3.37 (Unix) mod_auth_passthrough/1.8 mod_log_bytes/1.2 mod_bwlimited/1.4 PHP/4.4.7 FrontPage/5.0.2.2635.SR1.2 mod_ssl/2.8.28 OpenSSL/0.9.7f

tlangston, could you let us know what you are getting, if anything, in your various error logs (Drupal watchdog, PHP error log, Apache error log)?

i had a blank page as well - nothing of use in logs.

Like i have already posted though - switching to PHP5 seems to have fixed my problem.

BTW my php.ini files are pretty similar for my PHP4 and PHP 5 setups - but they are not exact. so possibly it is a setting thing rather than an actual PHP version thing - although i would still be on it being a version thing.

Blank page for me too. I look at the HTML source code and it says "Access denied". This is also what it says in the log and, oddly enough, it attributes this log entry to "Anonymous".

Any ideas anyone?

Hi guys. I have managed to isolate that damn bug in my system. View my case analysis for more information: http://zerculator.dyndns.org/?q=node/12

Setting this to active since there is no actual patch attached.

I also found this one reference to a segmentation fault from a while back: http://drupal.org/node/113294#comment-499457

We also have a dude here who found the cause of the problem from waaaayy back before I have even encountered the bug and formed my own case analysis. http://drupal.org/node/113294#comment-499465

Apparently, it seems that the function menu_parent_options(0) has a problem with PHP 4 in one Linux box, because it works flawlessly with PHP 5 in my other Linux box. For now, I see no other workaround on how to build the "Source Menu Tree" without using menu_parent_options().

I would like to dig deeper in Drupal core's menu.inc as well, seeing that it's where menu_parent_options() comes from.

I have finally fixed it Addy. And I have modified my blog at Comment #13 as well. This piece of code will fix everything.

$form['nice_menus_menu_'. $delta] = array(
  '#type' => 'select',
  '#title' => t('Source Menu Tree'),
  '#description' => t('The menu tree from which to show a nice menu.'),
  '#default_value' => variable_get('nice_menus_menu_'. $delta, '1'),
  '#options' => menu_parent_options(0, 0) //Bug squashed by Zer AC (zerac_ee) on 2007-11-03.
);

The justification for the menu_parent_options(0, 0) function call is available at http://zerculator.dyndns.org/?q=node/12. This works well on both my PHP 4 and PHP 5 installations.

I would like to make a patch for it but I don't know how to. :) So I'm simply posting the modification here. I hope someone can make these changes official at the nice_menus project.

Regards,

Rez

fixed means that it's been fixed in the module, not that you figured out the fix :)

setting status appropriately.

Hehe. Well I'm new to this patch-patch thing anyway. Thanks for tip. :)

Keep me posted for any updates one the official code. I'm a big fan of nice_menus and I'm eagerly waiting to use it in production mode for the sites I'm making.

Cheers to the whole Nice Menus team.

Rez

dude, stop changing the issue status to fixed. it's _not_ fixed. the code needs review, then it needs to be committed.

Oops sorry for the wrong status... Didn't notice that the dropdown field pointed to the wrong thing. I wish you guys would place it somewhere more obvious. Now it's "patch (code needs work)". :-( I can't change it.

Ah well, what the heck... setting it right this time. Sorry for all the fuss and the wasted comments.

Thanks Rez for tracking this down. I've created the patch. We need folks who have experienced this to test it out. Once we run it through its paces I'll commit it to the module.

Rez, creating patches is very easy. There is a handbook section just for patches and a page specifically for creating patches that even has a link to a video. If you have trouble figuring out the patching feel free to let me know and I'll help ya out.

Thanks for these links Addy! And thanks for this patch file. :) In all my years of programming, this will be my first time to join some worldwide patch-patch collaboration effort. I think I may get to like this. I'll keep track of this thread.

Alright well I went ahead and committed this to both 5 and HEAD (http://drupal.org/cvs?commit=87453). It doesn't break anything for my testing and hopefully this takes care of the issues others have had.