Submitting the form on admin/config/regional/content-language times out because it is enormous

Created on 22 January 2019, about 6 years ago

Updated 16 May 2024, 8 months ago

Problem/Motivation

We have something like 10 content types and ~150 other bundles. Around 120 of the entity/bundle from the whole list are translated.

Once we are at that point the page for management what content gets translated located on admin/config/regional/content-language gets progressively slower current form submission is processed in 50-60 seconds (tracking by browser response time).

Proposed resolution

I think a refactoring is needed to have this single page UI separated to a multi-page solution.

Page 1 - have the content types enabled / disabled with links for the enabled ones to page 2.
Page 2 - have the list of bundles of the entity type just listed on a dedicated page with action links for each.
Page 3 - have a dedicated page to handle single entity/bundle multilingual settings in a small form.

Maybe change the link from field UI that suggest enabling translation to the correct bundle management page (3).

Remaining tasks

Discussion, direction, patch.

User interface changes

TBD. Depends based on the discussion.

API changes

None expected - only UI changes...
Maybe add couple of new forms.

Data model changes

None expected - same config entities.

Release notes snippet

TBD.

🐛 Bug report

Status

Needs work

Version

11.0 🔥

Component

Content translation →

Last updated 4 days ago

No maintainer

Created by

🇧🇬Bulgaria ndobromirov

Live updates comments and jobs are added and updated live.

Performance
It affects performance. It is often combined with the Needs profiling tag.

scalability

Usability
Makes Drupal easier to use. Preferred over UX, D7UX, etc.

Needs issue rescope

Incomplete comments

Comments & Activities

Not all content is available!

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

Comment 8 months ago →
🇫🇷France duaelfr Montpellier, France
@Berdir #15 > The language module provides *only* the entity type + bundle-level setting, that scales fairly well. Only when you also enable content_translation then you get the vast list of per-field-per-bundle checkboxes. Those two things were added at different times, and both pretty early in the D8 lifecycle.

What if we only changed the bit added by content_translation to only add links/buttons in this form leading to a specific page for each entity type? I think we don't even need to split it to a page per bundle to begin with (could be done in a follow up).
Comment 2 months ago →
🇺🇸United States banoodle San Francisco, CA
@duaelfr I like this idea. It is similar to how domain_entity module handles things.

This feature would really help me out ; )

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024