Hello @hage,
Thank you for contacting us and sorry for any inconvenience that might have been caused due to that.
We have already shared this with our development team. As soon as we get some updates, we’ll make sure to let you know.
We would really appreciate your kind patience regarding this issue.
Hi @rakibuzzamansiam1,
thank you for your reply, and I’m really glad if I’ve been able to help clarify the issue.
Hello @hage,
You’re very welcome, and thank you for taking the time to explain the situation. Your clarification was very helpful and gave us a much better understanding of the issue.
Please do not hesitate to let us know if you need our assistance with anything else.
Thank you.
Hello @jaideeprm and @rakibuzzamansiam1
I’m surprised that this issue has been marked as “resolved”, as the issue still persists.
I have therefore changed the status back to “not resolved”.
Best Regards,
Hans-Gerd
Hello @hage,
Thank you for the update.
That’s perfectly fine. The issue was marked as resolved because it had already been escalated to our development team for further review. However, we understand your concern and have no problem keeping the ticket open.
We will let you know as soon as we have an update from the developers or when a fix becomes available.
Thank you for your patience.
Plugin Support
Miguel
(@miguelrm)
Hello @hage,
We’re glad to let you know that the issue has been resolved internally and it’s due to be fixed in the next stable release of the plugin which is happening next week.
In lieu of that, we are going to close this thread. Feel free to re-open it or create a new one when you have tested the release and report if it’s not properly working on your end.
Thank you.
Hallo @miguelrm
great – thanks for info.
