php does not work at root level after upgrading with EA3

ronjo

• May 03, 2016 22:06

I upgraded my php to version 5.5.34 witn EA3. On one of my domains php gives error 500, but only at root level. Code in folders works fine. Any suggestions what to look for?

• 

  24x7server

  • May 04, 2016 11:55

  Hello :), Have you checked your .htaccess code of your root directory ? let know what exact error are you getting in apache error logs file.

  0
• 

  cPanelMichael

  • May 04, 2016 17:22

  On one of my domains php gives error 500, but only at root level. Code in folders works fine.

  
  Hello, Could you let us know the error messages listed under the "Errors" option in cPanel when you see the error in your web browser? This option is documented at: Errors - Documentation - cPanel Documentation We should be able to help narrow down the problem with the full error message. Thank you.

  0
• 

  ronjo

  • May 05, 2016 12:04

  1. I have no .htaccess at root level. 2. The error I get: [05-May-2016 08:35:49 UTC] PHP Fatal error: Directive 'allow_call_time_pass_reference' is no longer available in PHP in Unknown on line 0

  0
• 

  cPanelMichael

  • May 05, 2016 16:56

  . The error I get: [05-May-2016 08:35:49 UTC] PHP Fatal error: Directive 'allow_call_time_pass_reference' is no longer available in PHP in Unknown on line 0

  
  The "allow_call_time_pass_reference" directive is no longer available in the version of PHP installed on your system. Are you using a custom php.ini file within your account? If so, ensure you rename it to disable it, and then copy the file from /usr/local/lib/php.ini to the account. Or, if you are defining that value in your account's .htaccess file, ensure you remove the entry. Thank you.

  0
• 

  ronjo

  • May 05, 2016 22:51

  No, I am not using a custom php.ini what I am aware of. And even if I did, how does that only cause this error at root level? Where should the custom php.ini been placed?

  0
• 

  cPanelMichael

  • May 06, 2016 10:24

  Is this a WordPress website? If so, there's a similar report on their forums at: WordPress " Support " PHP Upgrade Site Continues to Error after Upgrades In that case, switching to a default theme addressed the issue, suggesting the problem was with the custom theme. Thank you.

  0
• 

  ronjo

  • May 06, 2016 12:29

  No, this is not WP. The index.php just contained a header redirect. Like "); ?> I replaced it with a js redirect. But I have other php scripts in the root that is harder to replace. I think it is some server directive that remain from previous installation...

  0
• 

  cPanelMichael

  • May 06, 2016 19:11

  Feel free to open a support ticket using the link in my signature so we can take a closer look. You can post the ticket number here so we can update this thread with the outcome. Thank you.

  0

Please sign in to leave a comment.