V17.1.0 Block Grid Draft status

Hi All,

I am currently working with the Block Grid and adding content programmatically.
Have no problems adding the content, but every row and column is in some sort of ‘draft‘ status.

What is it? And is there a way to make sure that doesn’t happen?
I also got the same thing when copy and replace from one grid to another grid.

I’ve read about element types being set to vary by culture, but none of them have that option on.

Thanks!

Kind regards,
Puck

Hi @ipsisPuckHolshuijsen

The Expose state is sort of a Published state, which is useful when managing Blocks in a Variant context. — this enables writing new Blocks and publishing them on specific Variants. Because of the data structure they would otherwise have been published on all variants always.

I see that it in its current state has near to no value in a single-variant context, as you properly want your content to be available. — I also dont think you will experience the not-exposed-state when working with Invariant Blocks in the UI.

Anyhow, the example of creating Blocks programmatically in this Docs article describes how to setup the Expose-states, so hopefully that will help you move forward:

Best, Niels

Hi Niels,

Sorry for the late response, but this was exactly what I was looking for.
What I didn’t mention was, that this is an upgraded website from U13 to U17. The internal JSON of the U13 has empty expose arrays, which - when you use that as a base - in turn results in the draft status for the newly copies grid content.

Was able to fix it, and now it works as it should!

1 Like

Good to hear @ipsisPuckHolshuijsen

Then you can mark my comment as the solution, and the thread will be closed off :slight_smile:

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.