EZPZSolutions

The cron_log error is fixed in 12.02.08. I forgot to remove some experimental code to automatically run a backup after updating a post or page before uploading the 12.02.07 release.

I apologize for the inconvenience.

For those of you who would like to use the old style (0.8.2) it can be downloaded here for manual installation.

Try clearing the backups using the “Clear Backups” button on the control panel. This will reset everything and then try a manual backup.

There’s been a few bugs which should be worked out now, the latest being the core php function bcadd() (PHP 4 , 5) which some servers did not have activated. The latest release, 12.01.26, no longer relies on bcadd() so that issue is resolved.

Large file transfers to Dropbox may be an unresolvable problem. Dropbox API limits http transfer to 300mb. This is overcome by automatically splitting zips over 200MB into smaller pieces and uploading them individually along with a script which can reassemble them on a Windows or Linux computer (Sorry but MAC’s don’t seem to offer a native way to join split binary files). The big issue is servers timing out on large transfers. It’s not a good practice to force a real long timeout setting for any php file because server lockout for TOU violations become a real possibility. I have personally tested EZPZ OCB on sites of 1GB which compressed to approx. 600MB and the transfers worked around 80% of the time.

There are two things which can help on large sites.

1. Exclude folders in the options which contain large static files such as media files. These file do not compress very much if at all when zipped. You probably already have these files stored on your computer so they can be uploaded manually if ever needed.
2. Remove php error logs throughout your site (mostly found in the WordPress root folder and wp-admin) and limit database logs.

   I recently worked on a WP app which had a database of over 3GB! Many hosting provider limit DB’s to 1GB or less. I found 2.2GB of logs from the “Redirection” plugin. That plugin had an option to limit the number of days logs were retained which had been set to forever. Changing this to 10 days made a remarkable improvement in DB size as well as overall site performance.

There’s a new beta version (12.01.21) which has several new compatibility checks that could help determine where the problem lies. You can download it here.

Just remove the old version and upload version 12.01.21. Please let me know if you get any warnings or error messages.

Thanks to everyone for the feedback!

From EZPZ OCB FAQs.

Q: What do I do if EZPZ OCB locks up during a backup?

A: You can abort a running backup which seems to be locked up by clicking on the “Abort” button either in the status bar or on the manual backup page.

If that doesn’t work you can click the “Clear Backups” button on the control panel page. This will stop all backup processes and delete all backup’s and other files used for running a backup. It will not change any of your option settings or affect any files outside the EZPZ OCB plugin.

Now try a background backup to see if it’s a display problem or a backup problem.

Please let me know the results.

Thanks for the feedback.

Please try a background backup and see if it completes. You will see a “Please wait… A background backup is in progress.” message during the backup. The status message should then return to “Ready to backup <Your Blog>”.

You should now have a completed backup. To verify click on “Last Backup” on the control panel and see if the backup is listed.

These steps will help me determine whether it’s just a display issue or something deeper and I’ll better know where to look.

There is no malware in EZPZ One Click Backup.

You can view the Virus Total report on EZPZ One Click Backup v 0.7.0.3 including Kaspersky at https://www.virustotal.com

EZPZ OCB backs up both the files and the database. There should be no conflict.

If you request your hosting provider to activate ZipArchive they should oblige. It should be included with most versions of PHP.

Thanks for pointing that out. I’ll fix that in the next release.

You can edit pages/ezpz-ocb-backup.php line number 199
$short_path = str_replace(ABSPATH, "", $save_path . "/" . $tar_name);

and change it to:
$short_path = str_replace(ABSPATH, "", $save_path . "/" . $zip_name);
and the problem should be resolved.

Sorry about that, Please upgrade to version 0.5.1.1

There was a problem with the auto updating of the news and FAQ pages. The problem has been resolved in the new version.

Are you getting a “white” screen, completely blank, or is the WordPress admin screen showing with no content between the header and footer?

I would first recommend reinstalling the plugin in either case, you may have a corrupt file somewhere in it.

It is stated under the description tab.

Like most applications EZPZ OCB has certain limitations and requirements. First and foremost, EZPZ OCB only works on Linux servers running PHP 5 and above…

We will include a pre-installation test in future releases which will halt the installation and issue a warning if it’s on a Windows server or the functions exec or mkdir have been disabled by the hosting provider.

We’ll add the datestamp format in the next release. As for the multiple backups, that’ll probably take a little longer.

To exclude the “wp” folder try wp/ which should keep the wp- folders included.

I will change the instructions where it says not to use trailing slashes.

Are you running on a Linux server? “Unable to fork” appears to be mostly associated with Windows servers. (See Google results) EZPZ OCB is not compatible with Windows servers.

If you are on a Linux server it appears mkdir and exec may have been disabled by your hosting provider.