Parent setting on Form display cannot be changed for custom Content type

Created on 4 April 2016, over 8 years ago
Updated 28 February 2023, over 1 year ago

Problem/Motivation

Unable to set the parent on a new content type at /admin/structure/types/manage/test/form-display.

Steps to reproduce

On a fresh D8 installation on Ubuntu 14.04, Apache 2.4.7-1ubuntu4.9, php 5.5.9+dfsg-1ubuntu4, using postgresql 9.3+154 and mysql 5.5.35. Drupal is installed at /var/www/drupal8 with the proper user www-data:www-data.

  1. Fresh install Drupal 8.0.5
  2. Create a new Content type: /admin/structure/types/add > Save and Manage Fields
  3. Click on the Manage form display tab
  4. Option 1
    1. Change the Parent setting of the title to content, scroll down and click on Save.
    2. It responds with "Your settings have been saved." but the Parent is unchanged.
  5. Option 2: Expand the title settings by clicking the icon on the right.
    1. Change the Parent setting of the title to content, and click on Update.
    2. This time, it produces an error (log attached):
      PHP Fatal error:  Maximum execution time of ... seconds exceeded in /var/www/drupal8/core/modules/field_ui/sr
      c/Element/FieldUiTable.php on line 67

Proposed resolution

TBD

Remaining tasks

TBD

User interface changes

TBD

API changes

N/A

Data model changes

N/A

Release notes snippet

N/A

πŸ› Bug report
Status

Needs review

Version

10.1 ✨

Component
Field UIΒ  β†’

Last updated 24 days ago

Created by

πŸ‡ͺπŸ‡ΈSpain bezunartea

Live updates comments and jobs are added and updated live.
  • Needs tests

    The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed.

  • Needs issue summary update

    Issue summaries save everyone time if they are kept up-to-date. See Update issue summary task instructions.

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡¦πŸ‡ΊAustralia mstrelan

    As per #3 this doesn't seem to make sense to have in core. Perhaps fieldgroup and other modules can alter this to add support. Attaching a patch to remove the parent column / fields and see what breaks.

  • πŸ‡¦πŸ‡ΊAustralia mstrelan

    Fix phpstan issues

  • Status changed to Needs work over 1 year ago
  • πŸ‡ΊπŸ‡ΈUnited States smustgrave

    This issue is being reviewed by the kind folks in Slack, #needs-review-queue-initiative. We are working to keep the size of Needs Review queue [2700+ issues] to around 400 (1 month or less), following Review a patch or merge request β†’ as a guide.

    Can the issue summary be updated? Makes reference for Drupal 8.0.5, just want to confirm Drupal 10.1.x is still valid. Also some TBD were in there.

    As a bug will need a test case as well.

    Thanks!

  • πŸ‡¦πŸ‡ΊAustralia larowlan πŸ‡¦πŸ‡ΊπŸ.au GMT+10

    Would this not break fieldgroup module pretty hard? Can we just prevent it from erroring as it stands?

  • Status changed to Needs review over 1 year ago
  • πŸ‡¦πŸ‡ΊAustralia mstrelan

    Uploading another patch that should fix the test failures.

    Note that this completely removes the "parent" concept as I haven't be able to find where it's used in core, and I suspect passing tests will reveal that it's not, or it's at least not covered. Fieldgroup would likely need its own customisations to allow for choosing a parent.

Production build 0.71.5 2024