Theme Editor Bug

jeremy
(@jeremybassetti)

1 year, 2 months ago

The theme editor seems to be having issues with the new TT5 theme. It seems that all the content blocks have shifted to the top and cannot be edited. This is especially a problem with the other templates (front page, post, etc.), but it is perhaps easier to see with this 404 template. When I click on the list view in the document overview, I see groups that can be selected, but they’re above the editing window and I cannot actually edit them.

It is the editor that is messed up. The actual templates publish fine, as they should. The problem is I cannot edit them.

I tried switching to the TT4 theme and the issue disappears. Moving back to TT5 and the issue comes back. I tried disabling all plugins, different browsers, etc. to no avail.

I’m running WP 6.7.1. I tried reinstalling the update and nada. It seems to be a TT5 issue.

Even the template previews in the all templates list are shifted up and look funny.

Any insights?

Viewing 7 replies - 1 through 7 (of 7 total)

George Appiah
(@gappiah)

1 year, 2 months ago

Can you provide a screenshot of what you describe?

Below is what I see on a FRESH WordPress 6.7.1 installation with the default TT5 theme and no plugin active. Everything works as expected, and I can edit all templates just fine.

I don’t see the problem you describe.

And if something basic like this is broken in such a fundamental way, you can be sure WordPress users would be out there in the streets with their pitchforks 😀

Thread Starter jeremy
(@jeremybassetti)

1 year, 2 months ago

I also had a fresh 6.7.1 installation with the default TT5 theme and no plugin active. This is what I get (zoomed out to emphasize the problem):

And here is the template previews looking weird in the template preview list:

George Appiah
(@gappiah)

1 year, 2 months ago

I can’t reproduce any of this at my end: tested multiple WordPress installations, different browsers, different devices.

Are there any console errors in your browser while editing the TT5 templates?

I’ll recommend testing from a different browser (or if you have just one browser, from a Guest/Private/Incognito profile) to rule out the effects of any local browser/extension interference. If the problem persists, report it in the TT5 theme’s dedicated support forum so the team that knows TT5 best can assist you. https://wordpress.org/support/theme/twentytwentyfive/

Good luck!
Thread Starter jeremy
(@jeremybassetti)

1 year, 2 months ago
No console errors in the browser.

I tried on multiple browsers on different computers/devices. They all produce the error. Therefore, I’ve determined the issue is not within the browser itself but likely in the software/install/server.
- This reply was modified 1 year, 2 months ago by jeremy.
Moderator threadi
(@threadi)

1 year, 2 months ago

Very strange bug you are experiencing. I’ve never seen it like this before. My guess would be either an anomaly with your hosting or a security tool that you have installed on all your devices and which is blocking some files.

Could you please go to WordPress under Tools > Site Health and see if any anomalies are reported there?

Please also post the site info here, which you can find under Tools > Site Health > Info. You are welcome to use the code block here in the forum: https://wordpress.org/support/forum-user-guide/block-editor/#code-block
Thread Starter jeremy
(@jeremybassetti)

1 year, 2 months ago
I have 3 recommended improvements:
1. The scheduled event, recovery_mode_clean_expired_keys, failed to run. Your site still works, but this may indicate that scheduling posts or automated updates may not work as intended.
2. The REST API is one way that WordPress and other applications communicate with the server. For example, the block editor screen relies on the REST API to display and save your posts and pages. The REST API did not process the context query parameter correctly.
3. Loopback requests are used to run scheduled events, and are also used by the built-in editors for themes and plugins to verify code stability. The loopback request returned an unexpected http status code, 404, it was not possible to determine if this will prevent features from working as expected.
Below is the SiteHealth info with the web domain “redacted.”
```
` wp-core

version: 6.7.1
site_language: en_US
user_language: en_US
timezone: +00:00
permalink: /%postname%/
https_status: true
multisite: false
user_registration: 0
blog_public: 1
default_comment_status: undefined
environment_type: production
user_count: 1
dotorg_communication: true wp-paths-sizes

