Have you come across an endless loading spinner when trying to save your work in Thrive Architect or Thrive Leads? This may occur due to an interference of certain security plugins or server configurations.
In this article, we’ll speak about the problem and the possible solutions that will help resolve it at your end.
The Problem
A few Thrive Architect and Thrive Leads Users may come across an “endless loading spinner” when trying to save their work. This is an unfortunate consequence of certain security plugins or server configuration settings.
The Solution
1. Check What’s Causing the Error
If you see the endless loading spinner on the screen, the first step to take is to hit F12 on your keyboard. You can open this by right-clicking anywhere in the viewport and clicking Inspect. This will load a set of options at the bottom or right side of your browser. Then, you should click on Console.
Under the Console tab, you’ll see whether there are any errors. Errors are marked in red. Here is what an internal server error looks like:
- Failed to load resource: the server responded with a status of 500 (Internal Server Error)
If you see the above error, you should know the problem is caused by an internal server error.
Solving the Internal Server Error 500 Issue
There are two primary causes for internal server errors when using a Thrive Themes product.
Security restrictions – Just so data can be saved, Thrive Themes needs to communicate with a WordPress file called admin-ajax.php. Some security plugins and server configurations restrict access to this file, causing an internal server error.
Fix – We recommend you to disable any security plugins temporarily and test again. This will isolate the issue. Please ensure that the yoursite.com/admin-ajax.php file is not blocked and is fully reachable.
The request is too big – Servers have settings that limit the size of data that can be sent to them in a request. Sometimes, if you’re building a big piece of content, this limit may be breached causing an internal server error.
Fix – We recommend you to ask your host to increase one/all of the following limitations:
– max_file_size
– max_upload_size
– MaxRequestLenIf the request is too large for the server then you will commonly see an error like this:-“[Wed Aug 19 11:15:50 2015] [warn] [client 107.145.38.209] mod_fcgid: HTTP request length 131215 (so far) exceeds MaxRequestLen (131072), referer: http://yourdomain.com/?page_id=11913&tve=true“This particular error message shows that the size of the HTTP request length was too big for the server configuration, and that’s what was causing the error.
If you’re still encountering issues, and the endless spinner persists, please also check out this article, which provides some more situations and issues that might cause the endless loading screen to appear.