Posted by kingfisher64 on August 2, 2011 at 11:18pm
6 followers
Jump to:
| Project: | Share Buttons (AddToAny) by Lockerz |
| Version: | 7.x-3.1 |
| Component: | Code |
| Category: | support request |
| Priority: | critical |
| Assigned: | Unassigned |
| Status: | closed (works as designed) |
Issue Summary
This module causes my site to produce the dreaded white screen of death once installed. I have tried copying, pasting, deleting the module in and out of the modules dir and it's defiantly something within the module. I havn't got any error logs to give you, just a blank white screen in behavior.
I tried 7.x-3.1 and 7.x-3.x-dev and both installations result in the same behavior. Once the module is removed no more wsod. I've gone back and forth testing this and without failure once in the mod dir...
I'm not a programmer but a designer so i'm not sure regarding how I would troubleshoot this issue to give you useful error logs or any other info. Any advice?
Comments
#1
I having almost the same problem.
clean install of drupal 7 on a virtual host with wamp. all the other modules install just fine. but when i try to install add to any it gives me an connection reinilisation error screen in the module screen.
im using drupal 7.7
frank
#2
I am getting the same WSOD, whether I am trying to install the module through the module configuration or manually by adding the module to the sites/all/modules folder. When I remove the module, everything behaves normally.
I am using the latest WAMP server in Windows 7, PHP 5.3.4, Apache 2.2.17, MySQL 5.1.41 and Drupal 7.7.
#3
Is anybody to do with the module going to help us? This was posted over 2 weeks ago and it's not as if it's a minor bug, it totally corrupts the drupal installation.
Some help would be appreciated.
#4
Doesn't seem to be affecting many others, and I wasn't able to reproduce the issue on a WAMP install.
@kingfisher64 are you also using WAMP? I'm wondering if a certain WAMP config is the issue...
Oftentimes this type of issue tends to be some sort of conflict and not the module that's directly causing issue. Would be great to pinpoint the root cause.
#5
Yep i'm using WAMP. Is there any specs I can give you to try and help pinpoint the problem?
Thanks for the reply it's much appreciated.
* Edit *
Apache/2.2.17 (Win32)
PHP/5.3.4
MySQL 5.1.53
#6
I can confirm this, same exact issue as kingfisher64, same wamp setup/version. I get a 101 error code in google chrome when i try to install it.
Apache error log has this, not sure if this helps:
[Wed Oct 12 16:14:59 2011] [notice] Parent: child process exited with status 255 -- Restarting.
[Wed Oct 12 16:14:59 2011] [notice] Apache/2.2.17 (Win32) PHP/5.3.4 configured -- resuming normal operations
[Wed Oct 12 16:14:59 2011] [notice] Server built: Oct 24 2010 13:33:15
[Wed Oct 12 16:14:59 2011] [notice] Parent: Created child process 3476
[Wed Oct 12 16:14:59 2011] [notice] Child 3476: Child process is running
[Wed Oct 12 16:14:59 2011] [notice] Child 3476: Acquired the start mutex.
[Wed Oct 12 16:14:59 2011] [notice] Child 3476: Starting 64 worker threads.
[Wed Oct 12 16:14:59 2011] [notice] Child 3476: Starting thread to listen on port 80.
#7
Update, i installed wamp 2.2 (apache 2.2.21 / php 5.3.8 / mysql 5.5.16) and was able to install the module. So appears something about wamp 2.1 (apache 2.2.17 / php 5.3.4 / mysql 5.1.53) doesn't play nice with this module.
#8
Upgrade WAMP: #1237438-7: WSOD due to WAMP (upgrading WAMP fixes)
#9
I'm using wamp 2.2 but get this error on install.php
hmm ok when I don't have the addtoany module extracted in my sites/all/modules folder I don't get this error. Install went fine without it.