Closed (duplicate)
Project:
Drupal core
Version:
8.8.x-dev
Component:
language system
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
22 Aug 2019 at 09:30 UTC
Updated:
22 Aug 2019 at 19:39 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
wim leersI suspect this form was designed in Drupal 6 times, when having so many entity types and/or bundles was unheard of.
More importantly, it also uses a pretty odd design pattern (arguably, no existing design pattern): checking a checkbox for an entity type reveals a huge form for that particular entity type. (Screenshots attached.)
Wouldn't the more elegant way to fix this be to just improve usability and as a side effect fix this scalability problem? I'm thinking vertical tabs, local tasks or something else still.
Comment #3
mikelutzI haven't hit the max input vars limit, but the form is extremely unwieldy, takes a long time to load and save, And I really hate going in there. Could we just break the form up by entity type and bundle?
Comment #4
ghost of drupal pastThanks Wim. Workaround attached. Don't forget to weigh it 11, content_translation seems to be 10 here.
Comment #5
ghost of drupal pastHum,, I should have pushed that into a sandbox or something ... that didn't work 100% but this one does. Same idea: all the submit/validate handlers iterate the
settingsarray so we can just pare it down to one bundle -- except it works now. This is not a proper solution for core but it is a solution for sites like ours which can't save this form. It is also something I wrote in like an hour and all the usual disclaimers apply, there's likely an XSS security hole if you allow untrusted users to label your bundles, blah, blah. We haven't QA'd it properly yet, I will post here when we are done with that -- I fully expect this to go into production next week.Comment #6
ghost of drupal past