Malae

Hi Mark,
Further to my post above, I have another issue. Wordfence is reporting that my updraft.php version 1.8.5 is differing from the original version. However, it shows the original version as 1.8.6, which is a development version not yet available though the regular WordPress updating process. Can you explain how and why Wordfence finds this newer version.

Hi David,

I have encountered this issue several times with various plug-in files and fortunately there is a Wordfence facility to compare the files side by side and I can usually ignore warnings that indicate differences of no consequence. I have also contacted Wordfence about these issues. Are the latest official versions not stored in the WordPress repository?

In this case it is showing me a new version 1.8.6 of updraft.php with many changes. I presume it is a development version, not yet released officially as an update. If you can confirm this, I would be curious to learn how it is accessed by Wordfence.

Hi Mark,
The above issue (see also below) has occurred again with a different file, same plug-in on a different site. However, this time if I use click here to clear all ignored issues and remove, it comes back after rescanning. Note this site running WordPress 3.8.

The two panels below show a before and after view of a file on your system that has been modified. The left panel shows the original file before modification. The right panel shows your version of the file that has been modified. Use this view to determine if a file has been modified by an attacker or if this is a change that you or another trusted person made. If you are happy with the modifications you see here, then you should choose to ignore this file the next time Wordfence scans your system.
Filename: wp-content/plugins/updraftplus/backup.php
File type: Plugin File
Plugin Name: UpdraftPlus – Backup/Restore
Plugin Version: 1.8.5

There are no differences between the original file and the file in the repository.

Was able to work around the problems previously. However, on my present site displays text, but will not display the date. Tried modifying the plugin.php and footer.php without success. No support, gave up!

Hi Mark,
I rescanned and the warning still occurred.
I updated Wordfence with new version 3.8.9 (today’s), rescanned and the warning still occurred.
I updated the Updraftplus with new version 1.8.2 (today’s) rescanned and the warning still occurred.
I updated WordPress with new version 3.8 (today’s), rescanned and the warning still occurred.
I checked the details and noted that it was reporting that the file was for Updraftplus version 1.7.41 (previous version), but viewing the file, it said it was updated today!
I deleted the notification warning in the ignored file tab and rescanned and it did not reappear. So the issued has disappeared! ??

Hi David,

I tried 776, but only 777 works. I have a similar issue with the attachments folder for a Contact Form. I now know to reset the permissions after each update of that plug-in.

It appears that my hosting has recently updated from Plesk Panel 9.5.4 to 10.4.4. It seems there are still issues, as I can’t access the tools or my database. Perhaps the permissions are linked the the Plesk settings. Hopefully the issues will be resolved soon.

Thanks for your excellent support.

Out of curiosity, what would have changed the permissions, which were ok until this problem? Was it the Updraft update or WordPress update to 3.7.1? Previous Updraft updates did not cause a problem.

The backup apparently succeeded (with warnings) and is now complete (Nov 06 23:12:25)

log file #2 per pastebin URL: https://pastebin.com/JAHqyGCe

If OK please advise any further action needed. Thanks in advance. Bed time now!

Have just changed the permissions on the Updraft directory from 775 to 777 and the Backup Now button is no longer ‘blued out’. Will try a back up. Is this the correct directory and setting?

Looking down the page, the backup directory is updraft.

The text below this is:

“Backup directory specified exists, but is not writable. Click here to attempt to create the directory and set the permissions, or, to reset this option click here. If that is unsuccessful check the permissions on your server or change it to another directory that is writable by your web server process. This is where UpdraftPlus will write the zip files it creates initially. This directory must be writable by your web server. It is relative to your content directory (which by default is called wp-content). Do not place it inside your uploads or plugins directory, as that will cause recursion (backups of backups of backups of…).”

I assume the above does not apply to backups made to Google Drive. I made no changes to the settings and apparently the backups worked fine up until the last Updraft update.

I am backing up to Google Drive with two current backups totalling only 159 MB.

I don’t recall the exact time of the backup. I updated yesterday, but because the backup that ran yesterday was automatic, it may have been before the update. Sorry that my feeling of the time yesterday was somewhat dulled after having spent more than 20 hours flying and changing time zones the previous day.

The Update Now button has light blue text and does not respond, but will try your suggestion.

I am already running version 1.7.35

FYI, I had problems earlier to log on to my site, previous to this issue. Later I tried to access the server via Plesk and it appears that Plesk has recently been updated. I could not access my database and advised my hosting. I have just received an e-mail, quote: “We are currently working on the issue that is impacting your site”, but no explanation of what the issue is. Possibly it is related to the backup issue.

Entire log file pasted into pastebin, URL: https://pastebin.com/qhBNna9w

Hi David, Your prompt response is much appreciated. I am posting the most recently modified the log file:

0000.000 (0) Opened log file at time: Mon, 04 Nov 2013 08:30:17 +0000
0000.002 (0) UpdraftPlus WordPress backup plugin (https://updraftplus.com): 1.7.34 WP: 3.6.1 PHP: 5.3.3 (Linux host.hostingforlife.com 2.6.18-194.26.1.el5PAE #1 SMP Tue Nov 9 13:34:42 EST 2010 i686) MySQL: 5.0.95 Server: Apache/2.2.3 (Red Hat) safe_mode: 0 max_execution_time: 900 memory_limit: 256M (used: 19.3M | 22.5M) multisite: N mcrypt: N ZipArchive::addFile: Y W3TC/ObjectCache: N
0000.003 (0) Free space on disk containing Updraft's temporary directory: 105640.2 Mb
0000.007 (0) Tasks: Backup files:  (schedule: weekly) Backup DB: 1 (schedule: weekly)
0000.008 (0) Processed schedules. Tasks now: Backup files:  Backup DB:
0000.010 (0) Decremented the semaphore (fd) by 1
0000.011 (0) Semaphore (fd) still locked
0000.012 (0) No email will be sent - this backup set was empty.
0000.013 (0) The backup apparently succeeded (with warnings) and is now complete

I will paste the entire file in to pastebin later unless you advise otherwise.