In this article, you’ll learn how to fix common editor loading and editing issues in Thrive Architect. These problems include the editor endlessly loading, inability to edit posts or pages, content that appears locked or uneditable, and the sidebar control panel not displaying. Each issue has specific causes and solutions that you can work through systematically.
Editor issues are almost always caused by plugin conflicts, caching problems, server configuration limits, or browser-related factors. The troubleshooting steps below are organized by symptom so you can quickly identify and resolve the problem.
Fixing Endless Loading of the Thrive Architect Editor
If the Thrive Architect editor gets stuck on a loading screen and never fully opens, follow these steps in order.
Step 1: Clear All Caches
Cached files can contain outdated scripts that prevent the editor from loading correctly.
- Clear your browser cache — go to your browser’s settings and clear cached images and files.
- Clear your WordPress caching plugin cache — if you use a caching plugin (such as WP Rocket, W3 Total Cache, LiteSpeed Cache, or WP Super Cache), navigate to its settings and purge all caches.
- Clear any server-level cache — if your hosting provider uses server-side caching (such as Varnish, Redis, or Nginx FastCGI), purge it through your hosting control panel.
- Clear CDN cache — if you use a CDN like Cloudflare or StackPath, purge the CDN cache from its dashboard.
Step 2: Disable Conflicting Plugins
Other plugins can interfere with the Thrive Architect editor’s JavaScript and prevent it from loading.
- Navigate to Plugins > Installed Plugins in your WordPress admin.
- Deactivate all plugins except Thrive Architect (and Thrive Product Manager if applicable).
- Try loading the Thrive Architect editor again.
- If the editor loads successfully, reactivate plugins one by one, testing the editor after each activation to identify the conflicting plugin.
Common plugins that cause loading conflicts:
- Optimization plugins (such as Autoptimize, WP Rocket, or SG Optimizer) that aggregate or minify JavaScript files
- Security plugins that block inline scripts or restrict AJAX requests
- Other page builder plugins running simultaneously
- Image optimization plugins that modify how assets are delivered
Step 3: Check PHP Memory Limit
Thrive Architect requires sufficient PHP memory to load the editor and process page content.
- Navigate to Thrive Dashboard in your WordPress admin.
- Check the System Requirements or Server Info section for your current PHP memory limit.
- If the PHP memory limit is below 256 MB, increase it by adding the following line to your
wp-config.phpfile:
define('WP_MEMORY_LIMIT', '256M');
- Alternatively, contact your hosting provider and request they increase the PHP memory limit to at least 256 MB.
Step 4: Check Server Configuration
Server settings can prevent the editor from loading if they are too restrictive.
- PHP version — Ensure your server runs PHP 7.4 or higher (PHP 8.0+ is recommended).
- max_execution_time — Should be at least 300 seconds. Low execution times can cause the editor to time out during loading.
- max_input_vars — Should be at least 3000. Complex pages with many elements may exceed the default limit of 1000.
- post_max_size and upload_max_filesize — Should be at least 64 MB to handle large page content.
Contact your hosting provider if you cannot modify these settings directly.
Fixing “Cannot Edit Posts or Pages” Issues
If you can access the WordPress admin but cannot open posts or pages for editing in Thrive Architect, the issue is typically related to permissions, corrupted data, or theme conflicts.
Checking User Permissions
- Navigate to Users > All Users in your WordPress admin.
- Click on your user account and verify that your Role is set to Administrator or Editor.
- If you are using a membership or user management plugin, verify that it has not restricted your editing capabilities.
Note: Only users with the edit_posts capability can use Thrive Architect. If you have a custom role, ensure it includes this capability.
Fixing Corrupted Post Data
If a specific post or page cannot be edited while others work fine, the post data may be corrupted.
- In the WordPress admin, navigate to Posts or Pages and find the affected content.
- Click Edit to open it in the default WordPress editor (not Thrive Architect).
- Check the Revisions section in the right sidebar. If revisions are available, try restoring a previous version.
- If the issue persists, create a new post or page and manually copy the content from the affected one.
Resolving Theme Conflicts
Some WordPress themes override editor functionality or include scripts that conflict with Thrive Architect.
- Navigate to Appearance > Themes in your WordPress admin.
- Temporarily switch to a default WordPress theme (such as Twenty Twenty-Four or Twenty Twenty-Three).
- Try editing the post or page in Thrive Architect.
- If it works with the default theme, your theme is causing the conflict. Contact the theme developer for a resolution, or consider using Thrive Theme Builder as your theme.
Fixing Content That Is Not Editable
If you can open the Thrive Architect editor but certain content on the page cannot be clicked, selected, or modified, follow these steps.
Locked Content
Content may appear locked if it was created using a different editor or plugin.
- WordPress block content — Content created in the WordPress Block Editor (Gutenberg) appears as a single block within Thrive Architect. To edit it, either edit it in the WordPress editor or delete the WordPress content block and recreate it using Thrive Architect elements.
- Shortcode output — Content generated by shortcodes from other plugins renders as read-only in the Thrive Architect editor. You can move or delete the shortcode element, but the shortcode’s output cannot be edited within Thrive Architect.
- Theme-generated content — If you are using Thrive Theme Builder, some areas of the page (such as headers, footers, and sidebars) may be controlled by the theme template. Edit these in the Thrive Theme Builder editor, not on the individual page.
Revision Issues
WordPress auto-saves and revisions can occasionally cause conflicts.
- In the WordPress admin, open the affected post or page in the default editor.
- Scroll down or look in the right sidebar for the Revisions section.
- Review recent revisions and restore a version where the content was editable.
- Save the post and then open it again in Thrive Architect.
If revisions do not resolve the issue, try clearing the Thrive Architect cache:
- Navigate to Thrive Dashboard > Thrive Architect.
- Look for a Clear Cache or Reset option and use it.
Fixing the Sidebar Control Panel Not Displaying
If the Thrive Architect editor loads but the left sidebar control panel does not appear when you select an element, this is most commonly caused by the Autoptimize plugin.
The Autoptimize Conflict
The Autoptimize plugin’s Aggregate JS-files option combines all JavaScript files on the page into a single file. This process breaks the Thrive Architect editor’s JavaScript dependencies, preventing the sidebar panel from rendering.
Solution
- Navigate to Settings > Autoptimize in your WordPress admin.
- Click on the JS, CSS & HTML tab.
- Find the Aggregate JS-files option and uncheck it (disable it).
- Click Save Changes and Empty Cache.
- Clear your browser cache and reload the Thrive Architect editor.
Tip: If you need JavaScript optimization, you can exclude Thrive Architect’s scripts from aggregation instead of disabling the feature entirely. In the Autoptimize settings, find the Exclude scripts from Autoptimize field and add tve_frontend to the exclusion list.
Other Causes
If you do not use Autoptimize but still experience a missing sidebar panel:
- Disable other optimization plugins — Plugins such as WP Rocket, SG Optimizer, Perfmatters, and Asset CleanUp can also interfere with Thrive Architect’s scripts. Disable their JavaScript optimization features or exclude Thrive Architect’s scripts.
- Check for JavaScript errors — Open your browser’s developer console (press F12 or Ctrl+Shift+I, then click the Console tab) and look for red error messages. These can identify the source of the conflict.
- Try a different browser — Test the editor in a different browser (such as Chrome, Firefox, or Edge) to rule out browser-specific issues.
General Troubleshooting Steps
When you encounter any editor loading or editing issue, these general steps can help identify and resolve the problem.
Check the Browser Console for Errors
- Open the Thrive Architect editor on the problematic page.
- Press F12 (or Ctrl+Shift+I on Windows, Cmd+Option+I on Mac) to open the browser developer tools.
- Click the Console tab.
- Look for red error messages. These messages often indicate which plugin or script is causing the conflict.
Try Incognito or Private Browsing Mode
Browser extensions can interfere with the Thrive Architect editor.
- Open an Incognito window (Chrome) or Private window (Firefox/Safari).
- Log in to your WordPress admin.
- Try loading the Thrive Architect editor.
- If it works in incognito mode, a browser extension is causing the issue. Disable extensions one by one to identify the culprit.
Common problematic browser extensions:
- Ad blockers (such as uBlock Origin or AdBlock Plus)
- Script blockers (such as NoScript)
- Privacy extensions that block certain requests
- Translation plugins that modify page content
Deactivate Plugins One by One
- Navigate to Plugins > Installed Plugins.
- Deactivate all plugins except Thrive Architect.
- Test the editor.
- Reactivate plugins one at a time, testing after each, to identify the conflict.
Switch to a Default Theme
- Navigate to Appearance > Themes.
- Activate a default WordPress theme (such as Twenty Twenty-Four).
- Test the editor.
- If the issue resolves, your theme is the source of the conflict.
Frequently Asked Questions
Why Does the Editor Load on Some Pages but Not Others?
This is usually caused by complex page content exceeding PHP memory or server limits. Pages with many elements, large images, or numerous shortcodes require more resources. Try increasing the PHP memory limit and max_input_vars setting.
Can Browser Extensions Cause Editor Loading Issues?
Yes. Ad blockers, script blockers, and privacy extensions can prevent the Thrive Architect editor from loading. Always test in incognito mode to rule out browser extension conflicts.
Does Clearing the Cache Fix Most Loading Issues?
Clearing the cache resolves loading issues caused by outdated scripts or styles. If the problem was introduced by a recent update, clearing all caches (browser, WordPress plugin, server, and CDN) often fixes it immediately.
What if None of These Steps Work?
If you have tried all troubleshooting steps and the issue persists, contact Thrive Themes Support with the following information:
- Your WordPress version and PHP version
- A list of active plugins
- Your theme name and version
- Any error messages from the browser console
- Screenshots or screen recordings of the issue
Related Resources
- Getting Started: Getting Started with Thrive Architect — Overview of the editor interface and requirements
- Common Issues: How to Troubleshoot Common Issues in Thrive Architect — General troubleshooting guide for plugin conflicts, 404 errors, and more
- Display Issues: How to Fix Display and Responsive Issues in Thrive Architect — Fixing horizontal scrolling, display warnings, and responsive layout problems
- Saving and Previewing: How to Save, Preview, and Manage Content — Avoiding save errors and managing content revisions
That’s it! You’ve successfully learned how to fix editor loading and editing issues in Thrive Architect. By systematically clearing caches, checking for plugin conflicts, verifying server settings, and using browser developer tools, you can resolve the vast majority of editor problems and get back to building your pages.