Hi Mohamed,
Thanks for your message.
I’ve already replied to your email with a suggested solution.
The second fix for the specific warning you mentioned hasn’t been officially released yet. That said, this issue shouldn’t affect the plugin’s functionality.
Regarding response times: as mentioned on our support page, we’re currently experiencing a higher volume of support requests than usual, which may cause delays. However, we do review and respond to every ticket, and we appreciate your patience, understanding, and compassion.
Since you’re using the paid add-ons, please continue the conversation in the other thread, and I will do my best to help you!
Thank you!
Have a great day!
Best regards,
Hi @assakour ,
Thank you a lot for your patience!
We released a new version today that resolves most of the reported issues, including the error you are getting.
I know some problems took longer to fix than anyone would’ve liked, and I apologize for that. Please note that your experience matters to us, and we want the plugin to be something you enjoy using again.
If you’re still facing any issues, please feel free to reach out to me again.
Thanks again for sticking with us! we’d love to earn back your full trust.
Best regards,
Thread Starter
Med
(@assakour)
Hi,
Thanks for the answer and clarification! I understand!
I updated the plugin, but the issue persists.
Thank you,
Mohamed
Hi @ahmeddr
Maybe you can respond to our support ticket as well. You really seem to have bad support even for licensed customers.
Super-slow support and no bug fixes to known problems – what a pity.
