Syncing Flaw Needs Fixed
-
My staging site looks correct but syncing to production is not reproducing the staging site accurately — navigation is missing and an incorrect video is displaying on production. I need help understanding why the sync is not working as expected and how to correctly push staging changes to production.
Great question — sync issues like this are usually related to whether the database was included in the sync. The navigation menus and dynamic content like video settings are stored in the database, so if you only synced files (themes/plugins) without including the database, those changes won’t appear on production.
When you push from staging to production, make sure to check the “Include Database” option in the sync modal — that’s what carries over menus, page content, widget settings, and any video configurations.
One important heads-up though: syncing the database will overwrite any content added to production after your last staging sync, so it’s worth double-checking that nothing important was added to production in the meantime. Since your site has a recent backup, you’re in good shape to restore if anything goes sideways.
Want to try the sync again with the database included, and let me know what you see?
MoreSources
Tried again. Video is correct this time but navigation buttons are not appearing on the production site
Good progress on the video! The navigation issue is likely because your theme (Inspiro Blocks) uses the Site Editor for menus, and the navigation block settings are stored in the database — but sometimes the block template parts don’t sync over cleanly.
Can you check on your production site by going to Appearance → Editor → Templates and seeing if the header template looks the same as it does on staging?
MoreSources
In Production see a template entitled front page that does not exist on staging
That’s likely the culprit — the production site has a “Front Page” template that’s overriding your navigation, and since it doesn’t exist on staging, it didn’t get replaced during the sync.
Head to Appearance → Editor on your production site and delete that “Front Page” template — would you like me to walk you through how to do that?
MoreSources
only option is edit
That means it’s one of your theme’s default templates, which can’t be deleted — only reset. Click Edit instead, and then let’s see if we can remove or fix the navigation block directly inside that template. What does the template look like when you open it?
MoreSources
so with this demo i can’t consistently use the staging site to push changes to production?
That’s a fair concern! The sync works well for most changes, but template parts in the Site Editor can sometimes be tricky because they’re stored as custom post types in the database — and if production has templates that staging doesn’t (or vice versa), they won’t always overwrite cleanly.
The most reliable workaround is to make navigation changes directly on production after syncing, rather than relying on the sync to carry them over. Would you like help fixing the navigation in that Front Page template right now?
MoreSources
no but my concern is high that if navigation can’t be pushed reliably from staging that staging is a bust
That’s a completely valid concern — staging is most valuable when you can trust that what you test will match what goes live. For a photography site like yours where the visual presentation is everything, that inconsistency is a real problem.
The good news is that syncing files (plugins, themes) is very reliable — it’s mainly the database/template parts that can get out of sync. So staging still shines for testing plugin updates or theme changes, just less so for navigation tweaks made in the Site Editor.
Since you’re still getting your site set up, would it help to book a personalized onboarding session where a specialist can screen-share with you and map out the best workflow for your specific setup? Or type “connect me to a human” for immediate chat support.
MoreSources
not yet – i need more hands on experience
That makes total sense — getting hands-on is the best way to really understand what staging can and can’t do for your workflow. Feel free to come back anytime you hit a snag or have questions as you explore. Good luck with Thomas Greene Photography!
MoreSources
in conclusion, i should only make navigation changes on production?
Pretty much, yes! For Site Editor navigation changes, go straight to production. Use staging for everything else — plugin updates, theme tweaks, layout experiments — where the sync is rock solid.
MoreSources
so i can reliably create the pages i’ll be navigating to in staging just not the navigation blocks connecting them
Exactly right — create and design your pages in staging, test everything looks good, sync to production, then build out your navigation on production pointing to those pages. That’s a solid workflow for your site!
MoreSources
not happy about that. makes me wonder what else i will run into that doesn’t work with syncing
That’s a fair frustration — and honestly, it’s worth testing as you go rather than assuming. The main gotcha is anything built in the Site Editor (navigation, template parts, global styles) since those live in the database as special post types and can behave unpredictably during sync. Regular posts, pages, media, plugins, and theme files all sync very reliably.
MoreSources
you should fix that
Ha, I wish I could! That’s genuinely good feedback though — if you’d like to share it with the WordPress.com team directly, you can submit it at wordpress.com/forums. Product feedback from real users does make a difference.
The blog I need help with is: (visible only to logged in users)
-
Hi there,
Thank you for reaching out about this!
I understand that syncing from production to staging didn’t reflect the latest changes; however, I’ve had a look around, and after clearing the website cache, I was able to see the latest updates. Could you review this on your end as well now and let me know if you’re missing anything in particular?
Best,
WordPress.com Forums 