Under PHP 8 this will cause a fatal error when it's printed on screen.
Instead of repeating the second placeholder, they've created a string that now accepts a minimum of three arguments. Our imaginary translator has decided to use the date argument twice, but they've done it wrongly. Here's an example of a translation that will break your website under PHP 8 if it receives two arguments:
#Online text formatter for wordpress code
PHP will forgive you for using fewer placeholders, but if you add too many then the code that renders the string will throw an error for supplying too few arguments. If your translation doesn't also have two placeholders then it's incorrectly formatted. They're numbered 1 and 2 here, so the intended order is clear and may be swapped if needed in another language. In this example the first argument is a CSS class the second is a formatted date. We say that the string accepts two arguments. Suppose a source string looks like this inside the Loco Translate editor: We won't repeat the WordPress documentation on formatting translations but we'll explain the two most common mistakes that can crash your website and leave you thinking there's a bug in the code, when in fact it's a bug in the translations. That means you could experience this issue even if your theme and plugins are 100% compatible with PHP 8. These errors are likely to be caused by incorrectly formatted translations that have been passed to PHP's printf function (or similar).
If you get fatal errors after upgrading from PHP 7 to PHP 8, check your error logs for messages like these:įatal error: Uncaught ArgumentCountError: 2 arguments are required, 1 givenįatal error: Uncaught ValueError: Unknown format specifier. This is likely to be a mistake in the translation, rather than in anyone's code. Incorrectly formatted strings can cause fatal errors under PHP 8. FAQ: Why do I get ArgumentCountError / ValueError when upgrading PHP?
0 kommentar(er)
