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.

CommentFileSizeAuthor
Capto_Capture 2017-03-24_04-13-00_.png45.97 KBmetakel
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

metakel created an issue. See original summary.

metakel’s picture

metakel CreditAttribution: metakel commented
Version: 8.2.7 » 8.3.7

Version: 8.3.7 » 8.3.x-dev

Core issues are now filed against the dev versions where changes will be made. Document the specific release you are using in your issue comment. More information about choosing a version.

Version: 8.3.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. Branches prior to 8.8.x are not supported, and 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.

amneh.shawish’s picture

amneh.shawish CreditAttribution: amneh.shawish at iHorizons commented

Increase the value of max_input_vars in php.ini file then restart apache.

noelia_11’s picture

noelia_11 CreditAttribution: noelia_11 commented

Works like a charm!!

cilefen’s picture

cilefen CreditAttribution: cilefen commented
Priority: Normal » Major
Issue tags: -translation, -language, -changes not saved
Parent issue: » #1565704: Core interfaces can go over max_input_vars
Lendude’s picture

Lendude
Primary language Dutch
Location Amsterdam
CreditAttribution: Lendude at iO commented
Status: Active » Closed (duplicate)

Thanks for all the feedback everybody.

Closing this as a duplicate of #1565704: Core interfaces can go over max_input_vars, if you feel that this is a separate issue, please feel free to reopen this.

heshamkh’s picture

heshamkh CreditAttribution: heshamkh at Coders Enterprise Web & Mobile Solutions commented

#2 worked for me

sicher’s picture

sicher CreditAttribution: sicher commented
Version: 8.9.x-dev » 10.0.x-dev
Status: Closed (duplicate) » Active

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

Version: 10.0.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. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

DrupalDope’s picture

DrupalDope CreditAttribution: DrupalDope commented

same problem here.
my input vars are at 10000
Drupal 10.2.4
I'm unable to translate the name of a language

Lendude’s picture

Lendude
Primary language Dutch
Location Amsterdam
CreditAttribution: Lendude at iO commented
Status: Active » Postponed (maintainer needs more info)

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));
      die();
    }

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.