Plugin Author
Nick
(@d4d5bh6)
Hi,
Thank you for your explanation.
First, please confirm that “Yes” is selected for the “Accessible via direct link” option under the “Where shall the backup(s) be stored” section. After confirming this, please try downloading a backup again.
If the issue persists, please share the debug code with us. You can generate it by navigating to:
Plugin → Troubleshooting → Check advanced options → “Share the debug information with the BackupBliss team”
Once you click the button, a code will be generated. Please copy it and share it with us.
Additionally, you can download the backup via FTP. The backup files are located in the path shown under the “Where shall the backup(s) be stored” section. Have you tried accessing the files through FTP? If so, please let us know the result.
Hi Nick, the accessible via direct link has “Yes” selected.
Here is the debug code – BMI-s8hrybID-87173.
I’m not sure how to do the FTP part. I’ve never had this problem. Usually, downloading is straightforward. I did add the Backup Migration folder back under the content folder so that it’s there like it should be. I deleted the folder before when I deleted the plugin and added it back.
Thanks for your help.
I just checked the folder that I added back under content and there’s nothig there after doing another backup. No backups, staging, tmp folders, etc.
Hi Nick, Did you find anything in the debug report?
Hi there, again. I figured it out. I reset the plugin. It would be good to have that more visible when you want to reset. I tried multiple times to remove and add the plugin back, but that did nothing.
Resetting took care of everything.
Thanks for repling earlier, and for a wonderful plugin.
Plugin Author
Nick
(@d4d5bh6)
Thank you. Our developers also added:
It appears that after cloning the site, deleting the configuration directory and then restore it. This likely caused an inconsistency in the internal state. I cannot determine the exact root cause due to the lack of full context, but this would explain why resetting the configuration resolved the issue.