WordPress Archives - Jesús Amieiro

Translation and localization resources

In this post, I collect some interesting resources to translate and localize software.

WP-CLI intro

Slides from my talk at Coruña WordPress meetup (November 3, 2022).

As Galician GTE, I translate a lot of strings from English to Galician: WordPress core, WordPress.org infrastructure, plugins, themes, … As a bilingual speaker (Galician and Spanish languages), I realized I can translate faster if I use the Spanish translations as starting point, so I develop a CLI tool to translate all WordPress stuff from Spanish to Galician, using the open-source translations created by the Spanish community (thank you, folks). A few months later, I converted this CLI tool in a website, so you can use it without any installation. And, of course, I have released it as open source (AGPL).

How to use PHPCS and PHPCBF with a single WordPress file

PHPCS and PHPCBF are two well-know PHP scripts used in the PHP development to (PHPCS) detect violations of a defined coding standard, and (PHPCBF) to automatically correct coding standard violations.

I usually use both with composer in my WordPress projects, adding them as dependency in the composer.json file.

But sometimes I need to check some individual PHP file without adding PHPCS and PHPCBF as dependency. In this post, I am going to explain how I do this.

Updating WordPress to the nightly version

Sometimes, it is useful to use the WordPress nightly version on your local environment, to avoid problems with your code in the near future.

Testing WordPress functions in the CLI

Sometimes you need to test some code, API functions,… in a WordPress plugin or theme without using anything else.

To do this, you can use the WP-CLI. Make sure you have installed it.

Running the GlotPress tests

GlotPress has some PHPUnit tests. In this post, I will go to explain how to run it in your local machine.

Using the dump() and dd() debug helpers in WordPress

dump() and dd() are two useful debug helpers available in the Laravel framework.

Using e() or esc_html_() when translating on WordPress

In a talk at the WordCamp Spain online 2021 Adriá Cobo asked me one interesting question about these 2 functions (e() and esc_html_()):

If everything that is printed must be escaped, what is the point of _e()? Is it a legacy code?

In this post, I try to answer this question.

Documenting GlotPress with phpDocumentor

The current GlotPress API documentation (October 2021) was generated by ApiGen. Last commit was made on April 4th, 2016.

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.

wget https://github.com/phpDocumentor/phpDocumentor/releases/download/v3.1.2/phpDocumentor.phar

To run phpDocumentor, execute:

php phpDocumentor.phar run \ 
-d ~/code/wordpress/glotpress-env/glotpress.git \ 
-t ~/code/wordpress/glotpress-env/gp-docs \
--ignore "vendor/"

Where:

~/code/wordpress/glotpress-env/glotpress.git is the GlotPress folder.
~/code/wordpress/glotpress-env/gp-docs is the documentation folder.
vendor/ is the folder where Composer stores all the information. It is located in the root folder of the project.

Category: WordPress