If Settings > General is blank, spins indefinitely, or will not save, first determine whether the fault is limited to your browser or affects the site. Try a private window or another browser with extensions disabled. If every browser fails, capture the JavaScript and REST errors, check Site Health and WordPress logs, then isolate plugins and the theme. The workflow below gives you evidence-based branches instead of a one-size-fits-all fix.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
1. Separate a browser problem from a site problem
A browser extension, cached script, or privacy setting can stop the administration interface while the site itself is healthy. A failure in every browser points to code or server behavior on the WordPress installation.
As an Amazon Associate I earn from qualifying purchases.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchRun a clean-session test
- Open the dashboard in a private or incognito window.
- Sign in without restoring extensions or previously opened tabs.
- If the page still hangs, test a second browser on the same computer or another device.
- In your normal browser, temporarily disable extensions, especially script blockers, ad blockers, password managers, and developer tools that rewrite pages.
- Reload Settings > General with the browser cache bypassed (for example, a hard reload from the browser’s developer menu).
| Test result | Most likely scope | Next action |
|---|---|---|
| Private window works; normal window fails | Extension, cached asset, or browser setting | Re-enable extensions one at a time, clear the site’s cached data, and identify the interfering extension. |
| Every browser fails for one administrator | Account-specific JavaScript, capability, or session issue | Capture the Console error and test another administrator account if available. |
| Every browser and administrator fails | JavaScript, REST, plugin/theme, PHP, database, or hosting problem | Continue with Console, Site Health, and log checks below. |
WordPress’s browser troubleshooting guidance summarizes the key distinction: “If the issue occurs in all browsers → it is likely a JavaScript or plugin/theme error.” Do not deactivate everything merely because one browser has a problem; prove the scope first.
2. Know what the General Settings screen controls
The screen is more than a title form. It controls the site title and tagline, WordPress and site addresses, administration email, user registration, the site language, timezone, date and time formats, and the day the calendar week starts. A failure can therefore affect both the visible form and requests that supply settings to the editor.
Why the URL fields may be read-only
If WP_HOME is defined in wp-config.php, WordPress uses that constant for the site URL and displays the value without allowing it to be edited on this screen. That is expected behavior, not a loading defect. Change the constant (with a backup and a plan for redirects) rather than trying to edit a locked field in the dashboard. A host, migration tool, or deployment configuration may define the constant outside the database, so check the configuration before changing database values.
3. Capture the browser error before changing the site
A spinner gives no diagnostic detail. The browser Console usually identifies the script, request, filename, and line that failed.
Open Developer Tools and preserve the evidence
- Open Settings > General.
- Open Developer Tools (typically F12 or the browser menu’s More tools > Developer tools) and select Console.
- Enable Preserve log, clear the console, and reload the page.
- Copy the complete error text, the stack trace, the filename, and the line and column number. Also note any failed request shown in the Network panel, including its status code and response body.
- Repeat once in a private window. Keep the two captures separate so an extension error is not confused with a site error.
Record the first meaningful error rather than only the final cascade of messages. A missing JavaScript asset, a syntax error, a blocked REST request, and a permission response require different fixes.
Use unminified core scripts temporarily
Production WordPress normally serves minified JavaScript, which can compress a stack trace into an unhelpful line. Add temporary debugging constants in wp-config.php, above the line that says WordPress is finished editing the file:
define('SCRIPT_DEBUG', true);Save the file, clear any server or browser cache, reproduce the failure once, and capture the expanded filename and line number. Turn SCRIPT_DEBUG off after the investigation; leaving development assets enabled adds unnecessary load and can make later diagnosis confusing.
4. Check Site Health, REST, and loopback requests
Go to Tools > Site Health and review both the Status and Info tabs. Pay particular attention to REST API availability, loopback requests, blocked HTTP requests, and warnings about debugging configuration.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Rank #3
Why REST matters to this screen
The REST settings resource represents values including title, description, url, email, timezone, and date-format fields. If the administration interface is waiting for that resource and the request returns an error, times out, or is blocked, the form can remain blank or keep spinning. In the browser’s Network panel, inspect the settings request (commonly under /wp-json/wp/v2/settings for a logged-in administrator) and record the HTTP status and response.
- 401 or 403: authentication, capability, security software, or nonce problems may be preventing the request.
- 404: a disabled or misrouted REST API, rewrite, or unusual front-end routing can be involved.
- 500 or 502: inspect PHP and web-server logs; the request reached the server but failed while running.
- Timeout or blocked request: investigate loopback restrictions, DNS, firewalls, SSL verification, or host-level outbound HTTP rules.
Understand loopback warnings
WordPress uses loopback requests to run scheduled tasks and verify that the site can call itself. A failed loopback does not prove that the General Settings page is the cause, but it is valuable evidence of a server, authentication, SSL, or plugin conflict. WordPress identifies plugin or theme conflicts as the most common cause of loopback failures. Record the exact URL, error text, and timing shown by Site Health before changing anything.
5. Capture PHP and server evidence safely
When the Console shows a generic failure, temporarily enable WordPress’s file logging and reproduce the issue once. Make a backup of wp-config.php first, then add these constants above the “That’s all, stop editing” line:
define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);
@ini_set('display_errors', 0);
define('SCRIPT_DEBUG', true);Load General Settings once, wait for the failure, and inspect wp-content/debug.log. Match the timestamp and the first relevant stack trace to the Console error. Look for the plugin or theme file named in the trace, a PHP fatal error, a deprecated call that breaks a strict configuration, a database query failure, or a memory exhaustion message.
Recommended Free Tools
Check the host’s logs too
Web-server and PHP-FPM logs can contain errors that WordPress cannot write to its own log, including permission failures, upstream timeouts, rejected requests, and process crashes. Hosting panels often label these as Error log, PHP log, or Web server log. Note the PHP version, WordPress version, request time, and any database or filesystem message when contacting the host or a plugin author.
Disable debugging after capture
Set WP_DEBUG, WP_DEBUG_LOG, and SCRIPT_DEBUG back to false or remove the temporary lines. Keep WP_DEBUG_DISPLAY disabled on a public site. Debug output can expose paths, SQL details, usernames, and other sensitive information; Site Health specifically warns that debug mode may reveal information that should not be publicly available.
6. Isolate plugin and theme conflicts
The official Health Check & Troubleshooting plugin provides the safest dashboard test when you can still sign in. Its troubleshooting mode changes the active plugins and theme only for your session; visitors and other administrators continue to see the normal site.
Use Health Check troubleshooting mode
- Install or open Tools > Site Health > Troubleshooting (the exact menu label depends on the installed plugin version).
- Enable troubleshooting mode for your account.
- With plugins disabled for the session and a default theme selected, open Settings > General.
- If the page works, exit troubleshooting mode or use its component controls to activate one plugin at a time.
- Reload General Settings after each activation. The first activation that recreates the error identifies the component to update, configure, replace, or report.
- If the page still fails in a clean session, the cause is more likely core JavaScript, REST/server configuration, PHP, the database, or hosting rather than an ordinary plugin conflict.
Manual conflict testing
If the troubleshooting plugin cannot run, make a full backup and use a maintenance window. Deactivate all plugins, test the page, then reactivate them individually. If the failure remains with every plugin off, switch to an installed default theme and test again. Do not leave a production site with security, caching, or backup components disabled longer than necessary.
When you are locked out of wp-admin
Use FTP or SFTP (or the host’s file manager) to rename the active theme directory, for example from your-theme to your-theme.disabled. WordPress will fall back to an installed default theme. If General Settings then loads, restore the original directory name and repair or update that theme. If no default theme is installed, upload one compatible with your WordPress and PHP versions before performing the test. Plugin deactivation can also be forced by renaming wp-content/plugins, but that affects every plugin and should be treated as a temporary emergency measure.
7. Match the symptom to the failure class
| Evidence | Likely layer | Practical response |
|---|---|---|
| Only the normal browser fails; private window succeeds | Extension, cached JavaScript, or browser profile | Remove the offending extension or site data; no server change is needed. |
| Console names a plugin or theme file | Plugin/theme JavaScript or PHP integration | Disable that component in troubleshooting mode, then update, reconfigure, or replace it. |
| REST settings request returns 401/403 | Authentication, nonce, capability, firewall, or security rule | Check the administrator session, security rules, and the exact response body; involve the security-plugin or host support if necessary. |
| REST request returns 500/502 and debug.log has a fatal | PHP, database, memory, or incompatible code | Use the named file and line to identify the component; verify PHP and WordPress compatibility and database health. |
| Site Health reports loopback or blocked HTTP requests | Outbound HTTP, DNS, SSL, firewall, or conflict | Compare the reported URL and error with server logs and host restrictions; test with plugins and theme isolated. |
| Page fails with a default theme and no plugins | Core, server, database, permissions, or hosting configuration | Escalate with the complete evidence set instead of repeatedly changing dashboard settings. |
| URL field is visible but cannot be edited | WP_HOME constant |
Change the configuration source deliberately; the dashboard is behaving as designed. |
8. A complete recovery sequence
Use this order to minimize downtime and preserve clues:
- Confirm the symptom in a private window and a second browser.
- Disable extensions and capture the Console, Network request, stack trace, filename, and line number.
- Check whether
WP_HOMEexplains a non-editable URL field. - Review Tools > Site Health for REST, loopback, blocked HTTP-request, and debug warnings.
- Temporarily enable
WP_DEBUG_LOGandSCRIPT_DEBUG, reproduce once, and savewp-content/debug.logplus host PHP/server entries. - Run Health Check troubleshooting mode, or deactivate plugins and switch to a default theme for a controlled test.
- Re-enable one component at a time and stop at the first reproducible failure.
- Restore normal debugging and configuration after capturing evidence.
- Provide the responsible author or host with the exact Console message, REST status and response, relevant log lines, PHP version, WordPress version, and timestamp.
9. When to escalate
Escalate when the page fails in every browser, in a clean troubleshooting session, and with a default theme and no plugins. The official guidance does not identify one universal fix because the same “stuck loading” symptom can originate in JavaScript, REST authentication, PHP, the database, filesystem permissions, exhausted memory, or hosting controls. The captured error is the shortest route to the right owner.
- Send a plugin or theme author the stack trace and the smallest reproducible conflict test, without publishing credentials or full debug logs that contain secrets.
- Send your host the timestamp, REST status, loopback result, PHP version, server-log entry, and whether the failure persists with a default theme and no plugins.
- If a migration or deployment system defines
WP_HOME, correct that source rather than editing the database blindly.
Do not leave troubleshooting mode, renamed directories, disabled security controls, or public debug output in place after the test. Restore the working component set, confirm that General Settings loads and saves, and then perform one final private-window check.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
