Memory is not the issue here. There are no complex operations, and the difference will be almost unmeasurable. What matters is readability: If your stuff function is rather short (less than eight functional steps) and you use the check just once – keep the check in it. But if you need the support check in … Read more
WordPress coding standards are loosely based on the Pear Coding Standards The Drupal open source project also follows similar standards and has published a guide to configuring various editors and IDEs which includes code for a Emacs Drupal mode which can be modified slightly for WordPress.
You’re not supposed to assign multiple variables on a single line. Do them separately: $pf_param_string = substr( $pf_param_string, 0, – 1 ); $validate_string = $pf_param_string; Or, if you don’t need both variables, just skip one of them: $validate_string = substr( $pf_param_string, 0, – 1 );
There are several things wrong with your code The is no need for translation there. The message should have been translated before it is being passed to that function. At that function there is actually no context at all to create any different translation than %s Escaping should happen at the output. You should escape … Read more
You can totally use namespaces in your project/theme/plugin! The only drawback is that you introduce a PHP 5.3 dependency, while WordPress itself only requires 5.2.4. I guess in 2015 this is not a big issue, even when distributing a plugin to a wide community (opensource or envato). Roots team is using namespaces in their themes, … Read more
I was mistaken. The underscores are required by the template-files if they are part of the custom-post-type’s handle. Make sure to flush the rewrite cache / visit the permalinks page when working with cpt templates The archive.php template the missing cpt-template was falling back to looked similar Following wp-includes/template-loader.php >> get_post_type_archive_template >> get_archive_template doesn’t look … Read more
WordPress.org does not have any hard requirements for code styles for plugins or themes. In the plugin guidelines, the relevant section is #4, “Keep your code (mostly) human readable.” Mainly it is about obfuscation. The most relevant line is this: We recommend following WordPress Core Coding Standards. Note the word recommend, there. This is not … Read more
Apparently PHPCS (link to issue) and WPCS (link to issue) do not work at this point with PHP8 and won’t until their next releases. It’s therefore recommended to use PHP 7.4 instead. “Hack” option Before downgrading my system to PHP7, I tried this hack. It seems to work for me, at least for the brief … Read more
Correct processing of `$_POST`, following WordPress Coding Standards
Consider something like the following: echo esc_html( sprintf( _nx( ‘%1$s Comment on “%2$s”’, ‘%1$s Comments on “%2$s”’, $comment_count, ‘Comments Title’, ‘theme-text-domain’ ), number_format_i18n( $comment_count ), get_the_title() ) ); Where you build the entire string with sprintf and escape that. The coding standards are clear that you should always escape output, and do so as late … Read more