🔍 What Is Happening
When you bulk select articles in BrandVault and sync them to WordPress, the published posts may display a raw numeric value — such as 16 — in the category field instead of the category name you selected during the sync. This occurs even when the sync popup appears to confirm the correct category was chosen.
This is a confirmed platform bug. Our engineering team has identified the root cause and a fix has been developed, reviewed, and is awaiting release to production.
⚠️ Is This Affecting You Right Now
You are affected by this issue if you notice any of the following after syncing BrandVault articles to WordPress:
- WordPress posts show a number (for example, 16) in the category field instead of a category name.
- The category appeared correct inside the BrandVault sync popup but was wrong after publishing.
- The issue happens consistently when syncing multiple articles in bulk.
📋 What You Should Do Now
Because the fix is currently awaiting deployment to production, the recommended steps are:
- Do not re-sync repeatedly in an attempt to correct the category — this will not resolve the issue and may create duplicate posts.
- Manually update the category on any already-published WordPress posts that are showing a numeric value. Log in to your WordPress admin, open each affected post, and reassign the correct category directly in WordPress.
- Hold off on new bulk category syncs for content where the correct category assignment is critical, until the platform fix has been deployed.
- Check back soon — once the fix is live in production, category names will sync correctly from BrandVault to WordPress without any manual workaround needed.
✅ What Our Engineering Team Has Done
This issue was escalated internally and logged as a confirmed bug: BrandVault → WordPress Content Sync: published posts show numeric category value instead of selected category name. The ticket progressed through full investigation, development, code review, and quality assurance. It is currently at the Awaiting Release stage, meaning the fix is complete and scheduled for deployment to production.
No action is required on your end to receive the fix — it will apply automatically once released.
💬 Need Help With Affected Posts
If you have a large number of posts impacted and need guidance on the fastest way to correct them, or if you want a status update on when the release is expected, our team is ready to help.
If you need further assistance, please reach out to our support team directly and we will be happy to assist you.