1. Home
  2. Knowledge Base
  3. Thrive Architect
  4. Troubleshooting
  5. How to Troubleshoot Common Issues in Thrive Architect

How to Troubleshoot Common Issues in Thrive Architect

In this article, you’ll learn how to troubleshoot common issues in Thrive Architect, including general troubleshooting steps, 404 errors, what happens when Thrive Architect is disabled, template save failures, and plugin or theme conflicts. These are the most frequently encountered problems, and each one has a clear resolution path.

Working through these issues methodically — starting with the simplest fixes and progressing to more involved solutions — will resolve the vast majority of problems you encounter with Thrive Architect.

General Troubleshooting Steps

When you encounter any unexpected behavior in Thrive Architect, follow these general troubleshooting steps before investigating specific issues. These steps resolve the majority of problems.

Step 1: Clear All Caches

Outdated cached files are the most common cause of issues after updates or configuration changes.

  1. Browser cache — Press Ctrl+Shift+Delete (Windows) or Cmd+Shift+Delete (Mac) in your browser and clear cached images and files.
  2. WordPress caching plugin — Navigate to your caching plugin’s settings (such as WP Rocket, W3 Total Cache, LiteSpeed Cache, or WP Super Cache) and purge all caches.
  3. Server-level cache — If your hosting provider uses caching (such as Varnish, Redis, or Nginx FastCGI), purge it through your hosting control panel.
  4. CDN cache — If you use Cloudflare, StackPath, or another CDN, purge the CDN cache from its dashboard.

Step 2: Try Incognito or Private Browsing Mode

Browser extensions and stored cookies can interfere with Thrive Architect.

  1. Open an Incognito window (Chrome) or Private window (Firefox/Safari).
  2. Navigate to your WordPress admin and log in.
  3. Test the behavior that was causing the issue.
  4. If the issue disappears in incognito mode, a browser extension or cached cookie is the cause.

Step 3: Disable Plugins One by One

Plugin conflicts are the second most common cause of Thrive Architect issues.

  1. Navigate to Plugins > Installed Plugins in your WordPress admin.
  2. Deactivate all plugins except Thrive Architect and Thrive Product Manager.
  3. Test whether the issue is resolved.
  4. If resolved, reactivate plugins one at a time, testing after each activation, until the issue reappears.
  5. The last plugin you activated before the issue reappeared is the conflicting plugin.

Step 4: Switch to a Default Theme

Theme conflicts can cause layout, display, or functional issues.

  1. Navigate to Appearance > Themes in your WordPress admin.
  2. Activate a default WordPress theme (such as Twenty Twenty-Four or Twenty Twenty-Three).
  3. Test whether the issue is resolved.
  4. If resolved, your theme is causing the conflict. Contact the theme developer or consider switching to Thrive Theme Builder.

Step 5: Check PHP Error Logs

PHP error logs provide detailed information about server-side issues.

  1. Access your hosting control panel (such as cPanel, Plesk, or your host’s custom panel).
  2. Look for an Error Log or PHP Error Log section.
  3. Open the most recent error log and look for entries with timestamps that match when the issue occurred.
  4. Common errors include memory exhaustion (Allowed memory size exhausted), fatal errors from conflicting plugins, and file permission errors.

If you cannot access error logs directly, add the following to your wp-config.php file to enable WordPress debug logging:

define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);

This creates a debug.log file in the wp-content directory. Remember to disable debug logging after troubleshooting by setting WP_DEBUG back to false.

Fixing 404 “Page Not Found” Errors

If pages built with Thrive Architect return a 404 error when accessed, the most common fix is to re-save your WordPress permalink settings.

Why 404 Errors Occur

WordPress uses rewrite rules to translate clean URLs (such as yoursite.com/my-page/) into the actual database queries that load the correct page. These rewrite rules can become corrupted or outdated after:

  • Installing or updating plugins
  • Changing your permalink structure
  • Migrating your site to a new server or domain
  • Updating WordPress core

When the rewrite rules are out of date, WordPress cannot match the URL to the correct page and returns a 404 error instead.

  1. Navigate to Settings > Permalinks in your WordPress admin.
  2. You do not need to change any settings. Simply scroll to the bottom of the page.
  3. Click the Save Changes button.

