blank screen in Edit posts and pages

  • Resolved skyfer

    (@midox08)


    5 years, 4 months ago

    When I’ve tried to edit a post, the page went to a blank screen, I’ve searched for the solution in this forum … and I’ve tried many of them such as deactivate plugins and using the default theme of wordpress … I also clear the cache and used another browser … but still have the same problem.

    I even try to use the last backup for the website, it was on 26 October, but sill have the problem.

    This is what the console show me on this page:

    style-rtl.css:1 Failed to load resource: the server responded with a status of 500 ()
    moxie.js:1 Failed to load resource: the server responded with a status of 500 ()
    wp-embed.js:1 Failed to load resource: the server responded with a status of 500 ()
    jquery-migrate.js?ver=1.4.1:23 JQMIGRATE: Migrate is installed with logging active, version 1.4.1
    moxie.js:1 Failed to load resource: the server responded with a status of 500 ()
    plupload.js:2379 Uncaught ReferenceError: mOxie is not defined
    at plupload.js:2379
    wp-embed.js:1 Failed to load resource: the server responded with a status of 500 ()
    heartbeat.js:1 Failed to load resource: the server responded with a status of 500 ()
    wp-mediaelement.js:1 Failed to load resource: the server responded with a status of 500 ()
    components.js:1 Failed to load resource: the server responded with a status of 500 ()
    wp-mediaelement.js:1 Failed to load resource: the server responded with a status of 500 ()
    react-dom.js?ver=16.8.4:21347 Download the React DevTools for a better development experience: https://fb.me/react-devtools
    components.js:1 Failed to load resource: the server responded with a status of 500 ()
    dmp.js:19 Uncaught TypeError: Cannot read property ‘Autocomplete’ of undefined
    at Module.357 (dmp.js:19)
    at __webpack_require__ (dmp.js:17)
    at dmp.js:19
    at dmp.js:19
    editor.js:2950 Uncaught TypeError: Cannot read property ‘SETTINGS_DEFAULTS’ of undefined
    at Module.358 (editor.js:2950)
    at __webpack_require__ (editor.js:21)
    at editor.js:85
    at editor.js:88
    block-library.js:5517 Uncaught TypeError: Cannot read property ‘withFallbackStyles’ of undefined
    at Module.<anonymous> (block-library.js:5517)
    at __webpack_require__ (block-library.js:21)
    at Module.<anonymous> (block-library.js:20111)
    at Module.<anonymous> (block-library.js:20240)
    at __webpack_require__ (block-library.js:21)
    at block-library.js:85
    at block-library.js:88
    edit-post.js?ver=3.3.6:1488 Uncaught TypeError: Cannot read property ‘createSlotFill’ of undefined
    at Module.360 (edit-post.js?ver=3.3.6:1488)
    at __webpack_require__ (edit-post.js?ver=3.3.6:21)
    at edit-post.js?ver=3.3.6:85
    at edit-post.js?ver=3.3.6:88
    format-library.js:1269 Uncaught TypeError: Cannot read property ‘withSpokenMessages’ of undefined
    at Module.367 (format-library.js:1269)
    at __webpack_require__ (format-library.js:21)
    at format-library.js:85
    at format-library.js:88
    post-new.php:1797 Uncaught TypeError: Cannot read property ‘initializeEditor’ of undefined
    at HTMLDocument.<anonymous> (post-new.php:1797)
    style-rtl.css:1 Failed to load resource: the server responded with a status of 500 ()

    I really need help !! what the other solutions that I can do ?

Viewing 2 replies - 1 through 2 (of 2 total)
  • Moderator James Huff

    (@macmanx)

    Internal server errors (error 500) are often caused by plugin or theme function conflicts, so if you have access to your Dashboard, try deactivating all plugins. If you don’t have access to your Dashboard, try manually resetting your plugins (no Dashboard access required). If that resolves the issue, reactivate each one individually until you find the cause.

    If that does not resolve the issue, try switching to the Twenty Nineteen theme to rule-out a theme-specific issue. If you don’t have access to your Dashboard, access your server via SFTP or FTP, or a file manager in your hosting account’s control panel (consult your hosting provider’s documentation for specifics on these), navigate to /wp-content/themes/ and rename the directory of your currently active theme. This will force the default theme to activate and hopefully rule-out a theme-specific issue.

    If that does not resolve the issue, it’s possible that a .htaccess rule could be the source of the problem. To check for this, access your server via SFTP or FTP, or a file manager in your hosting account’s control panel, and rename the .htaccess file. If you can’t find a .htaccess file, make sure that you have set your SFTP or FTP client to view invisible files.

    If you weren’t able to resolve the issue by either resetting your plugins and theme or renaming your .htaccess file, we may be able to help, but we’ll need a more detailed error message. Internal server errors are usually described in more detail in the server error log. If you have access to your server error log, generate the error again, note the date and time, then immediately check your server error log for any errors that occurred during that specific time period. If you don’t have access to your server error log, ask your hosting provider to look for you.

    Thread Starter skyfer

    (@midox08)

    Thank you, problem resolved, I just didn’t clear my browser data to see the differences when I deactivated the plugins …

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘blank screen in Edit posts and pages’ is closed to new replies.