Hi @snowbedding ,
Thanks for following up!
You’re right — the aioseo_sitemap_localization_disable filter wasn’t working as expected because of where it was being loaded in our code.
Our Development team has already identified the issue (it was tied to the class constructor being instantiated too early) and they’ve pushed a fix for it.
This will be included in our upcoming release, so you’ll be able to use the filter again without needing any special workarounds.
In the meantime, if you’d like to test the fix before the release, I’d be happy to provide you with a beta build. Just let me know and I can share it with you.
Thanks again for bringing this to our attention!
Thank you.
May I know the release date?
Hi @snowbedding,
The fix will be included in our next release, but I’m not able to provide an exact release date at this time. If you’d like, I can share a beta build with you so you can start using the fix right away without waiting for the public release.
Just let me know and I’ll be happy to send it over.
@snowbedding Please do not post email addresses on this site. I have archived your reply.
