Support from Acquia helps fund testing for Drupal Acquia logo

Comments

swentel’s picture

Project: D8 Field API » Drupal core
Issue summary: View changes

Updated issue summary.

larowlan’s picture

Project: Drupal core » D8 Field API
Issue tags: +modal dialog

Tagging

larowlan’s picture

Project: D8 Field API » Drupal core
Version: » 8.x-dev
Component: Code » field system
larowlan’s picture

Assigned: Unassigned » larowlan

Giving this a shot

larowlan’s picture

Status: Active » Postponed (maintainer needs more info)

So the issue here is that the dialog api and jquery.ui insert the elements into the dom as a child of the tag which means they are no longer part of the
tag. Hence submitting the form in the modal doesn't result in the form being rebuilt.
So we have a few options here, none of them too pleasant
1) We use a temp store object for the display entity and each settings form modal is a separate page callback/form that manipulates this temp store object, updating the object used to generate the display overview - only updating the display entity when submitted, this seems the most robust and mimics views, but is fairly involved
2) We use some javascript to close the dialog, attach the elements inside the
tag before the modal form is submitted, this smells hacky to me
3) Leave it as is and avoid the modal

thoughts?

larowlan’s picture

Here's the patch if you want to see what I'm talking about.
And some screenshots.
Screen Shot 2013-03-29 at 5.45.55 PM.png

Screen Shot 2013-03-29 at 5.46.19 PM.png

swentel’s picture

2 is indeed hacky all the way, I don't we'll be able to sell that one, plus I don't like it anyway :)
I'm also not sure whether this works then if you don't have javascript enabled ?

So, a separate callback, using the tempstore, just like all callbacks in views, seems the one that will make sure it works in javascript or non javascript, no.

Additionally, we *could* also use this on manage fields too for the field settings. But let's try one step at the time.

I'm all for it, but I'm not sure, as you mention, how fast we can convert this. Maybe we should talk to the VDC guys how hard this conversion would be/is.

yched’s picture

Status: Postponed (maintainer needs more info) » Needs work

Agreed. The tempstore seems like the most reasonable approach...

swentel’s picture

As an addition, amateescu and I had a talk with Bojhan on IRC and only doing formatters for now is fine. So not for fields as dialog is not for wizards or long forms and a mix of both isn't ideal.

swentel’s picture

Issue summary: View changes

Updated issue summary.

swentel’s picture

Issue tags: +Field API

tagging

swentel’s picture

Issue tags: -Field API

updating tags

larowlan’s picture

Assigned: larowlan » Unassigned
larowlan’s picture

Issue summary: View changes

Updated issue summary.

amateescu’s picture

Component: field system » field_ui.module
Issue summary: View changes
FileSize
2.26 KB

I wanted to check if #2094499: Convert "Manage (form) display" forms to be the official entity edit forms for EntityView[Form]Display objects will be of any help here, but the modal submit buttons are not doing anything (not even closing the modal).

Anyway, here's a reroll on top of #2094499: Convert "Manage (form) display" forms to be the official entity edit forms for EntityView[Form]Display objects if anyone wants to play with it.

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.8.x-dev

Drupal 8.6.x will not receive any further development aside from security fixes. Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.2.x-dev

Drupal 8 is end-of-life as of November 17, 2021. There will not be further changes made to Drupal 8. Bugfixes are now made to the 9.3.x and higher branches only. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.15 was released on June 1st, 2022 and is the final full bugfix release for the Drupal 9.3.x series. Drupal 9.3.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.4.x-dev branch from now on, and new development or disruptive changes should be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.9 was released on December 7, 2022 and is the final full bugfix release for the Drupal 9.4.x series. Drupal 9.4.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.5.x-dev branch from now on, and new development or disruptive changes should be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

tim.plunkett’s picture

Version: 9.5.x-dev » 10.1.x-dev
Issue tags: +Field UX

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.