Problem/Motivation

When a site is installed and built by script, and modules enabled and config set via drush commands, the Scheduler fields for Taxonomy Terms remain hidden. The form display is not updated to show the fields, like it is for node content types.

Steps to reproduce

View a Tugboat build, or install a site locally, including the following

drush pm:enable scheduler taxonomy
drush config-set taxonomy.vocabulary.tags third_party_settings.scheduler.publish_enable 1
drush eval "\Drupal::service('scheduler.manager')->resetFormDisplayFields()"

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Issue fork scheduler-3454624

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

jonathan1055 created an issue. See original summary.

jonathan1055’s picture

jonathan1055 commented

In SchedulerManager resetFormDisplayFields() for some reason, $form_display->isNew() is TRUE for the vocabulary default display, so the loop exits and does nothing.

entityTypeId => taxonomy_term
bundle_id => tags
display_mode => default
form_display => stdClass Object
(
    [__CLASS__] => Drupal\Core\Entity\Entity\EntityFormDisplay
    [entityTypeId:protected] => entity_form_display
    [enforceIsNew:protected] => 1
    [typedData:protected] =>

At the same point in the site build, the node, product and media forms all have isNew() giving 0. I don't know why Taxonomy is different.

jonathan1055’s picture

jonathan1055 commented
Related issues: +#3453345: Update tugboat config

Adding the issue where this problem was discovered.

jonathan1055’s picture

jonathan1055 commented
Title: Scheduler fields for Taxonomy Terms remain hidden when site is built for Tugboat preview » Scheduler fields for Taxonomy Terms remain hidden when site is configured by script (local drush or Tugboat preview )

Modified the title, it is not just Tugboat previews - this happens when configuring a locally-built site using drush commands.

jonathan1055 opened merge request !178

jonathan1055’s picture

jonathan1055 commented

Calling
vendor/bin/drush config-get devel.settings
seems to cause
Timeout (Tugboat Error 1085)

jonathan1055’s picture

jonathan1055 commented

Getting just the single item via
vendor/bin/drush config-get devel.settings debug_logfile
produced no error but also no output in the log.

Then adding a config-set

vendor/bin/drush -y config-set devel.settings debug_logfile 'custom_debug.log'

caused the build to fail.

jonathan1055 closed merge request !178

jonathan1055 reopened merge request !178