Uppgradering blir ej utförda i “Anpassa, “Block”

Hi Gill,

Both of these errors point to the same underlying cause rather than a theme issue. The Customizer saves your changes as a “changeset” post, and the block editor also writes to the posts table in your database — so when both fail with database insertion errors, it indicates WordPress is unable to write new posts to your database.

This is usually caused by one of the following:

• Disk space — your server or hosting account has run out of storage
• Database size limits — some hosts cap database size, and you may have hit that limit
• A corrupted database table (commonly wp_posts)

I’d recommend reaching out to your hosting provider and asking them to check your available disk space and database status. They can also repair database tables if needed.

You can also try repairing the database yourself by adding this line to your wp-config.php file:

define( 'WP_ALLOW_REPAIR', true );

Then visit yourdomain.com/wp-admin/maint/repair.php to run the repair tool. Remember to remove that line from wp-config.php afterward.

Since this is a server/database-level issue rather than something specific to GeneratePress, your host will be best placed to resolve it.

Hi Gill,

Thanks for passing that along. Since your host has ruled out disk space and database corruption, the next step is to find what’s blocking WordPress from saving.

These errors are most commonly caused by a security plugin, firewall, or another plugin interfering with the save request — rather than the theme itself. To confirm where it’s coming from, could you try the following:

1. Temporarily switch to a default theme (e.g. Twenty Twenty-Four) and try saving a post in the block editor. If the error still happens with a default theme active, it confirms the issue isn’t GeneratePress.
2. Deactivate all plugins except GenerateBlocks and test again. If saving works, reactivate them one at a time to find the culprit. Security plugins (Wordfence, etc.), firewalls, and caching/optimization plugins are the usual suspects.
3. Let me know if you have any security plugin or firewall active, and whether your site sits behind Cloudflare or a similar service.

If the error disappears with a default theme and all plugins off, we’ll know it’s a conflict and can narrow it down from there.

Hi Gill,

Thanks for testing that — it’s a really useful result. Since the error appears even with Twenty Twenty-Five active (a default WordPress theme with no GeneratePress code involved), we now know the cause sits outside the theme itself. That’s an important step forward.

The error “Could not insert post into the database” comes directly from WordPress when something interrupts it writing to the database. With disk space and database health already ruled out by your host, the most likely remaining cause is a plugin or security layer blocking the save.

The clearest way to confirm this is to temporarily deactivate all plugins — including GP Premium — and then test:

1. Deactivate every plugin on the site.
2. Try saving a change in the block editor.
3. Try saving a change in Customize.

If the error disappears with all plugins off, reactivate them one at a time, testing a save after each, until the error returns. The plugin that brings it back is the culprit — security plugins (Wordfence, etc.), firewalls, and caching/optimization plugins are the usual suspects.

One thing to keep in mind: deactivating plugins on a live site can have temporary side effects (for example, a security or caching plugin going offline). If possible, do this during a quiet period, or on a staging copy if your host offers one.

It would also help to know:

• Which plugins you currently have active, especially any security or firewall plugins?
• Whether your site sits behind Cloudflare or a similar service?