• Kramarz

    (@kramarz)


    I don’t know where are you at with fixing this new version, but so far… fail.

    I have just followed your advice of starting from scratch.

    I have deleted the plugin, installed again and followed the setup procedure.

    Results and notes so far:

    • I have set the backup of files to monthly and database to weekly
    • backups set run to Dropbox with 15 as a files limit (NOTE – it should still have a separate option for files backups and database backups, for example I may only want to keep 2 files backups, while may need 21 database backups, before old gets removed)
    • I am unable to set the dates, times, and file format anywhere within the settings (it sets it all auto dates, with .tar as file format, while I want .zip)
    • backup for files ran in a loop – 4 times – then it stopped
    • backup for DB didn’t run at all, and I am unable to run it manually. It says – “The job “Database Backup” destination “DROPBOX” is not configured properly” – for whatever reason, and I am unable to fix it
    • here’s the example issue with .tar archive – “WARNING: File name “wp-content/uploads/2024/08/Company-Director-Jailed-for-Illegal-Asbestos-Removal-in-Hampshire-Student-Accommodation-Project-300×153.jpg” is too long to be saved correctly in Tar archive!” – it WILL NOT backup long file names…

    Well… I suppose that’s enough for now… plugin unusable in current state 🙁

    Unless it will all get fixed SOON, I will have to attend almost 200 websites to remove it.

    All the best guys.

    • This topic was modified 1 year ago by Kramarz.
Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support WPM Support

    (@saranshwpm)

    Hi,

    Thank you for reaching out.

    Thanks for taking the time to test a fresh setup and share your detailed feedback. I’ll address each of your points below:

    • Backup file/database retention limits: Currently, the limit applies globally, but I’ll pass along your feedback about having separate retention settings for file and database backups.
    • Custom scheduling & file format: In the free version, backup schedules run at preset times and .tar is used by default. Custom scheduling backups are available in the Pro version.
    • Backup running in a loop: We’re aware of this issue and actively working on a fix.
    • Database backup not running: The error suggests that Dropbox may not be fully configured. Please try re-authenticating Dropbox following this guide: Backup to Dropbox.
    • Long file name warning: We’re aware of this and working on a solution to handle long filenames in .tar archives.

    We truly appreciate your patience. I’ll update you as soon as I have more details on fixes for these issues. Let us know if there’s anything else we can assist with in the meantime.

    Best regards.

    Thread Starter Kramarz

    (@kramarz)

    Re: Database backup not running: The error suggests that Dropbox may not be fully configured. Please try re-authenticating Dropbox following this guide: Backup to Dropbox.

    So far, until 4+ version, separate backups (or example separate files and database backups) required separate authentication with Dropbox. I bet same applies here, if you have 2 separate backups, 2 separate authentications are needed.

    I have already tried to re-authenticate as is, didn’t work.

    Anyway, you are restricting too many of so far freely available options from the plugin, so I guess time to say good bye.

    Thanks for all the years of a great plugin. Wishing you well on your chosen path.

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Plugin just runs backup in a loop’ is closed to new replies.