Jean-Paul Vosmeer → credited euphoric_mv → .
quietone → credited euphoric_mv → .
Hello,
We are having an issue with that cache tag, entity_field_info .
We have a website where each page is built by the list of multiple entity_subqueues with nodes list.
If we change the order in one sub-queue, it purges the cache for every entity in all pages, as each entity is tagged with that cache tag. That leads us to load everything from DB on each change in any sub-queue.
From my point of view, the EntityQueue entity type only has settings and doesn't have fields so there is no necessary need for the entity_field_info cache tag.
Here's the reasoning:
- Purpose of entity_field_info: This cache tag tracks information about entity fields. If an entity has no fields, there's technically nothing to cache regarding field definitions.
- Cache invalidation: The entity_field_info tag invalidates caches when field definitions change. With no fields, changes to settings wouldn't affect field definitions.
I would like to hear what is your opinion about this and can we maybe merge the patch?
I'm trying to fork the project, but no success. Does anyone has the same problem?
Hi @sudhanjs
Thank you for the reminder. I am working on a porting solution that I implemented in the project in this a contrib module. I will create PR and let you know guys to review it.
Hello @Murz.
I am currently implementing auto-instrumentation on one of our projects, it works fine, so I would like to create a fork and push it next week. I will push it without tests, so you can have just a picture of how it works. Once we agree on an approach, I will add some tests.
@t-lo Thank you
Hi,
We are upgrading Drupal from 9 to 10, and we have to upgrade the Akamai module to version 5, but we have a problem with the version of package akamai-open/edgegrid-client. It requires version ^2.0.5 but the latest version of that package is 2.0.0 and the composer is complaining about that.
Should I create a new issue for that problem?