Studio Sync 2.11.0: Page Trees Arrive Intact, Big Commits Stop Failing
Studio Sync 2.11.0 fixes page hierarchy syncing (parent slugs now travel with every page) and stops large-theme commits from reporting false timeout failures.
PBJ Studio Sync 2.11.0 is out, and it fixes the two most annoying things we’ve ever caught it doing — both discovered the hard way while pushing a client site full of brand-new pages to production.
Page trees now arrive intact
Studio Sync has always upserted content by slug, because numeric IDs never survive a sync — the receiving site assigns its own. The gap: a page’s post_parent is a numeric ID, and it was never translated. Push a new section like /service-area/ with fifteen child pages under it, and every child landed on live as a top-level page — URLs collapsed from /service-area/wellington/ to /wellington/, breadcrumbs flattened, and anything keyed off the page hierarchy quietly broke.
2.11.0 sends each page’s parent slug alongside it, and the receiver resolves that to its own ID. Children that arrive before their parent — the usual case for a brand-new tree — are queued and fixed at commit, once the whole batch is in. Top-level pages explicitly clear a stale parent, so moves out of a section sync correctly too. The push summary now reports the fixups (parents_fixed), and anything unresolvable surfaces as a run error instead of a silent flat page.
Big commits no longer cry wolf
The commit step is where the live site promotes every staged theme and plugin file into place. With a large theme — a YOOtheme install carries five-thousand-plus cache files — that promote can take longer than the 30-second HTTP timeout the client used for every JSON call. Studio would report “Commit failed: cURL error 28” while live had actually finished the promote seconds later: the work was done, the run was marked failed, and the incremental watermark stayed put, guaranteeing a scary-looking (but harmless) re-push next time.
The commit call now gets its own 150-second budget, sized to real promotes and still comfortably inside the step envelope. Small pushes are unaffected; big ones stop reporting false failures.
Get it
Licensed sites get 2.11.0 through the normal WordPress update flow — no key changes needed, and as always a license only gates updates, never functionality. The full version-by-version history lives on the Studio Sync changelog.