BugWP logo BugWP
Back to Community
Home / Community / Core → Fixing wordpress

WordPress 6.8 Template Editor Issues: Troubleshooting Guide

29 threads Sep 7, 2025 Core → Fixing wordpress

Content

Many users have reported issues with the template editor after updating to WordPress 6.8. This guide will help you understand the common problems and how to resolve them.

Common Issues After WordPress 6.8 Update

Based on community reports, these are the most frequent template-related problems:

  • Clicking "Site Edit" from the admin bar opens the general site editor (/wp-admin/site-editor.php) instead of the specific template for the current page
  • Template selection appears broken - clicking any template in "All Templates" shows only the "Front Page" template
  • Unable to select empty templates for specific pages
  • Custom template modifications being reverted or cleaned up

Why These Changes Happened

The 'Fixing WordPress' team has indicated that some of these changes are intentional. WordPress 6.8 introduced modifications to the site editor behavior, particularly how templates are accessed and managed. The shift to opening the general site editor rather than a specific template was a deliberate UX change.

Troubleshooting Steps

  1. Verify It's Not a Plugin Conflict
    Temporarily disable all plugins and check if the issue persists. Several users found that security plugins (like Solid Security) or page builders (like Elementor) were affecting template functionality.
  2. Check Your Theme Compatibility
    Test with a default theme like Twenty Twenty-Five to ensure your custom theme isn't causing the issues. Some problems may stem from theme-specific code that needs updating for WordPress 6.8.
  3. Clear Caching
    Clear any server-side caching, CDN caching, or browser caching that might be serving old versions of the editor interface.
  4. Review Template Files in Child Themes
    If using a child theme, ensure your template files follow proper WordPress standards. Some users reported that custom templates in child themes weren't being recognized properly after the update.
  5. Alternative Access Methods
    Instead of using the "Site Edit" button, navigate directly to templates through Appearance → Editor → Templates. Some users found this workaround effective.

When to Consider a Child Theme

For persistent template customization issues, creating a child theme might be your best solution. This ensures your customizations remain intact during theme updates. The proper structure for a Twenty Twenty-Five child theme includes:

  • A style.css file with proper header comment including Template: twentytwentyfive
  • A functions.php file to properly enqueue parent and child theme styles
  • A theme.json file with version 2 and "inherits": true properties

Final Thoughts

While some template editor changes in WordPress 6.8 were intentional, other issues may indicate conflicts with plugins or themes. Following the troubleshooting steps above should help resolve most template-related problems. If issues persist, consider reaching out to your theme or plugin developers for compatibility updates specific to WordPress 6.8.

Related Support Threads Support