Hey. Thanks for the neat module. Was desperately searching for it.

The one thing I was missing for my usecase was to disable the title field. Would be nice to have this feature aswell.

Cheers, Moritz

CommentFileSizeAuthor
#5 3002464-5.patch4.11 KBJeroenT
#5 3002464-5-test-only.patch960 bytesJeroenT
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

shortspoken created an issue. See original summary.

ajay_reddy’s picture

Assigned: Unassigned » ajay_reddy
Status: Active » Needs work
JeroenT’s picture

Assigned: ajay_reddy » Unassigned

It would be nice to support this, but currently I don't have a simple solution for this. But I'm afraid that this wil change the behaviour of this module structurally. Currently we're saving the settings as a third_party_settings on the field config. But afaik, this isn't possible for base fields like a node title, published field, ...

JeroenT’s picture

Version: 8.x-1.x-dev » 8.x-2.x-dev
JeroenT’s picture

Status: Needs work » Needs review
FileSize
960 bytes
4.11 KB

I was thinking again about this one and it was actually pretty simple. There already is a module that creates a ui for editing base fields (https://www.drupal.org/project/base_field_override_ui). When that module is enabled, we add the disable_field config form like on the field_config form. The actual disabling of the fields was already working for base fields.

  • JeroenT committed f83385f on 8.x-2.x
    Issue #3002464 by JeroenT: Use with title field
    
JeroenT’s picture

Status: Needs review » Fixed

Committed and pushed to 8.x-2.x. Thanks!

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.