A reliability release for Bedrock sites whose project root isn't directly under the site's files root (moved into its own subdirectory) — a real-world layout that previously went undetected across the app.
Fixed
- Bedrock detection now works at any nesting depth. Detection previously relied on a fixed, shallow search that could miss a nested Bedrock project even though the site worked fine and SpinupWP itself knew it was WordPress. It now anchors on the site's configured Public Folder at any depth, shared across the app:
- The plugins/themes view (
p) finds core correctly instead of reporting "no WordPress core found." - App identification (
d) correctly labels it "Bedrock" again, not just generic WordPress. - The clone wizard's Bedrock pull no longer hardcodes
web/. It re-detects the real project root independently on both source and destination (they're not assumed to match — the destination's layout comes from the git repo's own committed content, not the source's on-disk state), and fails cleanly with a specific message if the two disagree, instead of failing opaquely partway through. A pre-flight check also catches the common case of that mismatch before a destination site is even created. - The Stacks tab's default (pre-probe) "Bedrock" label also recognizes a nested webroot like
site/web, not just an exactweb.
- The plugins/themes view (
- A first-time local Bedrock pull now explains itself. "Pull production → local" (
pin Search) backs up the local database before overwriting it — on a fresh Bedrock checkout with novendor/yet, that step failed with wp-cli's generic "not a WordPress install" error. The message now suggests runningcomposer installfirst when that's the likely cause. - Clone-wizard error messages no longer get cut off at a fixed, often-too-short length. The site roster, Git-access deploy-key list, and DNS cutover roster all truncated errors to a small fixed character count regardless of available space. Errors now fill whatever room the row actually has.
- Onboarding's API token link was a 404. Replaced with generic "Settings → API Tokens" navigation instructions, since the correct URL is account-specific and can't be known before you have a token.
Notes
- Nested Bedrock layouts are now correctly detected in the plugins/themes view, app identification, and the clone wizard's size estimate — all live-tested. A standard (non-nested) Bedrock clone through the rewritten pull chain was also live-tested end to end, including a real DNS cutover. The clone wizard's pull for a nested Bedrock site detects a source/repo mismatch and refuses cleanly before creating anything, but the success path — a genuinely nested repo cloning through to completion — hasn't been live-validated yet. If you hit this, we'd welcome a report.