#D8MI

Since there's been no follow up, going to close this one out but if still desired task please re-open

Thanks all!

I rerolled a patch from #196 to not break with the Pathauto module.

Pushed a commit to revert the added "void" type and avoid an issue reported in: #3531848.

This small edit to the patch of #74 should make it work on D11 (and still work on D10).

Seems that there's some agreement on #6, which I added to the issue summary.

But as a 11 years older me, I remember lots of pain giving support to customers with hundreds of content types and hundreds of fields which had timeout issues, or POST request size issues on admin/config/regional/content-language. The workaround on that case was hacking the config files (not recommended for not-advanced users), or indicate to go to each content type and each field and mark the relevant checkbox.

So I think content_translation_form_language_content_settings_validate is a much valid approach, and/or even having a config schema validation constraint for this.

Closed [#issues] in favor of this one.

lets track under 📌 Entity configuration form allows to enable translation without any translatable field Active

This looks like it could actually still be a valid task.

Wanted to bump 1 more time before closing.

Feedback appears to be addressed on the MR and CR reads fine and the example helps a lot.