• Resolved mwarbinek

    (@mwarbinek)


    When I used Elementor to build my webpages, this was months before WordPress changed their editor to the Gutenberg Block editor. When WordPress updated to include Gutenberg editor, I have not used Elementor on my website until today.

    Today, when I created a new post (Project), the Gutenberg editor loaded first and showed the “edit with Elementor” Blue button. I click the Elementor button and it started to load, then suddenly the page changed to a white page listing a fatal memory error in two separate PHP files.

    The only thing that fixed it was to go to Elementor > Settings > Advanced and enable the “Switch Editor Loader Method” selection.

    Reloading the project post page, clicked the “Edit with Elementor” button and it loaded properly with no errors.

    I returned to Elementor settings, disabled the “Switch Editor Loader Method”, and tried it again. The project post loaded Elementor properly.

    So, enabling the “Switch Editor Loader Method” selection in settings seemed to have fixed something because I could not repeat the error, at least this time.

    Does the browser caching have a part in this?

    I think it also may have something to do with WordPress’s Gutenberg editor.

    FYI to others

Viewing 2 replies - 1 through 2 (of 2 total)
  • From this doc, https://docs.elementor.com/article/362-erremptyresponse-while-editing-with-elementor

    Switch Editor Loader Method is useful in solving the “err_content_decoding_failed” and err_empty_response” issues that sometimes occur. Enabling this option helps users running sites on servers with low resources which have difficulty reading long JSON code. When enabled, the tool splits the lines so that these servers can read the JSON code without issues. Switching to this method won’t negatively affect performance. Instead, it will likely improve performance.

    Perhaps something was temporarily causing low resources on your server. Just a guess, but glad you got it resolved.

    Thread Starter mwarbinek

    (@mwarbinek)

    thanks ??

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Fatal Error: Insuffiecent Memory / WordPress Gutenberg Block Editor’ is closed to new replies.