Bigul Malayi

Hi @rmcole,

We hope you are now using the latest version of WordPress (7.0). Does this issue occur when all plugins are disabled and the theme is set to the default 2025?

Have you tried disabling the browser extensions? Does the same issue occur with all Post Types, such as Pages or a custom post type?

Also, are there any additional errors in the browser’s Developer Console or WordPress Debug Log? https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/#example-wp-config-php-for-debugging

Hi @petewatterschatsworth,

Just to make sure, are you using the default full-width layout of the Twenty Twenty Five theme? Please refer to this documentation for more details – https://wordpress.com/support/wordpress-editor/change-the-width-of-a-block/

If the issue exists, it would be helpful if you could share a screenshot of the editor showing the block hierarchy (Group → Row → Heading).

Does it happen with a new Page?

Hi @starhorsepax2,

Hope you are using the latest version of WordPress (7.0). This may be a compatibility issue. Please make sure you are using the latest versions of plugins and the theme.

If the issue is occurring, please make sure the bug is reproducible in a minimal setup (by switching to the default WordPress theme and deactivating all plugins). Please take a full site backup before the troubleshooting steps.

Hi @boktoken.

This is possible in WordPress, but the exact steps depend on the theme you are using.

In general, you can create a page and:

1. Set a full-width background image that covers the entire page.
2. Add a Heading block or Text block on top of the image.
3. Adjust the text color, size, and background overlay to ensure it remains readable.

If you are using the Block Editor, you can achieve this with a Cover block:

• Add a Cover block.
• Upload your background image.
• Set the image to cover the entire area.
• Add your text inside the Cover block.
• Adjust the overlay and text color as needed.

Hi @sdarte,

What you are seeing is normal WordPress behavior when it detects a potential filename or slug conflict.

When a file is uploaded, WordPress checks whether the filename or slug is already being used. If it finds a match, it automatically appends -1, -2, and so on to make it unique. Similar behavior occurs with posts and pages, where WordPress adds a suffix to the permalink if the slug is already in use.

Even if the original JPG file is no longer present in the 2026/06 uploads folder, WordPress may still detect a conflict with:

• An existing Media Library item.
• A previously uploaded attachment that used the same filename.
• A post, page, product, or custom post type that has the same slug.
• An image optimization or WebP plugin that modifies uploads.

Could you please check the following?

• Search the Media Library for an existing image with the same filename.
• Check whether there is a post, page, product, or other content with a matching slug.
• Let us know if the WebP files are uploaded directly or generated by a plugin.
• If you are using a WebP or image optimization plugin, try temporarily disabling it and test uploading a new file.

Please let us know what you find. This should help determine whether WordPress is detecting a slug conflict or whether a plugin is modifying the filename during upload.

Hi @xrl8,

Thank you for the clarification. Based on the environment names you mentioned (link, dev, prototype, archive, and syndicate), this appears to be a custom or legacy WCMS rather than a standard WordPress site feature.

As a quick check, look for any Bulk Actions, Select All, or List View options that may allow publishing multiple files at once. You could also check the Prototype environment for any Publish All, Sync, or Reset options.

Since this is a legacy government system, the fastest help will likely come from your agency’s internal web/CMS team or CDC support. If you can share the exact name of the system, we may be able to point you to more specific documentation.

Hi @xrl8,

Please check if your hosting provider offers a staging environment, you may be able to use it to test changes without affecting the live site.

However, if the publishing restrictions are coming from the WCMS platform itself, you may need to check the WCMS documentation or contact their support team for further guidance.

Could you please provide a bit more information?

• Which platform/hosting or application is this prototype environment part of?
• Are all files affected, or only specific ones?
• Do you see any option to reset or recreate the prototype environment?

These details will help us better understand the setup and suggest the most appropriate next steps.

Hi @emmanuelberanger,

It looks like the issue is due to a core file version mismatch in your WordPress installation. Have you migrated the site recently or manually upgraded WordPress?

Try the following steps after a full site backup (especially wp-config.php and the wp-content folder).

• Check your current WordPress version in wp-includes/version.php.
• Download the exact same version of WordPress from wordpress.org.
• Unzip it and replace all files in:
  • wp-includes/ folder
  • wp-admin/ folder
  • Root files (like wp-settings.php, wp-load.php, etc.)
  • DO NOT overwrite wp-config.php or anything inside the wp-content/ folder.
• Clear your browser cache and any site/server cache.

This fixes most cases where core files got mixed up during a manual or failed update.

If it still doesn’t work, try disabling all plugins (by renaming the plugins folder) and switching to a default theme, such as Twenty Twenty Four.

Let me know your current WordPress and PHP versions if the problem persists.

A similar issue: https://stackoverflow.com/questions/79904023/wp-is-valid-utf8-is-undefined-wordpress-6-9-1