Sometimes you need to test some code, API functions,… in a WordPress plugin or theme without using anything else.
GlotPress has some PHPUnit tests. In this post, I will go to explain how to run it in your local machine.
I think it is a good practice to sign your Git commits. In this post, the author explains why and how to sign your Git commits. An interesting reading.
The last ApiGen commit was made on 23 Apr 2018, so I think this tool is deprecated. Furthermore, I was not able to use it with PHP 7.4 and GlotPress, so I look for another tool. The most PHP used tool is phpDocumentor. In this post I explain how to use it with GlotPress.
Install phpDocumentor globally on the machine, using the .phar tool.
cd ~/code/utils mkdir phpDocumentor cd phpDocumentor
Get the last .phar URL.
To run phpDocumentor, execute:
php phpDocumentor.phar run \ -d ~/code/wordpress/glotpress-env/glotpress.git \ -t ~/code/wordpress/glotpress-env/gp-docs \ --ignore "vendor/"
~/code/wordpress/glotpress-env/glotpress.gitis the GlotPress folder.
~/code/wordpress/glotpress-env/gp-docsis the documentation folder.
vendor/is the folder where Composer stores all the information. It is located in the root folder of the project.
I have had some problems installing wordpress-develop on the M1 chip, so I describe here how I have solved it.
Laravel Valet is a development environment for macOS minimalists. It was developed to use in Laravel projects, but in this post, I will explain how to install and use with WordPress.
Moving a Laravel application between two servers, I get this error in the destination server:
When you execute Composer, it uses the default PHP version. Sometimes, you will have problems if you use Composer with a different version that the one that executes the project.