emiliol

debug.txt:

[2014-08-27 17:00:14] Starting backup
[2014-08-27 17:02:30] Completed backup
[2014-08-27 17:02:30] Starting next schedule

Hi Greg,

There’s no debug.txt in archive directory. In fact, there’s no debug.txt in any subdirectory.

Do I have to change the log location?:

class CYANBackup {
        public  $plugin_name = 'CYAN Backup';
        public  $textdomain  = 'cyan-backup';

        private $plugin_basename, $plugin_dir, $plugin_file, $plugin_url;
        private $menu_base;
        private $option_name;
        private $admin_action;
<strong>        private $debug_log = null;</strong>
        private $backup_page;
        private $option_page;
        private $about_page;

Remote storage is not enabled. I tryed but never get it working 🙁

I see the last sentence in scheduled backup function is:

$this->prune_backups( $options['prune']['number'] );

Can I move it to the top of the function, before the backup executes?

Hi Greg,

I have to try it yet in the dev environment. The schedule is working with the hack (and the original code), but the script doen’t delete old backups.

Is there any schedule for deletion that I can “hack”?

Thank you.

Yes, this backup shows up in the list, but after this one the cron job isn’t created.

Hi Greg,

I think CYAN backup and WP cron aren’t working together. Now I see it, after installing one plugin to edit cron jobs.

When I set the schedule using CYAN Backup, the cron job sets properly. When the scheduled backup finishes, the cron job completely disappears and won’t execute anymore.

“Next backup scheduled for:” is set to “None” and WP Cron doesn’t shows any cyan backup hook.

But if I set the backup schedule and, BEFORE it executes, I use WP cron to manually edit the schedule (to hourly, daily or even a custom schedule), then IT WORKS. I can see the hook on WP Cron GUI and the “Next backup scheduled for:” is set properly.

I think it’s working now.

Am I doing it right?

Thank you in advance.