Search results

It is working and backing up everything though. I have no idea why the files aren't showing in the zip file but like I said, you do a restore from it and all the files are actually there. So works as advertised.

It was a strange because unpacking the zip didn't show files in the root folder. However, on restoring the backup it did work and restored everything. So this is a non-issue.

Confirmed this is broken and the cron won't run. Tested on multiple servers. Looks like all the updated WP installs I'm seeing are due to internal update settings within WP. Can anyone confirm/help?

Bingo.

Just been looking over a server. It has over a hundred manually installed WordPress instances that are not in the toolkit. Is there a way to scan for all WP on server and get them in the Toolkit?

Good stuff. Might play with this.

Want to do a tutorial on how to auto-update plugins from WP-CLI? :)

For the most part the update system is working but we still get the odd WordPress not updating. For example see the image. A v4.8 with Minor switched on and update available for 4.8.1. .

Is there an ETA for automatic plugin updates?

@IgorG - this is really important if you want Varnish on Plesk to work correctly. We need it. Badly.

Okay, will do.

Hi Igor, Already tried: Issue - Website Importer broken in 17.5

TITLE: Website Importer Doesn't work on 17.7 PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE: Onyx, 17.5, CentOS 7, x64 PROBLEM DESCRIPTION: The Website Importer just doesn't work. Debug Log: Scanning for content Plesk Migrator returned non-zero exit code COMMAND: 'plesk-migrator'...

Okay, will see what they say.

There are no rewrite rules. This just doesn't work. Migration Debug log:

TITLE: Dropbox Extension not backing up files PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE: Onyx 17.5 CentOS 7 x64 PROBLEM DESCRIPTION: The Dropbox extension backs up everything except a site's files. I did a test on a primary domain with 2 subdomains. In the "Sites" folder were 2...

I just tested this with another Plesk server. Had to disable FTPS. First it errors out and the extra two fields appear for directory and URL. I tried combinations of everything. Obviously on this test I was trying to drill into httpdocs.

Website importing fails: Unable to locate the document root directory of the website Patch no worky. Halp.

On further checking I do have Varnish working okay on HTTPS. In Dev Tools on Chrome it still shows as MISS. Dev Tools on FF it shows HIT. I checked with isvarnishworking.com and it shows it is working as intended. However, it is impossible to force HTTP to load HTTPS. Plesk's function won't...

We have this working but the Really Simple SSL plugin redirects but Varnish headers show MISS. Also, if you load any blog content page without HTTPS it does not work - it stays on HTTP. We've spent hours on this and can't find any method to get forced redirects to HTTPS working with Varnish...