White Screen on Edit/New

  • Issue:
    When I create a new page or edit a page in WordPress, I get a blank white screen.

    Environment:
    nginx
    PHP 7.4.1
    MySQL 8.0.16

    WordPress Setup:
    Wordpress 5.9.2
    Advanced Custom Fields Pro 5.12.1
    Akismet 4.2.2
    Cookie Notice & Compliance for GDPR / CCPA 2.2.3
    Gravity Forms 2.6.1
    Hotjar 1.0.12
    Hustle 7.4.13.1
    Redirection 5.2.3
    Site Kit by Google 1.71.0
    SVG Support 2.4.2
    WP All Export 1.3.4
    Yoast Duplicate Post 4.4

    What I’ve Tried:
    1. Clearing caches — browser, server, and plugin. Nope.
    2. Disabling plugins (except ACF, which can’t be disabled without crashing the CMS). Did not work.
    3. Switching themes. This worked, but is clearly not a viable solution.
    4. Downgrading to WP 5.8.3. This worked, but is also not a viable long-term solution.

    I’ve gone into debug mode and cleared out all the Notices and I’m not getting any warnings now. The site renders a white page, but has source code. The source code includes a notice about needing to activate javascript in my browser and suggests the Classic Editor. This happens regardless of which browser/OS I use.

    I get two errors in the Console:

    TypeError: l.styles.forEach is not a function
    at edit-post.min.js?ver…448e76793d7:7:93653
    at Object.useMemo (react-dom.min.js?ver=17.0.1:220:462)
    at c.useMemo (react.min.js?ver=17.0.1:30:236)
    at zt (edit-post.min.js?ver…448e76793d7:7:93622)
    at Le (react-dom.min.js?ver=17.0.1:100:3)
    at Pj (react-dom.min.js?ver=17.0.1:231:183)
    at di (react-dom.min.js?ver=17.0.1:168:305)
    at Nj (react-dom.min.js?ver=17.0.1:168:236)
    at sc (react-dom.min.js?ver=17.0.1:168:96)
    at gf (react-dom.min.js?ver=17.0.1:162:109)
Ye	@	react-dom.min.js?ver=17.0.1:141
Mh.c.callback	@	react-dom.min.js?ver=17.0.1:141
dh	@	react-dom.min.js?ver=17.0.1:80
Bj	@	react-dom.min.js?ver=17.0.1:145
Qj	@	react-dom.min.js?ver=17.0.1:176
unstable_runWithPriority	@	react.min.js?ver=17.0.1:24
Za	@	react-dom.min.js?ver=17.0.1:73
eb	@	react-dom.min.js?ver=17.0.1:170
gf	@	react-dom.min.js?ver=17.0.1:162
Pa	@	react-dom.min.js?ver=17.0.1:157
yd	@	react-dom.min.js?ver=17.0.1:188
(anonymous)	@	react-dom.min.js?ver=17.0.1:191
bi	@	react-dom.min.js?ver=17.0.1:163
zd	@	react-dom.min.js?ver=17.0.1:191
M.render	@	react-dom.min.js?ver=17.0.1:243
Qt	@	edit-post.min.js?ver…5e642d448e76793d7:7
(anonymous)	@	post.php?post=366&action=edit:2205
    react-dom.min.js?ver=17.0.1:177 Uncaught TypeError: l.styles.forEach is not a function
    at edit-post.min.js?ver…448e76793d7:7:93653
    at Object.useMemo (react-dom.min.js?ver=17.0.1:220:462)
    at c.useMemo (react.min.js?ver=17.0.1:30:236)
    at zt (edit-post.min.js?ver…448e76793d7:7:93622)
    at Le (react-dom.min.js?ver=17.0.1:100:3)
    at Pj (react-dom.min.js?ver=17.0.1:231:183)
    at di (react-dom.min.js?ver=17.0.1:168:305)
    at Nj (react-dom.min.js?ver=17.0.1:168:236)
    at sc (react-dom.min.js?ver=17.0.1:168:96)
    at gf (react-dom.min.js?ver=17.0.1:162:109)
(anonymous)	@	edit-post.min.js?ver…5e642d448e76793d7:7
useMemo	@	react-dom.min.js?ver=17.0.1:220
c.useMemo	@	react.min.js?ver=17.0.1:30
zt	@	edit-post.min.js?ver…5e642d448e76793d7:7
Le	@	react-dom.min.js?ver=17.0.1:100
Pj	@	react-dom.min.js?ver=17.0.1:231
di	@	react-dom.min.js?ver=17.0.1:168
Nj	@	react-dom.min.js?ver=17.0.1:168
sc	@	react-dom.min.js?ver=17.0.1:168
gf	@	react-dom.min.js?ver=17.0.1:162
Pa	@	react-dom.min.js?ver=17.0.1:157
yd	@	react-dom.min.js?ver=17.0.1:188
(anonymous)	@	react-dom.min.js?ver=17.0.1:191
bi	@	react-dom.min.js?ver=17.0.1:163
zd	@	react-dom.min.js?ver=17.0.1:191
M.render	@	react-dom.min.js?ver=17.0.1:243
Qt	@	edit-post.min.js?ver…5e642d448e76793d7:7
(anonymous)	@	post.php?post=366&action=edit:2205
Viewing 3 replies - 1 through 3 (of 3 total)
  • Moderator t-p

    (@t-p)

    3. Switching themes. This worked, but is clearly not a viable solution.

    Report the issue to the theme’s developers.

    By the way, what theme are you using?
    Acquired from?

    Thread Starter Dan Bailey

    (@fontosaurus)

    It’s a custom-built theme, not a purchased or downloadable theme. Original developers no longer accessible.

    Moderator t-p

    (@t-p)

    It’s a custom-built theme,

    If this was a custom theme, you may have to go back to your developer team and ask them to make the necessary change(s) to the theme.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘White Screen on Edit/New’ is closed to new replies.