WP Workbench version 1.0.2 released

Thank you for your response IvanBG. This is exactly what I have done, following your thread above. Both wp folder and wp-cli.phar are owned by the server_user:server_user and the permissions are 771. I still get the same error.

The parent ~/bin folder has a 755 permission, cold that be an issue?

In the /bin folder I have 755 permissions. The same in wp file.

In the /bin folder you must have an archive called wp, not a folder (you do this with the command sudo mv wp-cli.phar /home/your_user_server/bin/wp). I don’t have a file called wp-cli.phar in /bin folder.

Hope this helps.

Now I have moved wp-cli.phar to wp file in bin, same permissions and ownership as mentioned, and still I get the same error with the wp-cli log being empty. I am running php-fpm on this host, could that be a source of problem?

i have install WP Workbench in old Centos 7 virtualmin and in a new Almalinux, and in a new server WP Workbench works good, but in Old Centos i have the same error →

Perl : Failed to parse JSON output from WP-CLI command : malformed JSON string, neither array, object, number, string or atom, at character offset 0 (before “(end of string)”) at /usr/libexec/webmin/web-lib-funcs.pl line 13005.
PHP : Failed running `/bin/php81 /home/finq


congratulations for the plugin, fantastic work and good idea.
I suggest to follow this way with the next improvements:
Management of mail blacklists, spam, etc
 that in postfix you have to do most of them manually.
Improved plugin management, for example update Nextcloud versions, etc
 i.e. a WP Nextcloud :wink:

1 Like

Anyone having this error, can you log in via SSH as that user, or just:

~# su - domain-owner-username

And then execute that command, i.e.:

/bin/php8.2 /home/domain/bin/wp --path=/home/domain/public_html

What error do you have then?

‘bash: /bin/php8.2: No such file or directory’

I checked, /bin/php8.2 exists but owned by root.

Thanks for checking Ilia

If you go to the “PHP Options” page, first disable PHP execution mode, and then re-enable it with PHP-FPM, does it solve your problem?

You shouldn’t even have a CentOS 7 server to try it on. It’s been EOL for over a year.

I tried and it’s the same:
‘bash: /bin/php8.2: No such file or directory’

I know, I know, since July last year, that’s why there’s a new one and an old one, let’s see if I can finish migrating everything at once
 this plugin will be very useful for that if I can get it working
Thank you very much for this plugin, things like this are the way forward.

In my case, I tested it on another blog, and it reappeared the error after following all the steps that work in others of my blogs:

malformed UTF-8 character in JSON string, at character offset 2142 (before "\x{ed}a de Egipto. I...") at /usr/libexec/webmin/web-lib-funcs.pl line 13005.

I noticed that the blog description in WordPress Settings contained several accented characters (I write in Spanish).

After removing the accents from the blog’s short description, WP WorkBench started working again, so the issue is probably related to characters that are not present in English.

Hope this helps.

1 Like

Dang! I see this issue too. I’ll look into fixing it!

1 Like

It was fixed, and will be included in WP Workbench 1.0.5.

It worked with this Update. Thank you so much, and it is truly amazing!

1 Like

WP Workbench is loading but it is not loading any values from the WordPress, so all the values are empty.

I tried the backup function and got this error:
‘Creating WordPress backup archive for database and files 


 error : failed to create archive’

I checked the home directory and the wordpress-backups folder was not created by Wordpress Workbench.

‘/bin/php8.2 /home/domain/bin/wp --path=/home/domain/public_html’ still not working, but I thought maybe it could be related to Jailkit being enabled? That the user can’t access /bin/php8.2?


I added /bin/php8.2 to be copied to Jailkit, now the error is changed, php is running but can’t access Phar extension:

‘Fatal error: Uncaught Error: Class “Phar” not found in’

When I run ‘/bin/php8.2 --info | grep ‘phar’’ it returns nothing, if I run it with admin user I receive the Phar extensions information.

I have been testing the backup function, and I have this error:

Flushing object cache ..
.. done
Exporting WordPress database ..
.. error : PHP Fatal error: Uncaught : call to undefined function exec() in phar:///home/userdomain/bin/wp/vendor/wp-cli/db-command/src/DB_Command.php:613 Stack trace: #0 [internal function]: DB_Command->export() #1 phar:///home/userdomain/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Dispatcher/CommandFactory.php(100): call_user_func() #2 [internal function]: WP_CLI\Dispatcher\CommandFactory::WP_CLI\Dispatcher\{closure}() #3 phar:///home/userdomain/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Dispatcher/Subcommand.php(497): call_user_func() #4 phar:///home/userdomain/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(441): WP_CLI\Dispatcher\Subcommand->invoke() #5 phar:///home/userdomain/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(464): WP_CLI\Runner->run_command() #6 phar:///home/userdomain/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(136): WP_CLI\Runner->run_command_and_exit() #7 phar:///home/userdomain/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(1350): WP_CLI\Runner->do_early_invoke() #8 phar:///home/userdomain/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(1294): WP_CLI\Runner->load_wordpress() #9 phar:///home/userdomain/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Bootstrap/LaunchRunner.php(28): WP_CLI\Runner->start() #10 phar:///home/userdomain/bin/wp/vendor/wp-cli/wp-cli/php/bootstrap.php(83): WP_CLI\Bootstrap\LaunchRunner->process() #11 phar:///home/userdomain/bin/wp/vendor/wp-cli/wp-cli/php/wp-cli.php(32): WP_CLI\bootstrap() #12 phar:///home/userdomain/bin/wp/php/boot-phar.php(20): include(...) #13 /home/userdomain/bin/wp(4): include(...) #14 {main} thrown in phar:///home/userdomain/bin/wp/vendor/wp-cli/db-command/src/DB_Command.php on line 613
Creating WordPress backup archive for database and files ..
.. done

I have opened the .tar.gz archive created in the directory /wordpress-backups, and I only see the files of the WordPress blog, but not the database backup.

Note: test it in last version WP Workbench 1.0.5.

Thanks!

Yes, all these issues seem to be related to the jailed environment. Try disabling it and see what results you get. Also, try changing the PHP version on the “PHP Options” page.

If it works without Jailkit enabled, you may need to copy more missing dependencies to the chroot.

Hello,

Solved! In my case, I had disabled exec in PHP with disable_functions = exec in php.ini.

Because of this, the backup didn’t work. I deleted exec from disable_functions in php.ini, and all works now.

@ilia It would be interesting if you could add the ability to schedule backups in the backup function of WP Workbench, just like in the general backup function of Virtualmin or Webmin.

Thank you for this great work!

1 Like