🇷🇴Romania @ioana apetri

I am also interested in using the module, but it must have added security advisory coverage. Thanks for considering it!

Hello, I have provided the changes discussed in #24. Thanks

ioana apetri → made their first commit to this issue’s fork.

I'm also having a problem while trying to upgrade from Config Split 1.x to 2.x It seems similar to the current issue - being related to a module dependency in my split (the tmgmt module).
However, this issue seems to be related to how Config Split handles these indirect dependencies.
\Drupal\Core\Config\Entity\ConfigDependencyManager::getDependentEntities not only gets direct dependencies, but also gathers dependencies of those dependencies.

I updated the patch for the Drupal 10.3.x compatibility. Thank you!

Can you provide me more details, how to set up this option? I can't find any 'Data Processing Terms'.
Thank you!

ioana apetri → created an issue.

ioana apetri → created an issue.

ioana apetri → created an issue.

ioana apetri → created an issue.

I managed to fix the 2 of the notices by applying the commit from dev https://git.drupalcode.org/project/tmgmt_cdt/-/commit/902532eabc547bedea... and also I created a patch for what remains.
Deprecated function: Creation of dynamic property Drupal\tmgmt_cdt\Plugin\tmgmt_cdt\Format\TmgmtCdtXml::$mappedItemsIDs is deprecated in Drupal\tmgmt_cdt\Plugin\tmgmt_cdt\Format\TmgmtCdtXml->getMappedItemIds() (line 331 of

Thank you!

ioana apetri → created an issue.

The fix for the issue I described above could be this patch. Can be reviewed?
Thank you!

So far, I've found that if I get rid of the next plus, the normal flow works perfectly.

--- a/src/Plugin/search_api/data_type/DateRangeDataType.php
+++ b/src/Plugin/search_api/data_type/DateRangeDataType.php
@@ -11,7 +11,7 @@
* id = "solr_date_range",
* label = @Translation("Date range"),
* description = @Translation("Date field that contains date ranges."),
- * fallback = "date",
+ * fallback_type = "date",
* prefix = "dr"
* )
*/

ioana apetri → created an issue.

Hello I am facing an issue with the addition of this commit when using custom Filter on date_range fields.

Steps to reproduce:
1. Set the "date range from" value to a specific date, e.g., "2024-03-04T00:00:00Z".
2. Set the "date range to" value as "*"(indicating a undefined range). - the formatFilterValue function returns 0 instead of the value itself.
I believe this case needs to be treated.

Thank you!

Hello,
I have the same issue when trying to add

Has anyone encountered this issue? Thank you!

ioana apetri → created an issue.

I use ddev for lunching the Drupal - version 10.1.4.I am experiencing the same issue, but after clearing the cache it dissapeared. I also cannot indentify why do I have this error in the error logs.

In case JQuery is used, than we need to replase $ sign with JQuery word.If you want to use $ sign you have to use this:
(function ($, Drupal,once, drupalSettings) {

I think also this part $(this).once('init') needs to be changed according the documentation.

Quick fix:

My image is now zoomed in and out with the fallowing code in the "drupal.imagefieldzoom.js" file.

        $(once('init', this)). parent( '.image-zoom'). zoom({
            url: original_urls[$(this).attr('fid')],
            on: drupalSettings.imageFieldZoom.image_zoom_style,
            touch: drupalSettings.imageFieldZoom.image_touchscreen_compatible,
            magnify: drupalSettings.imageFieldZoom.image_magnify,
            duration: drupalSettings.imageFieldZoom.image_fade_duration
          });

Also I modified the dependencies library to be the fallowing:
- core/jquery
- core/drupal
- core/once
- core/drupalSettings

ioana apetri → created an issue.

I also tested MR2 and it worked as expected with no errors. Please merge it as soon as possible. thank you!

I had the same issue when I uninstalled drush.
I use Drupal 9.5.10 and I work to upgrade to D10.
The issue for me is resolved when i resinstalled drush using composer.
Also the Upgrade Status module was installed using composer.
Hope this helps.

I am also waiting for the D10 compatible release. Thank you

When do you plan to release a new version for D10 compatibility?
For now I am using the dev version. Thank you!

I agree with comment #7 that the Context dependency in composer.json is for Context v4.1, which is incompatible with Drupal 10. I cannot update the Context to v5 until the requirement from composer.json of 'Context active trail' is not changed to the proper version.