🇨🇦Canada @francismak

francismak → created an issue.

Patch #75 works for 10.3.6, thank you! Putting more details here.

For our case, we are using a 'or' operator in views when filtering a taxonomy term.
Our config import was working in 10.2, but got error in 10.3.6

The configuration property display.block_1.display_options.filters.field_data_target_id.value.983 doesn't exist.

In the config yml, I removed the values with issues, and replaced with {} instead, and able to import. Then navigate to that view, tried to add back the 'or' filtering to that term and save:

InvalidArgumentException: The configuration property display.block_1.display_options.filters.field_data_target_id.value.983 doesn't exist. in Drupal\Core\Config\Schema\ArrayElement->get() (line 95 of core/lib/Drupal/Core/Config/Schema/ArrayElement.php).

Once patch #75 applied, both import and view saving are now working properly.

francismak → created an issue.

Hi,

We are having the same issue, and the patch #5 is working, thx @gouthamraon.

The "jumping/scrolling" was caused by trying to get the parent element of the dialog.
L1126 of core/misc/ajax.js

Original issue:
Focus state bug on text field AJAX calls 🐛 Focus state bug on text field AJAX calls Fixed

It introduced a new thing "preCommandsFocusedElementSelector". So if refocus back to "Insert Media" button is a problem as mentioned in #11, maybe able to make sure of this new command.

Ideally, it should focus the newly created media inside the CKEditor. However, the element doesn't exist before clicking the button.
And there is nothing to focus if user click 'x' to close the dialog in 3410598 🐛 CKEditor 5: scroll jump after dialog close Active

Instead of focus, I wonder if there is a way to "do nothing".

Thanks @sarwan_verma for doing the MR, this is working as expected. Just not sure if we need another person to verify.

francismak → created an issue.

patch for v2.3.1 based on #45 patch

Hi @lendude, for my use case, I wanted to create a views to show list of content that are belongs to all terms under a vocabulary. And there is no need to expose this filter.

I am able to accomplish this by selecting all the terms and save(which means include all terms).
However, if I create a new term later on, I have to go back to the views and add the new terms to save it.

And after reviewing other's comments, I realized I may mis-understood the usage of 'filter'. Instead of using filter, I should use the "Relationships" to restrict the results from particular vocabulary.

It could be another ticket whether the text "Leave blank for all" is misleading or not. That's an UI issue, but not a defect.

Closing this now, thx everybody.

@josepholstad appreciate your help!! I got it working now, using one entity without hard code language.

Sorry to make this thread becoming a support issue. Just sharing my setup here hope could benefit other users.

So I have my external database table as described in #13.

Apply the patch in this issue, setup external entity. Make sure 2 things.
1. Under the sql queries, select with the langcode field. i.e.
Full object. select id, field1, langcode from {1:samples} where id = :id
List objects. select id, field1, langcode from {1:samples} where TRUE :filters

2. Under field mappings, put the langcode column under the "Language » Language code" field.

Then create Solr search index with the new entity. If there is any field updated, make sure to 'Rebuild tracking information'.

At last, under the views, will be able to filter by "Item Language".

01-mapping

02-views

03-views-preview

Thank you @josepholstad for the instructions, the screenshot is important for me.
After some trial and error, the way I could configure it:

1. Create 2 external entities for both English and French.
2. Then in the Language mapping field, I use '+en' or '+fr' to hardcode my language.
3. Create two separate Solr index for those two languages
4. Create two views for and connect to the Solr index for both languages ...

I think there is no way to dynamically pickup the langcode column from the table.

Hi,

After applying the patch, I am able to see there are 3 new fields in the field mappings:
Language Code
Language Object
Default translation

May I know how to add translations? Let's say I have a custom table:
CREATE TABLE `samples` (
`id` int(11) NOT NULL AUTO_INCREMENT,
`langcode` varchar(12) NOT NULL,
`field1` text,
PRIMARY KEY (`id`)
);

With 2 rows:
id | langcode | field1
1 | 'en' | 'English field1 text'
2 | 'fr' | 'French field1 text'

My goal is to setup the entity, and let Solr index them and provide a views to search the 'field1'.
I am able to setup the field1 mapping using this module, setup the Solr index and created a views with search box to search field1.

However, for multi-language, my views just showing all rows from the above. Even though in my views, I have already added the filter "The item's language" using "Interface text language selected for page".

Thank you.

francismak → created an issue.

Thx for the input. At first I was not sure if this is a particular case for claro theme or not, that's why.
I do agree that make it more generic, could benefit for other users using different theme.

Attached with revised patch.

For our case, we were having a very long URL in the tag. When clicking the 'source' button, the layout break. It only happens to two columns layout in claro.

Unfortunately, the patch above not working in our particular case. Attached our patch for reference.
Tested in Drupal 10.1.4.

francismak → created an issue.

francismak → created an issue.

Thank you, the #26 patch is working. Looking at the original source, I think the issue maybe caused by:

From ajaxGetRemainingTime() in file src/Controller/AutologoutController.php:

    if (isset($active) && $active === "false") {
      $response->addCommand(new ReplaceCommand('#timer', 0));
      $response->addCommand(new SettingsCommand(['time' => 0]));

      return $response;
    }

Just wanted to understand the logic of this module.
Does anyone know why we are not updating the JS timer based on the $_SESSION/$_COOKIE,
but the line above will logout all browser tabs immediately, regardless of activities of other tabs.
Could this be the root cause of the issue we are having?