# Critical error on publish post to Discourse

**URL:** <https://meta.discourse.org/t/critical-error-on-publish-post-to-discourse/200009>\
**Category:** WordPress\
**Created:** [August 10, 2021, 10:17pm UTC](https://meta.discourse.org/t/critical-error-on-publish-post-to-discourse/200009 "2021-08-10T22:17:53Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![angus](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/angus/32/341715_2.png) [@angus](https://meta.discourse.org/u/angus)\
**Post date:** [August 11, 2021, 1:13am UTC](https://meta.discourse.org/t/critical-error-on-publish-post-to-discourse/200009/2 "2021-08-11T01:13:26Z")

</div>

Hey CJ, it looks like the error is coming from the Divi plugin or one of its extensions.

> [@oreillyc](#):
>
> An error of type E\_ERROR was caused in line 207 of the file /www/sociocracyforall\_679/public/wp-content/themes/Divi/includes/builder/feature/gutenberg/blocks/Layout.php. Error message: Uncaught ArgumentCountError: Too few arguments to function ET\_GB\_Block\_Layout::get\_the\_excerpt()

Indeed, if you google `ET_GB_Block_Layout` you’ll see a number of other sites have the same issue (In many cases present in the HTML being scraped by google). You should check you’re running the latest version of their plugin, and perhaps report this to Elegant Themes.

The reason the [WP Discourse](https://github.com/discourse/wp-discourse) code appears (further down, which typically means it’s not the source of the issue) in the stack trace is because whenever you click the publish button any post-publication code will be executed, in an interconnected fashion.

If there’s any exception post-publication, whatever the source, the [wp discourse](https://github.com/discourse/wp-discourse) plugin code is likely to appear at some point in the stack trace. It doesn’t mean it’s the source of the issue though.

---

_[View the full topic](https://meta.discourse.org/t/critical-error-on-publish-post-to-discourse/200009)._
