I'm having some issues upgrading from 6.x-3.7 to 6.x-3.8. Every other module installed and the core are updated, just placing the hierarchical_select folder inside sites/all/modules crashes the whole web server. I've tried disabling all the sub-modules before upgrading with no luck.
Rolling back to the old version fixes the issue.
I'm using "The Uniform Server 8.3.1" (PHP Version 5.3.10, Apache 2.4.1, MySQL 5.5.21) under Windows 7 x64. Been using this as a web developement station for the last year without issues whatsoever on D6 and D7. The crashing DLL in the Windows report is php5ts.dll, I can't seem to find any evidence in the errors.log of Apache.

Comments

wim leers’s picture

wim leers
Location Ghent 🇧🇪🇪🇺
commented
Category: bug » support
Status: Active » Postponed (maintainer needs more info)

Wow, that's interesting. Unfortunately, most of us don't seem to be able to reproduce this. So, for now, I suspect something is wrong on your end. I'm sorry that I can't be of more help.

blackspiraldancer’s picture

blackspiraldancer commented

I'll try reproduce the issue in a Linux environment and a different webserver components versions, I'll get back to you if I see anything interesting.
Feel free to close the issue if I'm not back in two weeks! :)

wim leers’s picture

wim leers
Location Ghent 🇧🇪🇪🇺
commented

Hah! :)

Good luck! :)

fotispan’s picture

fotispan
Primary language Greek
commented

Same issue here with wamp server

loze’s picture

loze commented

same here. Ive narrowed it down to the hs_taxonomy submodule.

Crashes on windows7 with Aquia stack php 5.3 (works with php5.2)

loze’s picture

loze commented

Well this is strange.
removing the comment on line 9 of hs_taxonomy.module
//----------------------------------------------------------------------------

fixes this. I dont know why, but it does.
adding the line back in causes it to crash again.

loze’s picture

loze commented

this may be the reason.
http://drupal.org/node/1562670

kars-t’s picture

kars-t commented
Status: Postponed (maintainer needs more info) » Fixed

Dear fellow Drupal enthusiasts,

this issue is now lasting for a very long time in the issue queue and was unfortunately never solved. As Drupal is a open source project everyone is helping on voluntary basis. So that this is was not solved is nothing personal and means no harm. But perhaps no one had time to deal with this issue, maybe it is too complex or did not describe the problem comprehensibly.

But this issue is not the only one. There are thousands of issues on Drupal.org that have never been worked on or could not be processed. This means that we are building a wave that is unmanageable and just a problem for the Drupal project as a whole. Please help us keep the issue queue smaller and more manageable.

Please read again, "Making an issue report" and see if you can improve the issue. Test the problem with the current Core and modules. Maybe the problem doesn't exist anymore, is a duplicate or has even been solved within this issue but never closed.

Help can also be found for it on IRC and in the user groups.

In order to remove this issue, I have set this issue to "fixed"

If there is new information, please re-open the issue.

Status: Fixed » Closed (fixed)

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