Hi,
Currently it is not possible to invalidate in the caching plugin for V5 the changes made in the navigation API, unless you invalidate the entire cache, which either happens after the ttl of the element has expired or by manually invalidating the entire cache, an option that can only be performed by someone having the "super admin" role.
Both options are far from ideal, our customers would gain a lot of benefit if also the navigation part of the API could be automatically invalidated , but at this moment we only see the message from the caching plugin: "Webhook runner not present. Contact with Strapi Navigation Plugin team." is this a part that has not yet been migrated from V4? And if so any idea when this migration will take place?
Cheers,
Bart Bakker
Hi,
Currently it is not possible to invalidate in the caching plugin for V5 the changes made in the navigation API, unless you invalidate the entire cache, which either happens after the ttl of the element has expired or by manually invalidating the entire cache, an option that can only be performed by someone having the "super admin" role.
Both options are far from ideal, our customers would gain a lot of benefit if also the navigation part of the API could be automatically invalidated , but at this moment we only see the message from the caching plugin: "Webhook runner not present. Contact with Strapi Navigation Plugin team." is this a part that has not yet been migrated from V4? And if so any idea when this migration will take place?
Cheers,
Bart Bakker