We use cookies to improve your experience. No personal information is gathered and we don't serve ads. Cookies Policy.

ExpressionEngine Logo ExpressionEngine
Features Pricing Support Find A Developer
Partners Upgrades
Blog Add-Ons Learn
Docs Forums University
Log In or Sign Up
Log In Sign Up
ExpressionEngine Logo
Features Pro new Support Find A Developer
Partners Upgrades
Blog Add-Ons Learn
Docs Forums University Blog
  • Home
  • Forums

Blank front-end, back-end works great

Development and Programming

Angie Herrera's avatar
Angie Herrera
357 posts
7 years ago
Angie Herrera's avatar Angie Herrera

So I just migrated an EE 4.1.3 site from local to dev/staging. The back-end CP works fine, no issues. However, the front-end is blank. Here are some things that I’ve tried, none of which brought any change or hint to what’s going on:

  • removed .htaccess entirely
  • had my host check error logs for suppressed PHP errors (couldn’t find any)
  • tried turning debugging on in both, the index.php file and in config.php
  • tried accessing domain.com/index.php directly, as well as domain.com/index.php/subpage-uri

Per PHP info, display_errors is ON and the database is connecting properly.

I’m stuck and not sure what to check next.

       
Jeremy S.'s avatar
Jeremy S.
353 posts
7 years ago
Jeremy S.'s avatar Jeremy S.

Have you double-checked all your paths in the event something differs in your dev/staging environment from your local?

       
Angie Herrera's avatar
Angie Herrera
357 posts
7 years ago
Angie Herrera's avatar Angie Herrera

Yep. I use a multi-environment config file so that’s definitely taken care of. I double-checked to be sure. I also switched to the standard single environment config and that produced the same results.

       
Derek Jones's avatar
Derek Jones
7,561 posts
7 years ago
Derek Jones's avatar Derek Jones

Give this a shot to eliminate potential hidden PHP errors:

https://gist.github.com/litzinger/5598641

       
Angie Herrera's avatar
Angie Herrera
357 posts
7 years ago
Angie Herrera's avatar Angie Herrera

Thanks Derek - that helped me find the issue (which was a Wygwam file needing to have an uppercase letter instead of lowercase).

       
Derek Jones's avatar
Derek Jones
7,561 posts
7 years ago
Derek Jones's avatar Derek Jones

Glad to help!

       
Derek Jones's avatar
Derek Jones
7,561 posts
7 years ago
Derek Jones's avatar Derek Jones

Incidentally do you happen to have the exact PHP error handy or can you trigger it again? I’m wondering if this is something we could trap so that on environments like this we could expose the error to the admin without having to add that PHP code.

       
Angie Herrera's avatar
Angie Herrera
357 posts
7 years ago
Angie Herrera's avatar Angie Herrera

Yep - I was able to reproduce. This time I got an additional error though (go figure). Here’s a screenshot of the error when I add the advanced php code from the gist: https://d.pr/i/yyvxSQ

The original error I got was similar to the first one in the screenshot in reference to Wygwam. That’s caused by the file in this screenshot (https://d.pr/i/G0XcDQ) needing to be Helper.php and not helper.php.

The second error is new though. Not sure what’s going on there. When I fix the Wygwam issue and remove the additional PHP code from index.php, everything works fine.

Hope that helps.

       
Derek Jones's avatar
Derek Jones
7,561 posts
7 years ago
Derek Jones's avatar Derek Jones

It does, thank you!

       

Reply

Sign In To Reply

ExpressionEngine Home Features Pro Contact Version Support
Learn Docs University Forums
Resources Support Add-Ons Partners Blog
Privacy Terms Trademark Use License

Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.