Sticky Postbox vs W4 Post List

Sticky Postbox is a piece of code written few years ago as exercise to learn how WordPress handles administration meta boxes’s availables statuses (closed, hidden and sortings). This very lightweight plugin adds the sticky feature to administration meta boxes allowing them to be sticky at top right corner of the browser window. Only one meta box can be sticky at once, so a new sticky meta box unstick the current one (if there is one). Basic Features Per-user settings. Multisite support. Usage Once the plugin is installed and activated you can sticky administration meta boxes using sticky icon (it appears on the top right corner of each box). API Constants You can use define following constants in your wp-config.php file. STICKY_POSTBOX_DEBUG Turn on debug messages (also WP_DEBUG has to be true). Default to false. STICKY_POSTBOX_GLOBAL_OPTIONS In a Multisite installation, allows to shares user’s sticky meta boxes settings across all his sites. For example, if you sticky Publish box in editing Pages in a specific site, it will be sticky on all Pages of all sites. Default to false. STICKY_POSTBOX_AUTOENABLE By default if the plugin has been activated, it starts automatically. Define to false if you want to init it manually, for example: // Activate manually the plugin once all plugin have been loaded. add_action( 'plugins_loaded', function() { \Sticky_Postbox::get_instance( array( 'debug' => WP_DEBUG, 'global_options' => false, ) ); } ); Hooks Currently the plugin doesn’t have actions or filters.

W4 Post List builds the lists that WordPress core still can’t: posts grouped under year, month, category or author headings; category and term indexes; user directories; and combined Terms + Posts and Users + Posts lists. You control the output with a template of plain HTML and simple template tags, so the markup stays clean, semantic and completely yours. Place any list anywhere with the W4 Post List block, the [postlist id="123"] shortcode, or the classic widget. What can you build? Year/month archives — posts grouped under date headings Category, tag or custom taxonomy indexes — with or without each term’s posts listed underneath Author and user directories — list users by role, with avatars, bios and each user’s posts Filtered post lists — any post type, filtered by status, taxonomy terms, custom fields, dates, authors, parents and more Media lists — image and attachment lists by mime type Five list types Posts Terms Users Terms + Posts Users + Posts Query options (Posts) Post type, status and mime type Search keyword Include/exclude posts by ID, exclude the current post Filter by parent, author, taxonomy terms (tax query), custom fields (meta query) and dates (date query) Items per page, with multi-page pagination Group results by Year, month, or month + year Category, tag or any custom taxonomy Author Parent Order results by ID, title, slug, publish date, modified date, menu order, comment count, custom field value, or random Pagination Next/previous links or numeric navigation, with optional AJAX page loading Full control over the output Output is template-driven: every list has an HTML template with template tags like [post_title], [post_permalink], [featured_image], [post_author_name] and [post_meta key="..."]. Start from a ready-made template — cards, archives, category indexes, user directories — and tweak it, or write your own markup for pixel-perfect control. A live preview in the editor shows your changes before you save. If you want a drag-and-drop visual builder, this plugin isn’t that — it keeps you close to your own HTML, which is exactly why themes and developers like it. See the full template tag reference and live examples with copy-paste templates. Lightweight, independently measured WP Hive independently measures W4 Post List at 19 KB memory usage and +0.05 s page-speed impact — better than 99% of the plugins they test. No bundled frameworks, no frontend bloat. Privacy Policy W4 Post List uses Appsero SDK to collect some telemetry data upon user’s confirmation. This helps us to troubleshoot problems faster & make product improvements. Appsero SDK does not gather any data by default. The SDK only starts gathering basic telemetry data when a user allows it via the admin notice. We collect the data to ensure a great user experience for all our users. Integrating Appsero SDK DOES NOT IMMEDIATELY start gathering data, without confirmation from users in any case. Learn more about how Appsero collects and uses this data.