Yep – I can confirm that the update (6.8.7) has been applied to the site, but unfortunately, the issue persists and hasn’t been resolved. It’s still showing the same problem.
Could you provide an ETA on the fix? At the moment, we’re unable to use this on the site in question, as this feature was the key differentiator from other solutions. It was working perfectly fine until the recent November update.
Looking forward to your response.
