gatsbyjs/gatsby · error

${node.__typename} ${node.id} couldn't process inline html i

Error message

${node.__typename} ${node.id} couldn't process inline html image ${imageUrl}

What it means

Warning during WordPress inline-HTML image replacement: resolving an image node's publicUrl threw inside the try block; the caught error is logged first, then this warning identifies the WP node (type/id) and the imageUrl whose <img> tag could not be rewritten.

Source

Thrown at packages/gatsby-source-wordpress/src/steps/source-nodes/create-nodes/process-node.js:636

              gatsbyStore
            )
          } else {
            publicUrl = publicUrlResolver(
              {
                url: imageUrl,
                mimeType: imageNode.mimeType,
                filename: path.basename(imageNode.sourceUrl || imageNode.url),
                internal: {
                  contentDigest: imageNode.modifiedGmt,
                },
              },
              helpers.actions,
              gatsbyStore
            )
          }
        } catch (e) {
          reporter.error(e)
          reporter.warn(
            formatLogMessage(
              `${node.__typename} ${node.id} couldn't process inline html image ${imageUrl}`
            )
          )
          return null
        }

        return {
          match,
          cheerioImg,
          fileNode,
          imageResize,
          maxWidth,
          publicUrl,
        }
      })
    )

View on GitHub (pinned to e85d62f177)

Solutions

  1. Check the WordPress media item exists and finished syncing as a node
  2. Verify the image URL, mime type and filename are valid
  3. If the node data looks correct, report the issue with the node id and imageUrl
Defensive patterns

Strategy: try-catch

When it happens

Trigger: Thrown at packages/gatsby-source-wordpress/src/steps/source-nodes/create-nodes/process-node.js:636 when the library encounters an invalid state.

Common situations: See trigger scenarios.


AI-assisted analysis of gatsbyjs/gatsby@e85d62f177 (2026-08-26). Data as JSON: /api/errors/117f47f77f4d4eb0. Report an issue: GitHub.