This forces WordPress to regenerate its rewrite rules. The 404 errors should resolve immediately.

Additional Steps if 404 Errors Persist

If re-saving permalinks does not fix the issue:

  • Check the .htaccess file — Navigate to your site’s root directory via FTP or your hosting file manager. Verify that the .htaccess file exists and contains the standard WordPress rewrite rules. If the file is missing or empty, re-saving permalinks should regenerate it.
  • Check file permissions — The .htaccess file needs to be writable by WordPress. Set its permissions to 644 using your file manager or FTP client.
  • Verify the page is published — In your WordPress admin, go to Pages and confirm the affected page has a status of Published (not Draft, Pending, or Trash).
  • Check for slug conflicts — Ensure the page’s URL slug does not conflict with another page, post, category, or tag that uses the same slug.

What Happens When Thrive Architect Is Disabled

If you deactivate or uninstall Thrive Architect, your page content does not disappear. However, its appearance changes significantly depending on how the page was built.

Regular Posts and Pages

For regular posts and pages that were edited with Thrive Architect:

  • The text content is preserved and displayed using your theme’s default styling.
  • All Thrive Architect styling — custom fonts, colors, backgrounds, spacing, and layouts — is removed.
  • Element-specific layouts (such as columns, content boxes, and background sections) are no longer rendered, so the content displays as plain, linear text.
  • Images embedded in the content are generally preserved, but their positioning and responsive sizing may change.
  • The content reverts to what the WordPress editor displays — essentially a text-only version of your page.

Landing Pages

Landing pages built with Thrive Architect behave differently when the plugin is disabled:

  • Landing pages bypass the theme’s template and rely entirely on Thrive Architect for their layout and styling.
  • When Thrive Architect is disabled, landing pages display a blank page or show only raw, unstyled content because the landing page template is no longer available.
  • If you are considering disabling Thrive Architect, convert any critical landing pages to regular pages first, or ensure you have a plan to recreate them.

Reactivation

When you reactivate Thrive Architect, all pages and content return to their original Thrive Architect design. The content is stored in the WordPress database and is not deleted when the plugin is deactivated.

Fixing “Template Not Saved” Errors

If you receive a “Template not saved” error when trying to save a content template, section template, or page template in Thrive Architect, follow these steps.

Check Your Internet Connection

Template saves require a stable connection to the WordPress server.

  1. Verify that your internet connection is active and stable.
  2. Try loading another page in your browser to confirm connectivity.
  3. If your connection is intermittent, wait for it to stabilize and try saving again.

Check Browser Storage Limits

Browsers have limits on local storage that Thrive Architect uses for temporary data.

  1. Clear your browser’s local storage and session storage — in Chrome, press F12, go to the Application tab, and clear Local Storage and Session Storage for your site’s domain.
  2. Clear your browser’s cookies for your site’s domain.
  3. Try saving the template again.

Try a Different Browser

Browser-specific issues can prevent template saves.

  1. Open your WordPress admin in a different browser (such as Chrome, Firefox, or Edge).
  2. Navigate to the page and try saving the template.
  3. If the save works in a different browser, the original browser may have a corrupted cache or an extension interfering with the save process.

Check for AJAX and REST API Issues

Template saves rely on WordPress AJAX and REST API requests. If these are blocked, saves will fail.

  • Security plugins — Some security plugins (such as Wordfence or iThemes Security) may block AJAX or REST API requests. Temporarily disable security plugins to test.
  • Server firewall — Web Application Firewalls (WAF) such as ModSecurity or Sucuri can block POST requests that look suspicious. Check your server’s firewall logs or contact your hosting provider.
  • .htaccess rules — Custom rules in your .htaccess file may restrict certain requests. Temporarily rename .htaccess to .htaccess_backup and re-save permalinks to generate a fresh file.

Identifying and Resolving Plugin and Theme Conflicts

Plugin and theme conflicts are the most common source of issues with Thrive Architect. A conflict occurs when two or more plugins (or a plugin and a theme) attempt to use the same resources, modify the same functionality, or include incompatible JavaScript or CSS.

Common Conflicting Plugin Categories

