Description
Summary
Adding a self-hosted site that uses plain permalinks fails with "Cannot load the WordPress site details" (WordPress/Classes/Login/SelfHostedSiteAuthenticator.swift). An Application Password is successfully issued (it appears in wp-admin → Users → Profile), but the app cannot load site details.
Root cause
The underlying login client (WordPressLoginClient, from Automattic/wordpress-rs) does not handle the ?rest_route= REST API root that WordPress advertises on plain-permalink sites — it path-extends that root into URLs that resolve to the API index. Full analysis + one-line curl reproduction: Automattic/wordpress-rs#1366
Secondary — diagnostics/UX
"Cannot load the WordPress site details" exposes none of the underlying reason. wordpress-rs already models richer failures (e.g. parse_api_root_failure_reason_wordfence_blocking_access); this case yields a silent parse failure with no actionable text. Surfacing the underlying WpLoginError/parse_api_root reason — and, where detectable, hinting at permalink / REST-route configuration — would save real support effort. The current self-hosted troubleshooting guide steers users toward host/firewall/Jetpack causes, which misattributes this bug.
Workaround
See Automattic/wordpress-rs#1366 — server-side rest_url filter + .htaccess rewrite, or enable pretty permalinks.
General Note
I am not a PHP developer or familiar with the low level WordPress code. The above was determined by debugging my system with Claude Code after updating to WordPress 7.0 for my WordPress instance.
Step-by-step reproduction instructions
- Self-hosted site, Settings → Permalinks = Plain.
- App → add self-hosted site → enter URL → authorize the Application Password.
- App shows "Cannot load the WordPress site details."
Screenshots, screen recording, code snippet
No response
Environment info
- Surfaced via WordPress iOS 26.8 on iOS 26.5 on iPad Air (5th Generation)
- Server Apache/PHP 8.3.30, WordPress 7.0, plain permalinks
Please confirm that you have searched existing issues in the repo.
Description
Summary
Adding a self-hosted site that uses plain permalinks fails with "Cannot load the WordPress site details" (WordPress/Classes/Login/SelfHostedSiteAuthenticator.swift). An Application Password is successfully issued (it appears in wp-admin → Users → Profile), but the app cannot load site details.
Root cause
The underlying login client (WordPressLoginClient, from Automattic/wordpress-rs) does not handle the ?rest_route= REST API root that WordPress advertises on plain-permalink sites — it path-extends that root into URLs that resolve to the API index. Full analysis + one-line curl reproduction: Automattic/wordpress-rs#1366
Secondary — diagnostics/UX
"Cannot load the WordPress site details" exposes none of the underlying reason. wordpress-rs already models richer failures (e.g. parse_api_root_failure_reason_wordfence_blocking_access); this case yields a silent parse failure with no actionable text. Surfacing the underlying WpLoginError/parse_api_root reason — and, where detectable, hinting at permalink / REST-route configuration — would save real support effort. The current self-hosted troubleshooting guide steers users toward host/firewall/Jetpack causes, which misattributes this bug.
Workaround
See Automattic/wordpress-rs#1366 — server-side rest_url filter + .htaccess rewrite, or enable pretty permalinks.
General Note
I am not a PHP developer or familiar with the low level WordPress code. The above was determined by debugging my system with Claude Code after updating to WordPress 7.0 for my WordPress instance.
Step-by-step reproduction instructions
Screenshots, screen recording, code snippet
No response
Environment info
Please confirm that you have searched existing issues in the repo.