Schlappgosch
Forum Replies Created
-
Hi there,
same thing as to jamesmartindesign happened also to me with version 3.0.6 of BackWPup. I observed this behaviour down to version 3.0.0. on backing up to my ftp server. When the backup directory (ftp/backups in my case) reached the number of allowed backups (20 in my case) those errors and warnings were generated in the report. However, the backup seemed to be correctly written, merely the deletion wouldn’t work.
I employ two groups of backups, a daily one and a weekly one. Two days ago I created two empty(!) subdirectories (ftp/backups/daily and ftp/backups/weekly) and changed the two BackWPup instruction sets accordingly.
Today I observed that multiple daily backups have been created, yesterday five, and today seven bacups have been written. The timestamps were scattered unregularily across the respective mornings. All had status O.K., since the limit of 20 was not yet reached on that directory and consequently, no deletion attempt did occur. It will probably, when the directory reaches the 20 entries.
Strange behavior.
Kind regards
Forum: Plugins
In reply to: [Social Media Tabs] Social Media Tabs – https request to googleapi malformedHi,
I double checked that. I _have_ included my Google + ID in the SMT Widget(!).
Do I have to fill in anoter field than the API Key under the Google + settings?
Thanks very much for the hint. Any other idea?
After my comment above was filed, five days later an overhauled version of BackWPup, version 3.0.5 has arrived – thanks for your effort, Daniel.
However, the version did not solve the problem – I observed the same behavior. In fact, it is worse, becauese now the files that shall be deleted are computed in a wrong way, i.e., not the oldest files are named but the youngest. Strange, there must have gone soemethin badly wrong. Anyone has similar issues?