Hi @pixelcanopy
The subdirectory isn’t the problem here. Both installs point the app to the right REST API address, and the app picks up the /en/ one correctly.
What’s broken is the REST API index on the English install. https://vanity2go.com/en/wp-json/ returns a WordPress critical error (HTTP 500), while https://vanity2go.com/wp-json/ returns the usual JSON. The app reads that index as part of signing in to check that WooCommerce is active. It fails there.
The individual namespaces load fine on their own (/en/wp-json/wc/v3, /en/wp-json/wp/v2), so my read is something fails only when WordPress builds the full index. The PHP error log on that install, or wp-content/debug.log with WP_DEBUG_LOG on, should have the fatal for that request.
Can you please check the log for the fatal from a request to /en/wp-json/ and share it here? If you’d rather go straight to a fix, deactivate plugins on the /en install one at a time until that URL returns JSON, then try the app again.
Hi @pixelcanopy,
We haven’t heard back on this one, so I’ll close the thread for now.
To recap where we left it: the subdirectory itself isn’t the problem. The REST API index on the English install (/en/wp-json/) returns a critical error, and the app reads that index when signing in, so login fails there. The individual namespaces load fine on their own, which points to something breaking only when WordPress builds the full index.
If you pick this up again, the PHP error log — or wp-content/debug.log with WP_DEBUG_LOG enabled — will have the fatal from a request to that URL. Deactivating plugins on the /en install one at a time until /en/wp-json/ returns JSON will get you there too.
Do open a new topic with the log entry if you’d like us to take it further.
If the troubleshooting here was helpful, we’d appreciate a review: https://wordpress.org/support/plugin/woocommerce/reviews/
