Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
When I enable this module and am logged out, I get 500 internal server error. Error log: Premature end of script headers: index.php
When I disable this module, all is fine.
Comments
Comment #1
das-peter CreditAttribution: das-peter commentedPlease provided detail information:
admin/config/development/performance
It's always a good idea to do complete cache flush:
drush cc all
or useadmin/config/development/performance
Comment #2
kubilayrd CreditAttribution: kubilayrd commentedHi,
After setting the memory_limit to 128M in settings.php file and clearing all the caches, I could get rid of this very same issue.
In the settings.php file, inserted this line:
ini_set('memory_limit', '128M');
Source Link
Comment #3
das-peter CreditAttribution: das-peter commented@kubilayrd Thanks for the information!
Comment #4
bensnyder CreditAttribution: bensnyder commentedgoing from 2.x to 3.0-beta1, the upgrade process went fine for me. However, several of my nodes that use media fields were getting HTTP 500 (WSOD) if accessed by an anonymous user. Logged in users could see the page, no prob.
I was getting "[notice] child pid XXXX exit signal Segmentation fault (11)" in apache error.log
D7.22, caches fully flushed and I debugged for about 2 hours.
Comment #5
das-peter CreditAttribution: das-peter commented@bensnyder did you try the suggestion in #2
Comment #6
bensnyder CreditAttribution: bensnyder commentedNot in settings.php but in my php.ini I have 512mb allocated
Comment #7
das-peter CreditAttribution: das-peter commented@bensnyder Well, I doesn't matter where it is defined as long as it's set. Btw. did you set the limit to a ridiculous amount to test with, e.g. 2GB?
Actually that sounds more like an issue with the media or file module itself since MBP doesn't affect the output of media/file/image fields.
Comment #8
gintaras.r CreditAttribution: gintaras.r commentedThis also just started happening to me and hopefully the extra info I'm throwing in here will help with this issue. All this is on a test server I set up on my home computer:
- Windows 7 x64; Apache 2.4; MySQL 5.6; PHP 5.4.17
- Drupal 7.22 (with patch 1525176-fix_entity_conditions-D7)
- Built using Spark profile spark-7.x-1.0-alpha9-no-core
- Installed modules: plenty (let me know if you really ned the whole list), but probably the most relevant ones are: file_entity-7.x-2.0-alpha2, media-7.x-2.0-alpha2, media_browser_plus-7.x-3.0-beta1
- Building my own subtheme of AdaptiveTheme (adaptivetheme-7.x-3.1). At this point only css and config changes (ie, no code changes).
- Mostly on Firefox 23.0.1, but tried also on IE10 with similar results
A few days ago i started getting 500 Internal server error (after a long load time) for any and every site URL, and at the time had no idea what could have caused it. Had no luck isolating it via Eclipse/xdebug. Eventually I came across a suggestion to increase memory limit in php.ini. Increased from 128 to 256MB.
Result was the site bombed out with this call stack trace displayed, which to me looks like a smoking gun pointing at MBPlus:
It goes on, but you get the picture. Infinite loop. If not for the 100 nest limit, would have been a 500 error again.
Some extra info that might be relevant:
- The site only has one page (which appears as the front page). This page has two videos embedded inline via Media Embed ckeditor button (which brings up a modal textarea dialog - was a little surprised to not get a MBP window).
- It appears the original poster is correct, in that it only bums out for unauthenticated users, though it may be worth testing for authenticated users without permissions to edit the content.
- Only a few weeks ago I was using file_entity-7.x-2.0-unstable7 and media-7.x-2.0-unstable7, without these issues. That might not mean anything though, as I hadn't embedded any media prior to the upgrade. I also may not have ever logged out (ie, i didn't browse the site as anonymous until a few days ago).
Hopefully this can be fixed and MBP made better and stronger!
-
Comment #9
das-peter CreditAttribution: das-peter commentedInterestingly I don't even have the function
media_browser_plus_file_entity_access()
in the latest MBP-dev version. However there'smedia_browser_plus_file_entity_access_wrapper()
instead.Thus I'd suggest to update MBP to the latest dev version.
Please let me know if this fixes the issue.
Comment #10
gintaras.r CreditAttribution: gintaras.r commentedLooks like that did the trick, at least in my case. Under the circumstances that I was getting the error before, now working as expected. If only everything in life was that easy!
You may want to add a note on the module page, as first instinct is to go for the non-dev version. Thanks for the quick response.
Comment #11
das-peter CreditAttribution: das-peter commented@gintaras.r: Release 7.x-3.x-beta2 (https://drupal.org/node/2088133) should be available soon.
Comment #12
das-peter CreditAttribution: das-peter commentedAs of the feedback from #10 I'd say the cause is found and the issue is fixed - in the latest dev / beta of 7.x-.-3.x.