Recent content by Robin Scott

Note '--username=' should be '--username=CORRECTUSERNAME' also we should have --user_pass=SOMEPASSWORD in there too?! Perhaps not in this log, but we should be using the change password, not the change username direction. We're not attempting to change the username here. I think its related to...

`[2018-09-03 17:03:19.923] ERR [1] '/usr/local/psa/admin/bin/filemng' 'SITENAME' ' exec' '/mnt/storage/www/SITEDOMAIN.co.uk' '/usr/local/psa/admin/plib/modules/wp...

Hi, This issue is still persisting despite the new version being installed.

In fact, why is the CLI code Plesk calls attempting to change the admin username - that's not what's being attempted here?!

So WP CLI, this works to change admin password in one of these failed sites - couldn't the "change password" code WPT uses do it this way? plesk ext wp-toolkit --wp-cli -instance-id 199 -- user update [USERNAME] --user_pass="[PASSWORD]" The code which is attempted by the WPT is failing, as...

hmm no - it doesn't resolve it for all of them, just the one site I was looking at...

Hey I found the issue here... Site which doesn't work: Site which does work Changing this setting to on, allows password to be reset. Note this was "like this before" and "worked before" so maybe will help in future if someone else runs into this issue. It was a bit of a weird one to...

In fact, it looks like this WP CLI command is malformed - its trying to change the admin username, but not supplying a new one?

` ERR [1] '/usr/local/psa/admin/bin/filemng' 'alexbar' 'exec' '/mnt/storage/www/[SITENAME].co.uk' '/usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/wp-cli/bin/wp' '--path=/mnt/storage/www/[SITENAME].co.uk/httpdocs' 'admin-username' 'change' '[USERNAME]' '--username=' failed with code...

I'll get some screencasts - can I email you these? They will almost certainly reveal private information...

Its working to install new WordPress sites. The issue is with pre-existing WP sites (not all of them - strangely there are 2x which were there already which work - both have the wp_ database prefix (not saying that's the cause, just something they have in common!))... The other server I tested...

I'll have the old install docs somewhere... I wrote them. This is a 1 client server, but with a heap of installs. Its a corporate client.

Installing a test domain - WPT works when I do it, but when the clients do it, they have anecdotally managed to install "not working" versions. Removing and reinstalling WPT does not work - the login is still missing, and update password does not work after the scan. Its strange, because every...

I'm going to remove the WPT extension, make sure that config file is gone, then reinstall and scan. This should rule out a heap of things.

When I say here, I mean here: If the option existed in WPT to change the database name, this would allow this issue to be at least ruled out. I don't think I'd be able to easily update the information in that wp-toolkit.sqlite3 file myself, otherwise.