Skip to content
This repository has been archived by the owner on Apr 30, 2020. It is now read-only.

White Screen Of Death when use Flynt starter theme #273

Open
HeoChauA opened this issue Apr 26, 2018 · 3 comments
Open

White Screen Of Death when use Flynt starter theme #273

HeoChauA opened this issue Apr 26, 2018 · 3 comments

Comments

@HeoChauA
Copy link

I using Flynt started theme and I have an issues:

  1. I cloned latest version of Flynt theme, using latest plugins:
  1. I run command in theme folder follow:
  • yarn
  • yarn build
  • yarn start
  1. Created virtual host name: flynt.local
  2. Enable 3 plugins and theme
    But I have "White Screen Of Death" when go to the pages, posts with: localhost:3000 or flynt.local
    How to fix this?
@dgrdl
Copy link
Contributor

dgrdl commented Apr 27, 2018

Hi @HeoChauA,

how is your WordPress installation set up? Could it be that there are no posts added in the backend? The default posts page should show a basic post list or nothing (white screen) if there are none.

On a side note, have you considered using the Flynt CLI to set up a blank installation instead?

Let me know if that resolved your issue.

@bdbch
Copy link
Contributor

bdbch commented Apr 28, 2018

@HeoChauA Did you tried using a page as the frontpage of your WP installation? What does your HTML markup produced by WP look like? Just an empty body or is there any Flynt markup included? It's not really clear if you already tried pages or post archives etc.

If it's a PHP error another way to find out what is wrong you could use PHP notice output or Xdebug to hook into some breakpoints of your wordpress installation to see if your code stops working on a certain line of code.

Hope we can help you somehow.

@bdbch
Copy link
Contributor

bdbch commented Jun 9, 2018

@HeoChauA I think I found the issue.

In your theme, go to Features/TimberLoader/functions.php and change line 44 from

$output = Timber::fetch($filePath, $componentData);

to

$output = Timber::fetch('index.twig', $componentData);

Should work now.

This should be a temporary fix since it's a major bug for Windows users. ( Yeah I know, Windows. 😁)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants