Hello @digitalboutiqueai,
Thank you for bringing this issue to our attention. We are currently working on a resolution. Please bear with us, and I will get back to you with an update as soon as possible.
Best regards,
@mohammedeisa : Thank you for the response.
Cheers.
Hi @digitalboutiqueai,
This is to let you know that our team identified the issue and will resolve it in the next Duplicator version.
Thanks for reporting this issue, and rest assured that we will do our best to launch the next release as soon as possible.
Hi @digitalboutiqueai,
We are actively working on an upcoming release that will include a fix for the issue you’ve encountered.
Thank you for your patience as we finalize this.
Any more information on this?
Hi @digitalboutiqueai ,
Thanks for checking in!
We’re still actively working on the upcoming release that will include this fix. We appreciate your continued patience as we get it ready.
Best regards.
Hello,
I see that version 1.5.16 has been released, which you indicated would contain the fix for this problem, but the release notes on your website have no comments for this version &/or if anything else was addressed.
Many thanks & looking forward to your reply!
Hi @digitalboutiqueai @flight750 @marypop,
This is to notify you that the issue this topic addresses has been resolved in the current Duplicator release.
We apologize for the extended waiting time while we were working on this. Please let me know if you encounter any further issues; I am happy to assist you.
Thank you,
Dear all,
We haven’t heard back from you in a few days, so I’m going to go ahead and close this thread for now. But if you’d like us to assist further, please feel welcome to continue the conversation.
Thanks!
Thank you for the updates on this issue, and “Yes”: in all recent backups (tested in at least 10 sites this week) I no longer encounter this problem. Thank You.
