🇷🇺Russia @_cosmos_

Thanks for patch

Oh thank you @esha_kundu for review!

Oh yes, you are right.
Looks like migrate_upgrade module rename all migrations
and add prefix upgrade_d7_user to d7_user migration

There is no d7_user migration
Rename to upgrade_d7_user

subscribe

There is the path for this issue.

The same error on 1.0.27 of the datafield module.
Really there is no use statement:

use Drupal\Core\Field\FieldTypeCategoryManagerInterface;

there
https://git.drupalcode.org/project/datafield/-/blob/1.x/datafield.module...

error message:
8 18/Jun 13:33 php Ошибка Error: Class "FieldTypeCategoryManagerInterface" not found in datafield_field_type_category_info_alter() (line 267 of /app/web/modules/contrib/datafield/datafield.module) [3e8cd77c-e52d-4b

Installed module
$ lando drush pml | grep datafield
Field types Data Field (datafield) Enabled 1.0.27

Well guys, catch the new feature,
now you can specify the number of links to be displayed in the pager.
Best wishes!

Well, that's good.
Best wishes!

Maybe it would be useful for other devs, as for me.
Keep it there please, I used it in my project.
It worked good.

_cosmos_ → created an issue.

Maybe this module will suit for you 
try it   https://www.drupal.org/project/email_validate  →

_cosmos_ → changed the visibility of the branch 3415229-drush-12-gdpr to hidden.

_cosmos_ → changed the visibility of the branch 3415229-drush-12-gdpr to hidden.

I faced with the same issue on Drupal 10.
Why it was closed?

Drupal\facets\Exception\InvalidQueryTypeException: Query type range doesn't exist. in Drupal\facets\Entity\Facet->pickQueryType() (line 545 of /app/web/modules/contrib/facets/src/Entity/Facet.php).

These changes were applied in new 1.0.5 release of the module.
Checking out the commits https://git.drupalcode.org/project/email_validate/-/commits/1.0.x?ref_ty...

Hello guys,
Thanks a lot for your efforts, all fixes were applied in new 1.0.5 release of the module.
Checking out the commits https://git.drupalcode.org/project/email_validate/-/commits/1.0.x?ref_ty...

Well guys,
Thanks a lot for your time, all fixes was applied in new 1.0.5 release of the module.
Checking out the commits https://git.drupalcode.org/project/email_validate/-/commits/1.0.x?ref_ty...

Hi sunil_lnwebworks,
Thank you for your attention for this issue,
I will apply this path in next minor version soon.

I dont think so, because view is not entity.
You should try this https://www.drupal.org/docs/contributed-modules/twig-tweak-2x/twig-tweak... →

Yes, it would be nice to have an export path field.

We are planning a small upgrade of the tokenlink module soon
and will announce it then in issue in AET module.
I hope it will be a worthy replacement of AET for Drupal >8.

I looked up the AET module and was surprised that they are very similar.

Although, when I developed the tokenlink module, I didn't see the AET module at all.

But despite the similarity of tokens syntax, there are significant differences.

The main idea of my module is to create a list of various template suggestions for token, to manage token rendering flexibility, while AET uses mostly view modes.

Also, we want to be able to write some logic in templates, for example, we want to use different classes for node tokens depends on the node status (published/not published).
Check out the templates for different entity types here https://git.drupalcode.org/project/tokenlink/-/tree/1.0.x/templates?ref_type=heads

I suppose that using the entity view modes is too heavy for token rendering.

However, in the token template, you can implement flexible logic and rendering.

Thanks for your contribution, guys!
When you fix these notices I will create the new release

I 've faced with the same bug, for example I have 2 domains
- Domain 1 has 3 articles
- Domain 2 has 2 articles

Then I created 2 sitemaps here /admin/config/search/simplesitemap
- Sitemap 1 (On Inclusion I set index Content only for sitemap1)
- Sitemap 2 (On Inclusion I set index Content only for sitemap2)

If I run cron from Domain1 I got this:
- Sitemap 1 (indexed 3 articles)
- Sitemap 2 (empty sitemap)

If I run cron from Domain2 I got this:
- Sitemap 1 (empty sitemap)
- Sitemap 2 (indexed 2 articles)

It's always generate sitemap for 1 current domain and remove for others.
But I need to get result like:
- Sitemap 1 (indexed 3 articles)
- Sitemap 2 (indexed 2 articles)

How to get the correct results?

Thanks man!

_cosmos_ → created an issue.

Hi guys,
I am going to create new module which extend the base functional of node token.
The "node_link" would be the most suitable name for this module.
So as you do not maintain your module could you please,
remove your module or give me all access for your module
to start contribute new version.

_cosmos_ → created an issue.

Hello Volker23,
Please describe step by step how to reproduce your case and I will try to fix it

updated

_cosmos_ → created an issue.

Fixed in 1.0.3 version

Moved to RBTC

Hi @Vadim478!
What version of Drupal are you using?
On D10 I didn't catch this error, it works fine.
Anyway, it included in the metatag module, so we can remove this dependency.
But you should know that you need the metatag_views module to override the metatags in views.