The wrapping div is easy. When you use wp_nav_menu(), add this argument: ‘container’ => false For the <ul> element, there’s an argument called ‘items_wrap’. See woodchucky’s answer for more info on that one (and upvote it!).
In my opinion, deprecating numberposts would not make sense, as numberposts is used to query x amount of posts, whilst posts_per_page is used to denote how many posts per page are being shown during pagination. If you were to deprecate numberposts in favor of simply posts_per_page, then pagination would not exist. ie: “numberposts” => 50, … Read more
PHPUnit would come to mind, if the WP test suite wasn’t so broken, and if WP had been designed and written in a way that it could actually be tested properly. 😉 More seriously, you can test your plugins all you want from their functional standpoint with unit tests and the like. The issue is … Read more
That’s because the file in which is_plugin_active() is defined – wp-admin/includes/plugin.php – is only loaded in the admin, after your plugin is loaded. Thus, you can only call it after ‘admin_init’ has fired: function check_some_other_plugin() { if ( is_plugin_active(‘some-plugin.php’) ) { … } } add_action( ‘admin_init’, ‘check_some_other_plugin’ );
It is easier to read: When is what called? If you are debugging a hook you can immediately see if you have to read the function or not: If it is not your hook, you can skip the code. In my themes and plugins I combine all registrations for actions, filters and shortcodes at the … Read more
As a rule of thumb, you should use a POST request for most actions, to make sure they are not executed by accident. But it is also a good practice to redirect to a normal page after a POST request, to prevent duplicate execution when the user refreshes the page. So the flow is like … Read more
The wp_insert_post_data filter can do that: add_filter( ‘wp_insert_post_data’ , ‘filter_post_data’ , ’99’, 2 ); function filter_post_data( $data , $postarr ) { // Change post title $data[‘post_title’] .= ‘_suffix’; return $data; }
It’s stored in the database, within the wp_posts table, under the custom_css post type, where the post name is the theme slug. There you also have the related customize_changeset and revision post types. The custom css post ID is also stored in the wp_options table under each theme mods, e.g. theme_mods_twentysixteen for Twenty Sixteen. It’s … Read more
This is not recommended in any WordPress style guide, and I think it is a bad coding style. Beginners are using this style, maybe because it feels more like HTML … Unfortunately, the default themes are using this style way too often, so some beginners might think it is part of a code style. One … Read more
A Custom Fields UI I think really custom fields with custom UI is really a big requirements for a lot of people. I mean, compulsory, repeating, grouped, multiple images, etc. There is a bunch of plugins trying to provide the functionality, but they are all add-ons and have to play catch up to new WP … Read more