WP-PostViews vs Shortcodes Ultimate – Content Elements

Building new pages with Gutenberg? Explore VovaBlocks, a focused collection of native marketing and content blocks from the creator of Shortcodes Ultimate. View VovaBlocks → About Shortcodes Ultimate Shortcodes Ultimate is a WordPress shortcode plugin for adding tabs, accordions, buttons, FAQs, sliders, carousels, lightboxes, columns, boxes and other reusable content elements without coding. It is ideal for site owners who want richer content layouts and practical UI elements without switching to a full page builder. Use Shortcodes Ultimate in the Block Editor, Classic Editor, widgets and template files. Generate shortcodes visually, preview the result before inserting it, and reuse the same elements across posts, pages and existing shortcode-based content. Trusted by hundreds of thousands of WordPress sites, Shortcodes Ultimate helps you replace multiple single-purpose UI plugins with one maintained toolkit. Explore live examples What you can build With Shortcodes Ultimate, you can quickly add common WordPress content elements such as: Accordions and FAQ sections Responsive tabs CTA buttons and download buttons Boxes, notes and callouts Columns and layout helpers Sliders and carousels Lightboxes for images and custom content Post lists and dynamic content blocks Spoilers, toggles and expandable content Media embeds and visual content blocks Instead of installing a separate plugin for every small content element, Shortcodes Ultimate gives you one maintained toolkit for everyday WordPress content tasks. Works with modern and classic WordPress workflows Shortcodes Ultimate works with the Block Editor, Classic Editor, widgets and template files. You can insert shortcodes manually, use WordPress shortcode blocks or use the built-in shortcode generator to configure elements visually. This makes the plugin useful for: Site owners who want to improve content without coding Bloggers and affiliate publishers who need reusable CTA and content blocks Agencies and freelancers maintaining multiple WordPress sites Developers who want shortcode-friendly output in templates Existing sites with older content that already uses shortcodes Why use Shortcodes Ultimate? 50+ ready-to-use WordPress shortcodes Visual shortcode generator Live preview Works with the Block Editor and Classic Editor Shortcodes can be used in posts, pages, widgets and template files Responsive elements that work with your theme Built-in Custom CSS editor Developer-friendly hooks and documentation Free version available on WordPress.org Pro version available for advanced shortcodes, extra styles and premium support Why shortcodes still matter in WordPress The WordPress Block Editor is great for visual content editing, but shortcodes are still useful when you need portable, reusable content elements that work across different parts of a WordPress site. Shortcodes are especially helpful when you want to: Reuse the same content element in many posts or pages Add dynamic content inside widgets or templates Maintain older WordPress sites that already use shortcodes Work across Classic Editor and Block Editor workflows Add content elements without switching to a full page builder Keep common UI elements available through a simple text-based syntax Shortcodes Ultimate is designed for these practical workflows. It gives you a large collection of ready-made shortcodes and a visual generator, so you do not need to write shortcode syntax manually unless you want to. Free and Pro The free version of Shortcodes Ultimate includes a large collection of useful shortcodes for everyday WordPress content tasks. Shortcodes Ultimate Pro adds advanced shortcodes, additional styles, Content Slider, Pricing Table, Testimonials, Shortcode Creator, Elementor support and premium support. Compare Free and Pro Useful links Documentation Live Examples Pro features Support

WP-PostViews counts how many times each post, page or custom post type has been read and gives you somewhere to show the number. The count is kept as post meta, so it sorts, queries and exports like anything else WordPress stores about a post. Features A view count on any post, page or custom post type, printed by a template tag or by the [views] shortcode. Two templates you edit yourself, with tokens for the count, the title, the date, the excerpt, the thumbnail, the author and more. Choose who is counted — everyone, guests only or logged in users only — and leave known robots out. Template tags and a widget for the most and least viewed posts, optionally within a category or a tag. A sortable Views column on the post and page list tables. The count on the REST API as a views field, and an AJAX counting path for sites behind a page cache. A section on the WP-Stats page when that plugin is installed. Donations I spent most of my free time creating, updating, maintaining and supporting these plugins, if you really love my plugins and could spare me a couple of bucks, I will really appreciate it. If not feel free to use it without any obligations. Usage The simplest way, and the only one that works in a block theme without editing template files, is the shortcode. Put it in the post or page whose count you want shown: [views] shows the count for the post it appears in. [views id="1"] shows the count for post 1, wherever you put it. To show the count on every post automatically, a classic theme calls the template tag from index.php, archive.php, single.php or page.php, anywhere inside the loop: The settings live at WP-Admin -> Settings -> WP-PostViews, on two tabs. Settings is where you choose who gets counted and whether WP-Stats is offered a Views section; Templates is where you edit the markup a count is rendered with. Where the count appears is decided by where your theme calls the_views() or where you put the shortcode. To hide it somewhere in particular, answer the wp_postviews_should_display filter: add_filter( 'wp_postviews_should_display', function ( $show ) { return ! is_archive() && ! is_search(); } ); Showing The View Count In A Block One block is available in the editor, under Widgets: Post Views — the view count, rendered with the template from the Templates tab. Leave Post ID at zero to show the count of the post the block is in, which is what an empty [views] does, or set it to another post’s ID to show that post’s count instead. It renders on the server, so the block preview in the editor is the real number rather than an approximation, and the count keeps rising in every post showing it without anything being re-saved. Previewing the block in the editor does not count a view. The shortcode still works and is not going anywhere. [views] and [views id="1"] behave exactly as they always have, and a post already containing one needs no change. The block calls the same code the shortcode calls, so the two render identically — use whichever suits the post. WP-CLI wp postviews list wp postviews list --limit=50 --format=json wp postviews get 42 The command reads and never writes. No screen in this plugin edits a view count, so the command does not offer one either — wp post meta update views is still there for whoever genuinely needs it, and says plainly that it is reaching past the plugin. REST API POST /wp-json/postviews/v1/post/ /view Reading a count needs no route of its own. The count is already published as a read-only views field on the core post resource, so /wp-json/wp/v2/posts/ answers with the post and its count together, and a list of posts carries every count in one response. What the core field cannot do is write, which is what this route is for: it counts a view, and it exists for sites serving cached pages, where the view has to be reported after the page is delivered. It takes the same wp_postviews_nonce the counting script is given, as a nonce parameter. It is refused unless the site defers counting — that is, unless it has a page cache and has turned the AJAX counting path on. Otherwise the view has already been counted while the page rendered, and counting again here would record every view twice. A refusal answers 403 — a bad nonce, or a site that counts views while the page renders. A post that does not exist is 404. This route is an addition. The admin-ajax.php wp_postviews action is unchanged and still supported.