Skip to content

Support creating Content that varies by culture #54

@OwainJ

Description

@OwainJ

I was trying out the MCP Server today, and ran into issues where it could not create any content on my test site and reported a Content type culture variance mismatch exception when attempting to create content.

Looking at the source code for the create-document tool, I can see that the Culture value is currently being hardcode as null in the payload that's sent to the Management API:

variants: [
{
culture: null,
name: model.name,
segment: null,
},
],

I imagine proper support for variants is planned, but thought I'd just raise an issue just in case this was missed.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions