I am running Display Suite 7.x-1.2 and it seems to be working fine. However, when I try to update DS to either version 7.x-1.3 or version 7.x-1.x-dev (from August 8), it crashes my entire Drupal site. I have tried using D7's automatic update and updating manually using the regular update process and I get the same result. Once I have copied the new DS module folder into sites/all/modules, the next time I go to my Drupal site and try to load any page (including running update.php), I immediately get an error screen from my browser saying "Internet Explorer cannot display this page". If I switch the DS folder in sites/all/modules back to version 7.x-1.2 and go back to my Drupal site, all pages show up fine again.

While I could stick with Display Suite 7.x-1.2, as the site admin, I keep getting these Drupal messages saying there is a critical security update for Display Suite (7.x-1.3) and telling me to upgrade immediately. Any help would be very much appreciated.

In terms of my setup, I am running Drupal 7.7 with CTools 7.x-1.0-rc1 (the latest recommended release), and I am using Internet Explorer 8.

CommentFileSizeAuthor
#15 ds_extras.info.patch514 bytesdub4u
#10 1244514.patch793 bytesswentel
#9 1244514.patch330 bytesswentel

Comments

swentel’s picture

Status: Active » Postponed (maintainer needs more info)

You should check your error logs of either php or your webserver - this has nothing todo with a browser.

mrpauldriver’s picture

I'm getting the same problem and don't even have the module enabled currently

When I attempt to run update.php my browser returns the following error:
Error 101 (net::ERR_CONNECTION_RESET): The connection was reset.

My Apache error log reports the following:
[Fri Aug 12 13:38:29 2011] [notice] Parent: child process exited with status 255 -- Restarting.
[Fri Aug 12 13:38:29 2011] [notice] Apache/2.2.17 (Win32) PHP/5.3.4 configured -- resuming normal operations
[Fri Aug 12 13:38:29 2011] [notice] Server built: Oct 24 2010 13:33:15
[Fri Aug 12 13:38:29 2011] [notice] Parent: Created child process 1492
[Fri Aug 12 13:38:29 2011] [notice] Child 1492: Child process is running
[Fri Aug 12 13:38:29 2011] [notice] Child 1492: Acquired the start mutex.
[Fri Aug 12 13:38:29 2011] [notice] Child 1492: Starting 64 worker threads.
[Fri Aug 12 13:38:29 2011] [notice] Child 1492: Starting thread to listen on port 80.

As soon as I remove the ds folder from the sites/all/modules directory the situation resolves.

swentel’s picture

Status: Postponed (maintainer needs more info) » Active

Hrm, looks like a php 5.3.x error - I should really start deploying and testing on php 5.3, still doing that on php 5.2. That's a good pointer, it's most likely that, I'll investigate that next week.

swentel’s picture

Priority: Critical » Major

Ok, this is weird, I can easily run DS on PHP 5.3 - note it's PHP 5.3.6 on my local machine here. There's one php 5.3.x issue in the queue, see #1244896: Revert layout results in warning: Parameter 1 to ds_revert_layout_field_settings_form() expected to be a reference, but I don't think that would relate to an apache crash since that file isn't called often. And I don't see any problems related to the .install file as well. So, so far I can't reproduce this at all and I can't really tell what's going on here, maybe upgrade to latest PHP version ?

honza pobořil’s picture

I used to have same issue, it was cost by some missing table. (missing update script?) Reinstall of DS solved errors.

wolfib’s picture

Hi,

Having the same trouble when I try to install it from scratch (either the 7.3 or dev version).

I've checked my apache log, but there's nothing in it when trying to access the admin/modules page (with ds folder in my module folder).

I've tried with several browsers. Chrome only tells me this :

Erreur 101 (net::ERR_CONNECTION_RESET) : The connection was reset.

Note also that my php.ini memory limit is set to 128Mo. My PHP version is 5.3.4.

Hope that helps...

swentel’s picture

Looks like PHP 5.3.4 seems to be a consistent factor - it happens at least for 2 users - I'll have to try and install that version - I'm running 5.3.6

swentel’s picture

Status: Active » Postponed (maintainer needs more info)

Could anyone running php 5.3.4 try and upgrade (or downgrade) and see if the crashing goes away ? - In the meantime I'm trying to find a 5.3.4 version (I'll have to built myself I'm afraid) and see I can reproduce this.

swentel’s picture

StatusFileSize
new330 bytes

Also, here's a patch that changes the ds_update_7003 line - you never know.

swentel’s picture

StatusFileSize
new793 bytes

updated patch - again, not even sure.

wolfib’s picture

Hi,

I've tried the two patches, but same problem... :(

I'm not sure I am keen enough at upgrading my php version, but I'm sure that unfortunately all hosing systems won't have the latest version.

Thanks for help.

langworthy’s picture

For what it's worth I didn't have any problems upgrading with php 5.3.5-1ubuntu7.2

dub4u’s picture

Subscribe. I also have PHP 5.3.4 on a WAMP setup and after installing DS 7.x-1.3, Drupal crashes. All I get in error log looks the same as Paul Driver's above.

However, I had no prior version of DS installed, 7.x-1.3 was the first version I ever installed on this system.

dub4u’s picture

OK, I've narrowed this down to ds/modules/ds_extras/ds_extras.module

Basically what I did is

  1. Install DS via http install URL from admin/modules/install
  2. Server crashes now, so remove ALL files from sites/all/modules/ds, restart server
  3. Server responds again normally, doesn't list Display Suite
  4. Then I added one file at a time, and reloaded admin/modules/list after each file addition:
    1. ds.info
    2. ds.install
    3. ds.module
    4. ds/modules/ds_extras/ds_extras.info
    5. ds/modules/ds_extras/ds_extras.install
    6. ds/modules/ds_extras/ds_extras.module

And BANG, that's where the server crashes. If I now remove the file, the server still crashes until it has been restarted.

Hope this helps.

dub4u’s picture

Status: Postponed (maintainer needs more info) » Needs review
StatusFileSize
new514 bytes

Further investigation suggests that the description field of ds_extras.info is too long. The attached patch fixes the problem for me.

Please review.

swentel’s picture

Status: Needs review » Postponed (maintainer needs more info)

@dub4u THAT is awesome. I'll make it my personal goal this weekend to try and get myself a 5.3.4 installation and reproduce this behavior. I hope I can somehow can find the root of this problem, since I'm kind of afraid this might be a really freaky PHP problem. I'll do the best I can, really thanks for that report!

swentel’s picture

Status: Postponed (maintainer needs more info) » Needs review

Oops, cross posted, that patch is an even better step. Can anyone in this thread try and see if this fixes the problem. @dub4u, as I've said in #16, I need to try and get me a 5.3.4 installation and hope that everything crashes first and that patch fixes it :)

dub4u’s picture

@swentel: yes, this looks like Drupal core has a problem with PHP 5.3.4

iwerksom’s picture

I can confirm that the patch in #15 works. I am running PHP 5.3.4 on Wampserver 2.1.
Before the patch the Apache error log reported: Parent: child process exited with status 255 -- Restarting

swentel’s picture

Status: Needs review » Fixed

Ok, I've committed this to the dev version, thanks!

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.