Unresolved Component
When copying reference blocks between repositories, you may encounter an "Unresolved Component" error if the referenced target content doesn't exist in the destination repository. This safeguard prevents broken references in your content structure.
What Causes This Error?
References in BaseHub are connections between content blocks. When you copy a reference block to a new repository, it tries to maintain its connection to the original target blocks. However, if those target blocks don't exist in the new repository, the reference becomes "unresolved" and triggers this error.
The error is specifically about missing target blocks - all other blocks of your reference block (including nested children and schema-related components) will copy over correctly. Think of it as a broken link to external content rather than an issue with the reference block's internal structure.
How to Resolve
There are two main ways to fix an unresolved component error:
Clean up the reference: If you don't need the broken reference in your new location, you can simply remove it from the reference block before committing your changes.
Copy the target blocks: If you want to maintain the reference relationship, copy both the reference block AND its target blocks to the new repository. This ensures all necessary content is available and the reference remains valid.
[Image placeholder: Screenshot showing the error message]
[Video placeholder: Demonstration of copying reference and target blocks]
Best Practices
Before copying reference blocks, identify all target blocks they connect to
Consider whether you need the complete reference structure in the new location