Views: Cannot save new translation

Created on 23 March 2017, about 7 years ago
Updated 3 April 2024, 10 days ago

I have a site using views for displaying blocks. My sites has three language. I need to translate the block titles to be displayed when the user switch languages.

I go to the views list and select "Translate" in the Operation column. Then I click the "Add" button for a language, found the block and did my translation.

I found that some of the views work perfectly. However I could not save changes for some of my views. No matter what I translated, then clicking "Save translation" do nothing. The "Add" button of that language remain "Add" (Not the normal "Edit" after the language had been added). And of course the blocks inside that view does not display in the desired language.

I have no idea why some of my views work while some of them don't. Do you have any idea? Thank you.

πŸ› Bug report

Postponed: needs info


11.0 πŸ”₯

Views UIΒ  β†’

Last updated about 12 hours ago

Created by

πŸ‡­πŸ‡°Hong Kong metakel

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

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

  • πŸ‡¦πŸ‡ΉAustria sicher

    Does not work for me on views with many displays, with
    max_input_vars = 5000 or even 10000.

    On "smaller" views I can press "Save Translation" but get:

    Status message
    German translation was not added. To add a translation, you must modify the configuration.

    PHP 8.2.6, Drupal 10.0.9

  • πŸ‡ΉπŸ‡­Thailand manarak

    same problem here.
    my input vars are at 10000

  • Status changed to Postponed: needs info 10 days ago
  • πŸ‡³πŸ‡±Netherlands Lendude Amsterdam

    On a View with about 40 displays but not that many fields I have 8791 input vars, so hitting 10000 doesn't seem impossible, for me it also needed more than 256M of memory to actually load the form in the first place....

    If you add something like

        if (!empty($input)) {
          var_dump(count($input, COUNT_RECURSIVE));

    to \Drupal\Core\Form\FormBuilder::buildForm after $input has been build and then submit the form you can get an indication if this is the problem.

    Either way, we need better steps to reproduce this, because for most Views it works just fine. So for this to be an issue other than #1565704: Core interfaces can go over max_input_vars β†’ , please provide steps to reproduce this with a View that has less than the max_input_vars but still won't save and doesn't give an error message.

Production build 0.62.1