The following categories of plugins are most likely to conflict with Thrive Architect:

  • Optimization and caching plugins — Autoptimize, WP Rocket, SG Optimizer, LiteSpeed Cache, Perfmatters, Asset CleanUp. These plugins can break the editor by minifying, combining, or deferring Thrive Architect’s JavaScript files.
  • Other page builders — Elementor, Divi Builder, Beaver Builder, WPBakery. Running multiple page builders simultaneously can cause JavaScript and CSS conflicts.
  • Security plugins — Wordfence, iThemes Security, Sucuri, All In One WP Security. Overly aggressive security settings can block editor AJAX requests.
  • Image optimization plugins — ShortPixel, Smush, Imagify, EWWW Image Optimizer. Some optimize images in ways that interfere with Thrive Architect’s image handling.
  • JavaScript-heavy plugins — Plugins that add significant JavaScript to the admin area or front end, such as chat widgets, analytics dashboards, or popup plugins from other providers.

How to Identify the Conflicting Plugin

Follow the deactivation testing method:

  1. Navigate to Plugins > Installed Plugins.
  2. Make a note of all currently active plugins.
  3. Deactivate all plugins except Thrive Architect and Thrive Product Manager.
  4. Test whether the issue is resolved.
  5. If resolved, the issue is caused by one of the deactivated plugins. Reactivate them one at a time, testing after each activation.
  6. When the issue reappears, the most recently activated plugin is the conflict source.

Resolving the Conflict

Once you identify the conflicting plugin:

  • Check for plugin updates — Ensure both Thrive Architect and the conflicting plugin are running their latest versions. Conflicts are often resolved in updates.
  • Adjust plugin settings — For optimization plugins, exclude Thrive Architect’s scripts from minification, combination, or deferral. For security plugins, whitelist Thrive Architect’s AJAX endpoints.
  • Contact support — Reach out to Thrive Themes Support with the name and version of the conflicting plugin. They may have a known solution or workaround.
  • Find an alternative — If the conflict cannot be resolved, consider replacing the conflicting plugin with an alternative that is compatible with Thrive Architect.

Resolving Theme Conflicts

If deactivating all plugins does not resolve the issue, the theme may be the conflict source:

  1. Switch to a default WordPress theme (such as Twenty Twenty-Four).
  2. Test whether the issue is resolved.
  3. If resolved, the issue is with your theme. Consider using Thrive Theme Builder, which is designed to work seamlessly with Thrive Architect.

Frequently Asked Questions

How Do I Know If My Issue Is a Plugin Conflict?

If the issue disappears when you deactivate all other plugins and returns when you reactivate a specific plugin, it is a plugin conflict. The deactivation testing method described above is the most reliable way to confirm this.

Will I Lose My Content If I Disable Thrive Architect?

No. Your content is stored in the WordPress database. Deactivating Thrive Architect changes how the content is displayed (removing Thrive styling) but does not delete it. Reactivating the plugin restores the original design.

You only need to re-save permalinks when you encounter 404 errors or after making changes that affect URL structures (such as installing a new plugin, changing permalink settings, or migrating your site). It is not something you need to do on a regular schedule.

Can I Use Thrive Architect with Any WordPress Theme?

Thrive Architect is designed to work with most WordPress themes. However, some themes with heavy JavaScript, custom editor overrides, or non-standard WordPress practices may cause conflicts. For the best experience, use Thrive Theme Builder as your theme.

What Should I Include When Contacting Thrive Support?

Provide the following information for the fastest resolution:

  • Your WordPress version and PHP version
  • A list of all active plugins with version numbers
  • Your theme name and version
  • A description of the issue with steps to reproduce it
  • Any error messages from the browser console or PHP error logs
  • Screenshots or screen recordings showing the issue

That’s it! You’ve successfully learned how to troubleshoot common issues in Thrive Architect. By following the general troubleshooting steps, re-saving permalinks for 404 errors, understanding what happens when the plugin is disabled, resolving template save failures, and systematically identifying plugin and theme conflicts, you can keep your Thrive Architect workflow running smoothly.

Was this article helpful?
Yes No

Related Articles

Need Support?

Can't find the answer you're looking for?
Contact Support
>