Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Currently the module doesn't take in account that the entitycache could be flushed during execution and a new sync is necessary.
But the bigger problem is, that there's no way take this in account until this patch for entitycache is applied #1157430: Provide hook_entitycache_reset().
As soon as entitycache is patched the attached patch should do the trick.
Comment | File | Size | Author |
---|---|---|---|
title-reset-cache-on-entitycache-reset.patch | 625 bytes | das-peter | |
Comments
Comment #1
plachWhy don't we just do
drupal_static_reset('title_entity_sync')
here?Comment #2
das-peter CreditAttribution: das-peter commentedAs far as I the code understand we only get the id's of the actually reset entities. This can be just one or multiple. Thus I think this loop is more efficient than reprocessing the sync of all entities.
Comment #3
plachOk, thanks.
Comment #4
plachCommitted to HEAD. Thanks!