wordpress_path: /home/customer/www/redacted.com/public_html
wordpress_size: 57.03 MB (59798075 bytes)
uploads_path: /home/customer/www/redacted.com/public_html/wp-content/uploads
uploads_size: 608.23 KB (622828 bytes)
themes_path: /home/customer/www/redacted.com/public_html/wp-content/themes
themes_size: 8.03 MB (8415114 bytes)
plugins_path: /home/customer/www/redacted.com/public_html/wp-content/plugins
plugins_size: 99.52 MB (104350695 bytes)
fonts_path: /home/customer/www/redacted.com/public_html/wp-content/uploads/fonts
fonts_size: directory not found
database_size: 1.19 MB (1245184 bytes)
total_size: 166.35 MB (174431896 bytes) wp-active-theme

name: Twenty Twenty-Five (twentytwentyfive)
version: 1.0
author: the WordPress team
author_website: https://wordpress.org
parent_theme: none
theme_features: core-block-patterns, post-thumbnails, responsive-embeds, editor-styles, html5, automatic-feed-links, widgets-block-editor, block-templates, post-formats, editor-style
theme_path: /home/customer/www/redacted.com/public_html/wp-content/themes/twentytwentyfive
auto_update: Enabled wp-plugins-active (2)

Blubrry PowerPress: version: 11.11.1, author: Blubrry, Auto-updates enabled
Minimal Coming Soon & Maintenance Mode: version: 2.42, author: WebFactory Ltd, Auto-updates enabled wp-media

image_editor: WP_Image_Editor_GD
imagick_module_version: Not available
imagemagick_version: Not available
imagick_version: Not available
file_uploads: 1
post_max_size: 256M
upload_max_filesize: 256M
max_effective_size: 256 MB
max_file_uploads: 20
gd_version: 2.3.3
gd_formats: GIF, JPEG, PNG, WebP, BMP, AVIF, XPM
ghostscript_version: 10.02.1 wp-server

server_architecture: Linux 6.6.63-MCIclouder663-c9 x86_64
httpd_software: Apache
php_version: 8.2.27 64bit
php_sapi: apache2handler
max_input_variables: 3000
time_limit: 120
memory_limit: 768M
max_input_time: 120
upload_max_filesize: 256M
php_post_max_size: 256M
curl_version: 8.2.1 OpenSSL/3.1.4
suhosin: false
imagick_availability: false
pretty_permalinks: true
htaccess_extra_rules: true
current: 2025-01-23T14:44:29+00:00
utc-time: Thursday, 23-Jan-25 14:44:29 UTC
server-time: 2025-01-23T14:44:28+00:00 wp-database

extension: mysqli
server_version: 8.0.39-30
client_version: mysqlnd 8.2.27
max_allowed_packet: 33554432
max_connections: 500 wp-constants

WP_HOME: undefined
WP_SITEURL: undefined
WP_CONTENT_DIR: /home/customer/www/redacted.com/public_html/wp-content
WP_PLUGIN_DIR: /home/customer/www/redacted.com/public_html/wp-content/plugins
WP_MEMORY_LIMIT: 256M
WP_MAX_MEMORY_LIMIT: 768M
WP_DEBUG: false
WP_DEBUG_DISPLAY: true
WP_DEBUG_LOG: false
SCRIPT_DEBUG: false
WP_CACHE: false
CONCATENATE_SCRIPTS: undefined
COMPRESS_SCRIPTS: undefined
COMPRESS_CSS: undefined
WP_ENVIRONMENT_TYPE: undefined
WP_DEVELOPMENT_MODE: undefined
DB_CHARSET: utf8
DB_COLLATE: undefined wp-filesystem

wordpress: writable
wp-content: writable
uploads: writable
plugins: writable
themes: writable
fonts: not writable
```
Moderator threadi
(@threadi)

1 year, 2 months ago

The message about the REST API is probably the reason for your problems. The loopback message also indicates a problem, which is probably related to this. The cause is usually a firewall in the hosting that does not allow certain requests through or a missing DNS resolution of your own domain. You would need to discuss this with your hoster’s support team.

However, I see that you have 2 plugins active, including “Minimal Coming Soon & Maintenance Mode”. This in particular could also interfere here and I would recommend deactivating it (and the other one if necessary). If that doesn’t solve the problem, then the support from the hoster certainly will.