CiviCRM Community Forums (archive)

*

News:

Have a question about CiviCRM?
Get it answered quickly at the new
CiviCRM Stack Exchange Q+A site

This forum was archived on 25 November 2017. Learn more.
How to get involved.
What to do if you think you've found a bug.



  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Upgrading CiviCRM (Moderator: Deepak Srivastava) »
  • Upgrade to 4.3.1 causes WSOD on "New Contribution Page", :New Mailing"
Pages: [1]

Author Topic: Upgrade to 4.3.1 causes WSOD on "New Contribution Page", :New Mailing"  (Read 1669 times)

Cyberflyer

  • I post occasionally
  • **
  • Posts: 35
  • Karma: 2
  • It's a piece of cake, Ezra!!
    • North Star Community Foundation
  • CiviCRM version: 4.5.6
  • CMS version: Drupal 7.34 / Commons 7.x-3.20
  • MySQL version: 5.5.13
  • PHP version: 5.4.38
Upgrade to 4.3.1 causes WSOD on "New Contribution Page", :New Mailing"
April 25, 2013, 10:29:44 am
I'm running CiviCRN 4.2 on Drupal Commons  6.x-2.12 On Drupal 6.28.

I have a local install on Mac OS X 10.6.8/Apache 2.2.24/PHP 5.3.23 of both a 'test' and a 'production' site.

Upgrade to 4.3.0 went well on one, to 4.3.1 went well on the other.

My hosting provider, AN Hosting is running Linux/Apache/PHP 5.3.23

When I upgraded my test install to 4.3.1, I ended up with a situation where trying to add a "New Contribution Page' or a 'New Mailing" gives me a White Screen of Death".  No reply, No watchdog message, no PHP errors Logged, No Server errors logged, No Stack trace, Although I can provoke a Stack trace at SMS messaging because I don't have SMS configured.

It's driving me nuts that there is no debug info at all.  I have run through the usual Drupal WSOD issue solutions and error reporting is full-on.

The same installation runs on my local system and "New Contribution Page" works fine.

Any ideas as to why this is happening would be appreciated.
 ???

Hershel

  • Forum Godess / God
  • I’m (like) Lobo ;)
  • *****
  • Posts: 4640
  • Karma: 176
    • CiviHosting
  • CiviCRM version: Latest
  • CMS version: Mostly WordPress and Drupal
