Steve Cliff

I’m not expert at all on this but AFAIK the “|” character is the or, so shouldn’t the last section of your filter be:

(mail=%s)|(uid=%s)

As I said – no expert though – I could be wrong ??

• This reply was modified 7 years, 3 months ago by Steve Cliff.

OK, no worries – thanks for confirmation.

Steve.

Just updated one of my live sites – all working fine ??
Can’t spot box toggle but the text you now have in “S3 Region” makes absolute sense and nice and easy to understand – so all good from me!

Yet again – thanks for an awesome level of support – *the* best backup plugin for WordPress and one that I make sure to tell people about.

Resolved

Hi – thanks for the info – if pointed me in the right direction. My site is running under HTTP but behind an Nginx reverse proxy that holds the SSL cert. I’d forgotten to update my site to show that it was accessed by https not http, hence I had the following error:

The page at ‘https://slimming.familycliff.co.uk/’ was loaded over HTTPS, but requested an insecure stylesheet ‘https://slimming.familycliff.co.uk/wp-content/uploads/form-maker-frontend/css/fm-style-52.css?ver=1’.

Changing the site settings to HTTPS made the request for the stylesheet as HTTPS too and the problem went away. I’m presuming that older versions of your plugin did this differently as I hadn’t had the problem before.

Either way, just for clarification – your plugin is working fine and was not at fault.

Thanks for the response.
Steve.

Works really well Liuta – no problems that I’ve found – good work! ??

Some minor suggestions regarding the UI:

If you want to use Amazon you’d use the S3 Region drop down, if you wanted to use an S3 compatible you’d fill in the endpoint yourself. Therefore they are mutually exclusive I think? If so then how about the following to cut down on confusion for some people:

Add a “Custom” option to the S3 Region dropdown then …

1. Move “S3 Endpoint” below “S3 Region” so that it’s more logically placed (I.E. you’d choose the region before the endpoint)
2a. When an Amazon region is chosen, fill in the S3 endpoint automatically but make read-only (this would also make the endpoint you are using for Amazon visible .. if Amazon change something in the future it could be useful for debugging – minor point though!)
2b. When the new “Custom” option is chosen, make the S3 endpoint writeable so you can type in the custom endpoint

The above (for me anyway!) seems a nice neat logical way of presenting the options without potentially getting people confused that once they have entered an S3 compatible endpoint they still have the option of choosing region.

Just a suggestion though – the plugin works great anyway!

Thanks,
Steve.

First “get it going” test went through well – no issues – excellent.
Now heading in to “see if I can break it” test ….. ??

NB. Let me know if you need a minio to test against!

@aj777 – just checking, the spelling of “archive” is wrong looking at your screenshot. Does this match up with a valid directory, if not then I suspect that may be your problem?

I’m not getting any response from the Nextcloud forum unfortunately. I’ve tested your plugin against a demo Nextcloud site and it works fine but for some reason it won’t work on my Docker version (which as they are both pushed out by Nextcloud I would have expected to work the same ?? )

Either way as it doesn’t seem to be your plugin I will close this ticket … and probably never touch WebDav again as it’s doing my head in – lol!

Thanks,
Steve.

Ok, thanks – I will ignore then ??

But unfortunately I’m still stuck where I can’t use WebDav. I’ve tried on another site while watching the access log on the NextCloud server. I can see sabre-dav calls being processed when I click Verify in the plugin (a put followed by a get – presumably it’s just testing whether it has the right access permissions to verify?) and that’s fine.

The backup itself though still stops almost immediately after triggering it as you can see from below.

[2017-06-09 18:13:35] xcloner_remote_storage.INFO: Could not transfer file backup_sue.familycliff.co.uk-2017-06-09_16-01-sql-a118a.tgz [] []
[2017-06-09 18:13:34] xcloner_remote_storage.INFO: Transferring backup backup_sue.familycliff.co.uk-2017-06-09_16-01-sql-a118a.tgz to remote storage WEBDAV [""] []
[2017-06-09 18:13:33] xcloner_remote_storage.INFO: Doing WEBDAV remote storage cleanup for 30 days limit [] []
[2017-06-09 18:13:33] xcloner_remote_storage.INFO: Creating the WEBDAV remote storage connection [""] []

Hmmm – I’ve just checked the logs on some other sites too – and although the backup appears to have worked on those, I can see a lot of errors similar to this:

[2017-06-09 17:06:34] php_system.INFO: E_NOTICE: array ( 'type' => 8, 'message' => 'Undefined variable: matches', 'file' => '/var/www/html/wp-content/plugins/bulletproof-security/includes/general-functions.php', 'line' => 498, ) [] []

I’m wondering if I’ve set something up wrong – or whether something has changed in the latest WordPress Docker container I’m using ….

Ovidiu – just tested out latest dev version and everything aligns correctly now ??

Just spun up a blank site and have the issue.

Only step I did was to add the xcloner plugin. Hence plugins are the normal Akismet / Hello Dolly (both disabled).

The base site is made up from an official WordPress PHP 7 Apache based Docker image:
https://github.com/docker-library/wordpress/blob/716fe2fabb0be1bcd46626fad83d8c345946d343/php7.0/apache/Dockerfile

On top of that I layer on in my Docker image the following:

libldap2-dev added & initially configured (for LDAPS functionality)
zip added
PHP tweaked:
– file_uploads = On
– memory_limit = 64M
– upload_max_filesize = 64M
– post_max_size = 64M
– max_execution_time = 600

Cheers,
Steve.

Sure:

Akismet Anti-Spam
MainWP Child
Wordfence Security
WP Mail Logging
WP-Mail-SMTP

– I’ve also disabled all of them and the screen is the same
– I’ve tried in Internet Explorer as well as Chrome

Just going to spin up a blank site and check that ….