Troubleshooting Editor and Media Issues
BuddyPress Member Blog overviewFree + ProGet BuddyPress Member Blog →
Problems with the post composer, the three editors, image uploads and autosave. The composer saves, uploads and autosaves through the WordPress REST API, so many of these come back to scripts or REST requests being blocked.
The editor does not load
Section titled “The editor does not load”Symptom. The composer shows “Loading editor…” and never finishes, or the writing area is empty.
Check first. Update Free and Pro to 4.3.0. Earlier versions sent a strict Content Security Policy on the composer page that blocked scripts served from a CDN (for example Bunny, QUIC.cloud or Cloudflare) or an offload plugin.
Then work through these.
- Look for errors. Open the browser’s developer tools (F12, or Cmd+Option+I on a Mac) and check the Console tab. A red error usually names the file or plugin at fault.
- Script optimisation. Plugins and host features that combine, defer or delay JavaScript (for example Autoptimize, WP Rocket, LiteSpeed Cache) can break the editor. Exclude the plugin’s scripts, or turn off “delay JavaScript” for the composer page, and clear the cache.
- Your own Content Security Policy. If your site, host or a security plugin sends a CSP header, it must allow every origin your site serves scripts, styles and fonts from. Member Blog’s own header on the composer page is only
frame-ancestors 'self'; developers can change it with thebpmb_csp_policyfilter. - Page caching. The composer page must not be cached. The plugin sends no-cache headers there, but some cache layers ignore them. Exclude the submission and dashboard pages from your page cache.
- Try another editor. Under WB Plugins > Member Blog > Editor, switch Active editor to Classic Editor (TinyMCE) and test. If Classic works and Editor.js does not, a script conflict is the likely cause.
- Find the conflict. Switch to a default theme and deactivate other plugins, then reactivate them one at a time.
Saving or publishing fails
Section titled “Saving or publishing fails”Symptom. Clicking Save, Submit or Publish shows a message that the request failed, or nothing happens.
- REST API blocked. Visit
/wp-json/while logged in; you should see JSON. If a security plugin or firewall blocks/wp-json/, allow it for logged-in users. See Common issues. - Validation message. Read the message above the form or beside the field. It names what is wrong, such as a missing title, a blocked category or, with Pro, a word limit.
- A limit or credits banner (Pro). If a banner names a posting limit or credits, publishing a new post is blocked until the limit resets or credits are added. Saving a draft still works.
- Session expired. If you were logged out in another tab, reload the page and log in again. Your autosaved work is offered back.
Images do not upload
Section titled “Images do not upload”Check the size limits. Three limits apply and the smallest wins:
| Limit | Where to check | Default |
|---|---|---|
| Maximum upload size | WB Plugins > Member Blog > Content > Image Uploads | 20 MB |
| Your server’s limit | Shown next to that setting as “Your server maximum” | Set by your host |
PHP upload_max_filesize and post_max_size |
Your hosting control panel | Set by your host |
The plugin’s setting can never exceed your server’s limit.
Check the file type. Only the formats ticked under Allowed image types are accepted. JPG, JPEG, PNG, GIF and WebP are allowed by default.
Check permissions.
- Members whose role is allowed on the Access tab can upload even if their WordPress role normally cannot. A role manager plugin that removes
upload_filesdoes not stop this, but one that blocks uploads in another way can. wp-content/uploads/must be writable by the web server. Test by uploading in Media > Add New as an administrator. If that fails too, the problem is on the server.
Check the REST API. Uploads go through /wp-json/wbcom-member-blog/v1/upload-image. If /wp-json/ is blocked, uploads fail.
Autosave or draft recovery does not work
Section titled “Autosave or draft recovery does not work”- Check Autosave drafts is on under Editor. It is on by default.
- Autosave uses the REST API, so a blocked
/wp-json/stops it. - The restore prompt appears only when you reopen a published, scheduled or private post that has unsaved changes. A new post or a draft is saved in place, so there is nothing to restore: open it from your Drafts tab.
Autosave never changes a post’s status. On a post that is published, scheduled or private, your unsaved changes are kept aside and offered back when you return, so readers never see half-finished edits.
Formatting looks wrong on the published post
Section titled “Formatting looks wrong on the published post”- Theme styles. Your theme’s CSS may style headings, lists or quotes differently from the editor. Compare with a default theme.
- Removed markup. For security, post content is cleaned when it is saved, so scripts and unsupported HTML are stripped.
- Classic Editor. Make sure you are in the Visual tab, not Text, when applying formatting.
Embeds do not appear
Section titled “Embeds do not appear”The editors embed anything WordPress can embed. Paste the link to a supported service (YouTube, Vimeo and so on) on its own line or into an embed block. If an embed fails, check the same link works in the WordPress block editor.
The editor looks wrong on a phone
Section titled “The editor looks wrong on a phone”On phones the composer has a sticky action bar and a collapsible Post settings section. If the layout looks broken, clear your page cache and CSS optimisation cache, then reload.