It is not easy to write them, so I explain here how to write them in a Spanish keyboard:

You can copy and paste to the new document: « ».

Windows

Use the ALT key and a number:

• ALT+174 for the open quotation mark: «.
• ALT+175 for the close quotation mark: ».

macOS

Use Option (Alt) + Shift (Uppercase) + a key:

• Option (Alt) + Shift  + ´ for the open quotation mark: «. The key just at the right of the ñ key.
• Option (Alt) + Shift  + ç for the close quotation mark: ».

In a WordPress/PHP project, we usually use PHP_CodeSniffer (phpcs) to detect violations of a defined coding standard, and PHP Code Beautifier and Fixer (phpcbf) to automatically correct coding standard violations.

To automatically execute both scripts when you try to commit the code with Git, you can use a Git hook: a script that Git runs before or after events such as committing or pushing. The pre-commit hook runs before the commit is completed. If this script exits with a non-zero status, the commit will be aborted.

To set this up, create or edit the .git/hooks/pre-commit file in my project directory:

touch .git/hooks/pre-commit

Then, make it executable:

chmod +x .git/hooks/pre-commit

Next, add this code to the pre-commit file:

#!/bin/ bash # Remove the space between "/" and "bash"

# Paths to the phpcs and phpcbf executables
PHPCBF="./vendor/bin/phpcbf"
PHPCS="./vendor/bin/phpcs -n"

# Run phpcbf to automatically fix coding standard issues
echo "Running phpcbf..."
$PHPCBF

# Run phpcs to check for coding standard violations
echo "Running phpcs..."
$PHPCS

# If phpcs fails (returns a non-zero exit code), prevent the commit
if [ $? -ne 0 ]; then
    echo "phpcs found coding standard violations. Commit aborted."
    exit 1
fi

echo "All checks passed. Proceeding with commit."

This script runs phpcbf to automatically fix coding standard issues. Then it runs phpcs to check for coding standard violations, and if it finds any violation, it exits.

Now, when you commit, this file is executed:

git commit -m "Add the the_title hook only when I am in the page"
Running phpcbf...
................... 19 / 19 (100%)
No fixable errors were found
Time: 1.8 secs; Memory: 12MB

Running phpcs...
................... 19 / 19 (100%)
Time: 145ms; Memory: 24MB

All checks passed. Proceeding with commit.

[local-import-pages 43e3e6a4] Add the the_title hook only when I am in the page
 2 files changed, 7 insertions(+), 3 deletions(-)

your connection is not private

When I clicked on the “Advanced” button, I got this information: the certificate was expired.

To solve this problem, you need to unsecure the local domain (glotpress.test in my local environment):

valet unsecure glotpress.test

Then you need to remove the certificates for this local site:

rm ~/.config/valet/Certificates/glotpress.test.*

And, finally, secure the local domain another time:

valet secure glotpress.test

Now the certificate is valid.

Note: sometimes, the last command valet secure glotpress.test doesn’t work. A workaround that worked for me is to access to the folder of the site and then execute the command to secure the site:

cd /Users/myuser/code/wordpress/glotpress
valet secure

• Slides.
• Scripts (5).
  • main_script.sh, with all the steps to be able to reproduce this workshop.
  • import_products.sh, to import a list of products from a CSV.
  • create_fake_orders.sh, to create to fake customers and orders.
  • export_pending_orders.sh, to export a list of previously created orders in pending status.
  • export_customer_list.sh, to export a list of the shop’s customers.
• Data to import (2):
  • pasta.ods. Spreadsheet with the 5 products to import.
  • pasta.csv. CSV file with the 5 products to import.

If you try to install with brew, you are going to get an error:

$ brew install php@8.0

Error: php@8.0 has been disabled because it is a versioned formula!

At the official website, you can see it disabled.

If you need to use this version, or a previous one, between 5.6 and the last supported, you can use a different tap. To do this, you need to add the tap:

brew tap shivammathur/php

Then you have to install the desired version:

brew install shivammathur/php/php@8.0

And now you have this unsupported version installed on your macOS:

php -v
PHP 8.0.30 (cli) (built: Aug  3 2023 17:13:08) ( NTS )

More info:

• https://github.com/shivammathur/homebrew-php
• Installing Old Versions of PHP With Homebrew

To do it, you can use this trick:

fwrite(STDERR, print_r($myOddVariable, TRUE));

This will show you the $myOddVariable in the console when you exeucte the test.

Remember, this is a temporary trick, and you should not use this in the final test.

Seen at Stack Overflow.