The section on comment_form_default_fields and comment_form_defaults is especially helpful for understanding what should be changed via filters vs. arguments. One extra tip: if you’re customizing fields, it’s worth keeping accessibility in mind (labels, aria-required, and clear error states) so the form stays usable even with heavy theme styling.

Adeel Arshad
CEO: https://digitalperfection.ae/

That basically gets into the pluralizing section, which I talk about on a later post.

I would like to add my distaste for sprintf as the token replacer though. In my experience translators rarely understand the arcane placeholders, especially when there’s more than one.

I now use PHP’s ‘strtr’ function, which allows for much more obvious replacements for translators to deal with.

For example, “Shipped %1$d on %2$s” conveys nothing and is ripe for errors in typing, whereas “Shipped [QUANTITY] on [DATE]” (or similar) is clearer for everyone, and is much easier for the translator to switch around if the grammar demands it.

There’s an answer on Stack Overflow here with more examples: https://stackoverflow.com/a/60182650/

Correct, and I have no plans to update it.

Stop using this plugin. I wrote about how to stop using it almost 4 years ago now: http://ottopress.com/2017/on-the-topic-of-that-pesky-widget/

This plugin made sense back when migrating theme sidebars to widgets was a new thing, but that hasn’t been since WordPress 2.5 or so. Everybody should stop using executable PHP code stored in the database. Either write a custom plugin, or just switch to using blocks instead, which is much saner, safer, and a solid path forward.

PHP Deprecated: Function create_function() is deprecated in wp-content/plugins/php-code-widget/execphp.php on line 62

p.s. PHP 8.1.0 – just released

No.