octobercms/october · error · SystemException

Unable to find content fieldset definition with UUID of '{$t

Error message

Unable to find content fieldset definition with UUID of '{$this->blueprint_uuid}'.

What it means

Thrown by BlueprintModel's getContentFieldsetDefinition() when BlueprintIndexer::findContentFieldset($this->blueprint_uuid) returns null — no content fieldset is registered for the model's blueprint UUID. Import/export models rely on the content fieldset to know which fields to import or export, so a missing fieldset aborts with a SystemException.

Source

Thrown at modules/tailor/traits/BlueprintModel.php:69

        }

        $blueprint = BlueprintIndexer::instance()->find($uuid);
        if (!$blueprint) {
            throw new SystemException(sprintf('Unable to find import/export blueprint with ID "%s".', $uuid));
        }

        return $this->blueprintCache = $blueprint;
    }

    /**
     * getContentFieldsetDefinition
     */
    public function getContentFieldsetDefinition(): Fieldset
    {
        $fieldset = BlueprintIndexer::instance()->findContentFieldset($this->blueprint_uuid);

        if (!$fieldset) {
            throw new SystemException("Unable to find content fieldset definition with UUID of '{$this->blueprint_uuid}'.");
        }

        return $fieldset;
    }

    /**
     * isEntryStructure
     */
    public function isEntryStructure(): bool
    {
        return $this->getBlueprintDefinition() instanceof StructureBlueprint;
    }

    /**
     * resolveBlueprintModel
     */
    protected function resolveBlueprintModel()
    {

View on GitHub (pinned to b608633a7e)

Solutions

Run php artisan tailor:sync and php artisan cache:clear to register content fieldsets
Verify the blueprint actually defines content fields under its fields: section; add at least one field if it is empty
Confirm the model's blueprint_uuid matches an existing blueprint (see error 755 fixes)

Defensive patterns

Strategy: validation

Validate before calling

// Check the content fieldset exists before importing
$fieldset = \Tailor\Classes\BlueprintIndexer::instance()->findContentFieldset($model->blueprint_uuid);
if (!$fieldset) {
    // sync blueprints or abort with an actionable message
}

Type guard

function contentFieldsetExists(?string $uuid): bool
{
    return $uuid !== null
        && \Tailor\Classes\BlueprintIndexer::instance()->findContentFieldset($uuid) !== null;
}

Prevention

Ensure target blueprints define at least one content field before building importers against them
Run tailor:sync after any blueprint field changes and before running imports
Clear the blueprint cache (php artisan cache:clear) after syncing in production

When it happens

Trigger: Calling getContentFieldsetDefinition() on an import/export model whose blueprint_uuid is null or references a blueprint without content fields; blueprints whose fieldset content was never synced; blueprints with no fields defined at all may also fail to produce a content fieldset.

Common situations: Fresh environments where tailor:sync was not run; blueprint UUID drift after deletion/recreation; importing against a blueprint whose content fields were removed or restructured without a re-sync.

Related errors

AI-assisted analysis of octobercms/october@b608633a7e (2026-08-21). Data as JSON: /api/errors/cdaa10deb7143c5c. Report an issue: GitHub.