🇺🇦Ukraine @Kostiantyn

@chauvirea and @thetwentyseven after applying the patch, it will not take effect locally (it is only for the module developer to make changes more easily and quickly).
The patch does not work because when installing dependencies, Composer does not look at the local composer.json file inside the module folder but rather at the one in the remote repository. Therefore, any changes you make to the file: /web/modules/contrib/hubspot/composer.json will not be applied.
You can manually modify composer.lock in your project and change the version of the hubspot-php library (e.g., "hubspot-php": "^5.3") by replacing it with a different version. However, this is a poor solution and should only be done by those who fully understand the implications.

kostiantyn → created an issue.

Hi,
I have the same problem, I think we need to open a ticket again.
Drupal 10.3.0,
Domain Access: 2.0.0-beta2

I’ve created a patch and need a review.

We just need to update the dependencies in the module's composer file to a newer version of the library, as they fixed it.
https://github.com/HubSpot/hubspot-php/pull/420

This patch resolves the issue

need check

kostiantyn → created an issue. See original summary → .

@davidwhthomas Thank you for the comment, this is exactly what I was looking for. I tried to migrate this way, and it worked for me for a while, but I found an issue where migrations fail when all fields are empty. For some reason, skip_on_empty doesn't work as I expect it to.

body/value:
  -
    plugin: skip_on_empty
    method: row
    source: body
  -
    plugin: extract
    source: body
    index:
      - 0
      - value
body/summary:
  -
    plugin: skip_on_empty
    method: row
    source: body
  -
    plugin: extract
    source: body
    index:
      - 0
      - summary
body/format:
  -
    plugin: default_value
    default_value: full_html

Tested, waiting for release.

Kostiantyn → created an issue.

@begrafx You simply need to find the module where this field is used, and disable/enable that module. In my case, the problem disappeared.

I created an issue from version 2.0.0, but for some reason it forked from the 8.x-1.x-dev branch. So, I created another branch and set it up for merge. Please clean up the git, as I don't have access. Thank you.

Kostiantyn → created an issue.

Kostiantyn → created an issue.

I've made the edits.
Please Review it!

Kostiantyn → created an issue.

RTBC

I think we can close the task. There's a duplicate → where the solution is provided with a more accurate description of the module and a file in .md format.

I'm closing this task as it duplicates two previous ones.
task1 →
task2 →
You can compare your solution with the one provided earlier and suggest improvements if any.

I added a README file, creating it from the module description on the page → .

Kostiantyn → created an issue.

fixed, needs review.

Kostiantyn → created an issue.

I added a README file, creating it from the module description on the Drupal.org page. Needs review.

Kostiantyn → created an issue.

Done, needs review.

Kostiantyn → created an issue.

Just finished testing. The filtering works for all fields except for field_adress:state. When the checkbox "Display the State/Province name instead of the state code" is enabled, the filtering for this field doesn't function as expected. It searches based on codes like AO-CNN instead of the actual name (see screenshots), even though it displays the name. If this is not related to this issue, then it can be closed.

I added mr. Please review it.

Kostiantyn → created an issue.

This is not a bug. Closing as a duplicate of another issue
https://www.drupal.org/project/active_menu_item_by_path/issues/3425306 📌 Replace README.txt with README.md Active

I tested the patch from @shashank5563 on Drupal 9.5.11. The error has disappeared.

@Duwid, thank you for your improvement, I am testing it right now.

On Drupal version: 10.2.3, MariaDB version: 10.4, and PHP version: 8.1, everything is working fine. I was able to reproduce the error on Drupal version 9.5.0, but the patch from @shashank5563 successfully resolves it.

Is there a patch available for drupal 8.9? I can't seem to find one. The one for version 9 isn't working for me.

@tuuuukka When I apply the patch, I encounter the error "TypeError: undefined is not an object (evaluating 'drupalSettings.select2.htmlAsText')". The error disappears when I set the configuration for the field, but it's not very convenient to set these settings for every field, even for those where these values are not needed.

+