Hi @rcain
Thanks for reaching out!
The conflict arises from an older translation library in our plugin, which isn’t compatible with the newer version used by Shield. Unfortunately, due to WP RSS Aggregator v4’s architecture, we can’t update this library without causing more issues.
We’re working on a major update, Aggregator v5.0, which will solve this problem entirely. We expect to release v5.0 around late June this year. We kindly ask for your patience until then.
We understand this might be inconvenient, and we greatly appreciate your understanding.
To directly answer your questions:
- Is there anywhere special that filter needs to go in order to work? No, there’s no special location where the filter needs to be placed.
- Is there any more permanent fix imminent? Yes, a permanent fix is imminent. We’re working on a major update, Aggregator v5.0, which will solve this compatibility issue entirely.
Thank you for your continued support.
Hi Hendra,
Thanks for your reply. I quite understand the problem.
Just to reiterate – the wpra/twig/use_translations filter solution doesn’t seem to work (though I haven’t determined why). The longer code mod solution does work however – which we can live with for the time being 🙂 .
Look forward to the new version later this summer. Great plugin. 🙂
Best regards.