Is it possible to disable the automatic publishing of blocks crea

Is it possible to disable the automatic publishing of blocks created directly in content area?

Frank Eller

Vote:

Hi everybody,

We're working with CMS 12.22.3 currently.

I realized that when I create a block directly in the content area, this block is immediately published. The blocks we use do sometimes have other blocks as properties, which in turn contain required properties (that are not shown in the UI, probably because they're inside "nested" blocks).

Those required properties prevent the block from being published, but in this case also from being created.
Our customer does not want the blocks to be immediately published, he prefers to publish them manually (for various reasons).
Also, the editors don't want to create blocks in the sidebar and then drag them over to the content area.

So, the question is, can I disable this behaviour? Or rather, how can I disable this behaviour, because disable it I must somehow.

I hope the answer is not "this is not possible", that would be disappointing ...

Regards,

Frank E.

#312458

Nov 13, 2023 12:28

Ha Bui

Vote:

Hi Frank,

Sorry to hear that but my answer is: No, in the meaning of official functionality (autoPublish always set to true without any customizable).

The reason to do that is simplify process for editor, because the block will created as local asset (under For This Page / Block folders) so many editors complains - very hard to find those ones.

But nothing is impossible please contact our support team (fire an support case) then we can help you more detail.

#312459

Nov 13, 2023 14:19

Frank Eller

Vote:

Hi Ha Bui,

first, thanks for the answer.

I will contact support. However, about three weeks before go-live I will most definitely not upgrade the CMS-version because it's too risky. Looks like we need to disable the validation for the time being.

Please consider in the future to make such features Opt-In/Opt-out, because "many Editors" is not "all editors", and in our case the editors explicitely do want the "old" behaviour.

Regards,

Frank Eller

#312514

Nov 14, 2023 6:10

Ha Bui

Vote:

Thank Frank for your understanding and your very good suggestion! Yes we have a policy here about op-in/out feature considering whenever develop a new one.

But to be fair, this one isn't new (at-least from 2016).

Could you please put your support case number here then I can prioritise it.

Thank you again!

#312519

Nov 14, 2023 8:19

Frank Eller

Vote:

Hi Ha,

thanks a lot. I raised a support case, don't know if I filled out all the fields correctly. The ID is #1280234.

Thanks a lot,

Frank Eller

#312523

Nov 14, 2023 10:25

Ha Bui

Vote:

Thank Frank, I can see the ticket is in our first line support stage, will be hand on this soon and keep you update to date with the status as well as the solution.

Appreciate!

#312525

Nov 14, 2023 10:33

Ha Bui

Vote:

Hi again Frank,

The ticket was sent back to our supports to double check / verify before give you a final answer with solution was added.

Many thanks for your patient!

Ha Bui

#312532

Nov 14, 2023 15:15