Simplify your stack and build anything. Or everything.
Schedule a Demo
USE CASES
Headless CMSEnterprise App BuilderHeadless E-CommerceDigital Asset Management
FEATURES
Multi-TenancyWhite LabelLocalizationAccess ControlAuth
CASE STUDIES

See what others are building with Payload.

Browse Case Studies
Build tomorrow’s web with a modern solution you truly own.
PAYLOAD IS FOR
DevelopersMarketing teamsEnterprise companiesAgencies & Consultancies
COMPARE PAYLOAD
Payload vs WordPressPayload vs ContentfulPayload vs SanityPayload vs StrapiPayload vs Directus
AGENCY TESTIMONIAL

"Payload has transformed the way our clients manage content. It's an indispensable tool for any modern agency."

Become a PartnerFind a Partner
Code-based nature means you can build on top of it to power anything.
Resources
DocumentationExamplesTemplatesGitHubReleasesBlogGuides & Tutorials
Community
RoadmapDiscordCommunity Help
Payload Cloud

Deploy your entire stack in one place with Payload Cloud.

LoginCloud Pricing
It’s time to take back your content infrastructure.
Schedule a Demo
Enterprise Features
SSOAI Auto-EmbeddingPublishing WorkflowsVisual EditorStatic A/B testingAI features
Customer Stories
MicrosoftASICSBlue OriginHello BelloTekton
Featured Customer Story

Microsoft chose Payload to tell the world about AI.

Read the case studyBrowse all
LoginGet Started
Community Help

Custom Component Changes Not Enabling Save Draft or Publish Changes

default discord avatar
58bitslast year
2

Posting this here for posterity, and in case anyone else comes across this. In a custom field and field component, changes from

setValue

via

useField

were not 'enabling' the Save Draft or Publish Changes' buttons. Manually calling

setModified(true)

via

useForm

before calling

setValue

solved the issue. This was only occurring when the custom field was used as a field in a block.

  • discord user avatar
    alessiogr
    last year

    This is weird that that's required. Does that happen to every custom field or only with the lexical one?

  • default discord avatar
    58bitslast year

    Yeah - it was a puzzle for sure. And it only happens in our custom Lexical field FieldComponent and only (I believe) when it's part of a block field. I ran out of time trying to debug it - but I did test as much as I could including setting up a test repo, and at one point using the identical field definition, but with a swapped out field component (using a simpler component) and it worked. Heh. In the end

    setModified(true)

    just before

    setValue({...})

    worked fine and apparently without any other side effects and so I've left this as a future 'TODO: Revisit'.

Open

Continue the discussion in Discord

Star on GitHub

Star

Chat on Discord

Discord

online

Can't find what you're looking for?

Get dedicated engineering support directly from the Payload team.