Description
When the image used in a Media & Text block is deleted from the WordPress Media Library, the image still appears in the WordPress editor/backend and on the post front end, but the Media & Text block is omitted from the beehiiv newsletter.
The image URL is still directly accessible, so the block appears to still have a valid image URL available.
Example image URL:
https://beehiivqa.instawp.site/wp-content/uploads/2026/06/image-1024x469.png
Post URL :
https://beehiivqa.instawp.site/qa-media-and-text-2/
Steps to Reproduce
- Create/edit a WordPress post.
- Add a Media & Text block.
- Select/upload an image in the media column.
- Add text content in the text column.
- Save the post.
- Delete the selected image from the WordPress Media Library.
- Confirm that the image still appears in the WordPress editor/backend and on the post front end.
- Enable/send the newsletter to beehiiv.
- Check the beehiiv newsletter/front end.
Expected Result
If the saved image URL is still valid and the image renders in WordPress, the Media & Text block should be included in the beehiiv newsletter.
If the block cannot be mapped because the attachment no longer exists, the plugin should show a warning before sending that the block/content will be omitted.
Actual Result
The image still appears in the WordPress editor/backend and on the post front end, but the Media & Text block is omitted from the beehiiv newsletter.
No warning is shown before sending.
Notes
The mapping doc says attrs.mediaId is not needed for MVP, while attrs.mediaUrl maps to the beehiiv image URL.
This suggests the Media & Text mapping should rely on the saved mediaUrl rather than requiring the WordPress attachment/media ID to still exist, or at least warn the user if the block will be omitted.
Reference from mapping doc:
attrs.mediaId → not needed
attrs.mediaUrl → columns[image_column].blocks[].imageUrl
Description
When the image used in a Media & Text block is deleted from the WordPress Media Library, the image still appears in the WordPress editor/backend and on the post front end, but the Media & Text block is omitted from the beehiiv newsletter.
The image URL is still directly accessible, so the block appears to still have a valid image URL available.
Example image URL:
https://beehiivqa.instawp.site/wp-content/uploads/2026/06/image-1024x469.png
Post URL :
https://beehiivqa.instawp.site/qa-media-and-text-2/
Steps to Reproduce
Expected Result
If the saved image URL is still valid and the image renders in WordPress, the Media & Text block should be included in the beehiiv newsletter.
If the block cannot be mapped because the attachment no longer exists, the plugin should show a warning before sending that the block/content will be omitted.
Actual Result
The image still appears in the WordPress editor/backend and on the post front end, but the Media & Text block is omitted from the beehiiv newsletter.
No warning is shown before sending.
Notes
The mapping doc says
attrs.mediaIdis not needed for MVP, whileattrs.mediaUrlmaps to the beehiiv image URL.This suggests the Media & Text mapping should rely on the saved
mediaUrlrather than requiring the WordPress attachment/media ID to still exist, or at least warn the user if the block will be omitted.Reference from mapping doc:
attrs.mediaId→ not neededattrs.mediaUrl→columns[image_column].blocks[].imageUrl