Re: Upgrade to 4.3.1 causes WSOD on "New Contribution Page", :New Mailing"
April 25, 2013, 10:36:36 am
Very hard to say why if there are no messages. :(

I would think the only way would be to debug the code manually by stepping through it....
CiviHosting and CiviOnline -- The CiviCRM hosting experts, since 2007

See here for the official: What to do if you think you've found a bug.

Cyberflyer

  • I post occasionally
  • **
  • Posts: 35
  • Karma: 2
  • It's a piece of cake, Ezra!!
    • North Star Community Foundation
  • CiviCRM version: 4.5.6
  • CMS version: Drupal 7.34 / Commons 7.x-3.20
  • MySQL version: 5.5.13
  • PHP version: 5.4.38
Re: Upgrade to 4.3.1 causes WSOD on "New Contribution Page", :New Mailing"
April 25, 2013, 11:01:07 am
Where do I start? What module, which file?

Coleman Watts

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 2346
  • Karma: 183
  • CiviCRM version: The Bleeding Edge
  • CMS version: Various
Re: Upgrade to 4.3.1 causes WSOD on "New Contribution Page", :New Mailing"
April 25, 2013, 11:26:21 am
Did you check the civi log files? /sites/.../files/civicrm/ConfigAndLog/*
Try asking your question on the new CiviCRM help site.

Cyberflyer

  • I post occasionally
  • **
  • Posts: 35
  • Karma: 2
  • It's a piece of cake, Ezra!!
    • North Star Community Foundation
  • CiviCRM version: 4.5.6
  • CMS version: Drupal 7.34 / Commons 7.x-3.20
  • MySQL version: 5.5.13
  • PHP version: 5.4.38
Re: Upgrade to 4.3.1 causes WSOD on "New Contribution Page", :New Mailing"
April 25, 2013, 11:33:34 am
Yes.  There are backtraces for errors where I don't get the WSOD.  That info is useful for those errors.  Not a peep on the WSOD cases.  I've created a page that forces the error and am working with tech support.

Donald Lobo

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 15963
  • Karma: 470
    • CiviCRM site
  • CiviCRM version: 4.2+
  • CMS version: Drupal 7, Joomla 2.5+
  • MySQL version: 5.5.x
  • PHP version: 5.4.x
Re: Upgrade to 4.3.1 causes WSOD on "New Contribution Page", :New Mailing"
April 25, 2013, 01:56:17 pm

WSOD are mostly php/apache errors. So you'll find more detailed info in the apache error logs (or php error logs)

lobo
A new CiviCRM Q&A resource needs YOUR help to get started. Visit our StackExchange proposed site, sign up and vote on 5 questions

Eileen

  • Forum Godess / God
  • I’m (like) Lobo ;)
  • *****
  • Posts: 4195
  • Karma: 218
    • Fuzion
Re: Upgrade to 4.3.1 causes WSOD on "New Contribution Page", :New Mailing"
April 25, 2013, 02:57:14 pm
In a dev / debug situation you might like to add

ini_set('display_errors', 'On');

to settings.php
Make today the day you step up to support CiviCRM and all the amazing organisations that are using it to improve our world - http://civicrm.org/contribute

Cyberflyer

  • I post occasionally
  • **
  • Posts: 35
  • Karma: 2
  • It's a piece of cake, Ezra!!
    • North Star Community Foundation
  • CiviCRM version: 4.5.6
  • CMS version: Drupal 7.34 / Commons 7.x-3.20
  • MySQL version: 5.5.13
  • PHP version: 5.4.38
Re: Upgrade to 4.3.1 causes WSOD on "New Contribution Page", :New Mailing"
April 26, 2013, 12:10:02 pm
Thanks for the suggestions.  Still no joy.  Here is a message I sent ti AN Hosting:
Quote
On Apr 26, 2013, at 10:35 AM, support@midphase.com wrote:

Hello,

I added a word to  /home/nscfpin0/test/index.php file and the /home/nscfpin0/test/php5_error_log filoe was created.
Please check the force-error page again.
Thank you for your cooperation.
Please let us know if you need more help.
--
--
Best regards
Vitaliy Davydyuk
Level 3 Support Representative
AnHosting

Vitaliy:

Thanks for the attempt at support.  It's a start.  There is a log file.  Current contents are this:

-------
Code: [Select]
[26-Apr-2013 11:33:11 America/Denver] PHP Parse error:  syntax error, unexpected T_STRING in /home/nscfpin0/test/index.php on line 3-------

I put three lines of debug strongarm code into index.php to force error reporting.

Code: [Select]
error_reporting(E_ALL);
ini_set('display_errors', TRUE);
ini_set('display_startup_errors', TRUE);


I've checked for invisibles and cannot find an error.

If that line was failing we would not see any page at the site.



When I go to my test page, I get the text only then the error.

http://test.nscfundalaska.org/force-error   contains:

-------
Code: [Select]
This page will force an error:<br/>
<?php xdebug(); ?>
--------


The response is:

Quote
This page will force an error:

Here is an example of Drupal error reporting at work on the same site:

( screen shot if stack trace)


I have cleared the Cache tables in both the Drupal 6 and CiviCRM database using PHP My Admin.

I have cleared the cache using the Drupal admin interface.

I deleted the Smarty template compile folders by hand through my FTP file manager.

All of this is standard procedure in cases like this to make sure I'm not looking at residue errors.

I have turned on all Drupal Devel module error reporting:



The known (control)  bug in SMS/Send posts a message to the Drupal log file:

Code: [Select]
$Fatal Error Details = Array
(
    [message] => The <a href="/civicrm/admin/sms/provider?reset=1">SMS Provider</a> has not been configured or is not active.
    [code] =>
)



The CiviCRM log shows only the control error:

Code: [Select]
Apr 26 09:46:54  [info] $Fatal Error Details = Array
(
    [message] => The <a href="/civicrm/admin/sms/provider?reset=1">SMS Provider</a> has not been configured or is not active.
    [code] =>
)


Apr 26 09:46:54  [info] $backTrace = #0 /home/nscfpin0/test/sites/all/modules/civicrm/CRM/Core/Error.php(315): CRM_Core_Error::backtrace("backTrace", TRUE)
#1 /home/nscfpin0/test/sites/all/modules/civicrm/CRM/SMS/Form/Group.php(50): CRM_Core_Error::fatal("The <a href=\"/civicrm/admin/sms/provider?reset=1\">SMS Provider</a> has not ...")
#2 /home/nscfpin0/test/sites/all/modules/civicrm/CRM/Core/Form.php(336): CRM_SMS_Form_Group->preProcess()
#3 /home/nscfpin0/test/sites/all/modules/civicrm/CRM/Core/QuickForm/Action/Display.php(93): CRM_Core_Form->buildForm()
#4 /home/nscfpin0/test/sites/all/modules/civicrm/packages/HTML/QuickForm/Controller.php(203): CRM_Core_QuickForm_Action_Display->perform(Object(CRM_SMS_Form_Group), "display")
#5 /home/nscfpin0/test/sites/all/modules/civicrm/packages/HTML/QuickForm/Page.php(103): HTML_QuickForm_Controller->handle(Object(CRM_SMS_Form_Group), "display")
#6 /home/nscfpin0/test/sites/all/modules/civicrm/CRM/Core/Controller.php(316): HTML_QuickForm_Page->handle("display")
#7 /home/nscfpin0/test/sites/all/modules/civicrm/CRM/Core/Invoke.php(292): CRM_Core_Controller->run((Array:3), NULL)
#8 /home/nscfpin0/test/sites/all/modules/civicrm/CRM/Core/Invoke.php(70): CRM_Core_Invoke::runItem((Array:13))
#9 /home/nscfpin0/test/sites/all/modules/civicrm/CRM/Core/Invoke.php(52): CRM_Core_Invoke::_invoke((Array:3))
#10 /home/nscfpin0/test/sites/all/modules/civicrm/drupal/civicrm.module(354): CRM_Core_Invoke::invoke((Array:3))
#11 [internal function](): civicrm_invoke("sms", "send")
#12 /home/nscfpin0/test/includes/menu.inc(350): call_user_func_array("civicrm_invoke", (Array:2))
#13 /home/nscfpin0/test/index.php(20): menu_execute_active_handler()
#14 {main}




However, there is no PHP error file logging of any errors past the one that is there.

PHP error logging is still ineffective.

Some how, some way, exception errors for something as simple as an invalid function call are being thrown into a black hole.

I had suspected this issue may have to do with the Suhosin settings, but the module no longer shows in phpinfo().

http://test.nscfundalaska.org/info.php

I've compiled Xdebug into my local PHP 5.3.23 and it is valuable incases like this. I can utilize MacPDBG to step through cod execution.

The problem is that this problem does not exhibit in my environment, which is as near yours as I can make it.

Can you add Xdebug to my PHP?

I have a vague suspicion that the issue may stem from a Theme issue, but with out reliable error logging, there is no way to know what is happening.

I need your help to resolve this issue and give me the tools I need to do my part.

Thanks for your support.

L.

Hershel

  • Forum Godess / God
  • I’m (like) Lobo ;)
  • *****
  • Posts: 4640
  • Karma: 176
    • CiviHosting
  • CiviCRM version: Latest
  • CMS version: Mostly WordPress and Drupal
Re: Upgrade to 4.3.1 causes WSOD on "New Contribution Page", :New Mailing"
April 29, 2013, 05:05:05 am
If your host can not provide proper support, I would recommend you switch hosts.
CiviHosting and CiviOnline -- The CiviCRM hosting experts, since 2007

See here for the official: What to do if you think you've found a bug.

Cyberflyer

  • I post occasionally
  • **
  • Posts: 35
  • Karma: 2
  • It's a piece of cake, Ezra!!
    • North Star Community Foundation
  • CiviCRM version: 4.5.6
  • CMS version: Drupal 7.34 / Commons 7.x-3.20
  • MySQL version: 5.5.13
  • PHP version: 5.4.38
Re: Upgrade to 4.3.1 causes WSOD on "New Contribution Page", :New Mailing"
May 06, 2013, 10:01:59 am
Well, we have some progress.  Took 4 or 5 tries, but I got support:

Quote
I have managed to get errors reporting working on http://test.nscfundalaska.org/force-error page. For that I did the following. Edited /home/nscfpin0/test/sites/default/settings.php file and replaced:
ini_set('error_reporting', 'E_ALL ^ E_NOTICE');

with:
error_reporting(E_ALL);
ini_set('display_errors', TRUE);
ini_set('display_startup_errors', TRUE);

Please check if this works for you and try it on your actual site.

Now here is what the real issue is -- may be of use to others.

The file 'settings.php' in /sites/all/modules/civicrm/CRM/Contribute/Form/ContributionPage/  was missing.

This is because I enabled a rule in my FTP transfer program to block transfer of that filename, as it is used by Drupal to hold install specific information.

That is a gotcha others should be aware of in a WSOD in the CiviCRM update process.

Doing a synchronize revealed a number of files that were not the same file length, to I overwrote them from my local test instance.

Now it seems the CiviCRM page top menu is broken, so I'm on to diagnose how that happened.

Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Upgrading CiviCRM (Moderator: Deepak Srivastava) »
  • Upgrade to 4.3.1 causes WSOD on "New Contribution Page", :New Mailing"

This forum was archived on 2017-11-26.