No Frames vs W4 Post List

No frames removes the browser frames sometimes imposed on your site. It has become a trend for top sites especially news and content aggregrators to show your site inside a frame (if you see a site toolbar on the top of the page it’s usually using a frame). Basically the visitor never leaves the site using the frame although they are viewing content created by you. This is done for multiple reasons and one is to improve the metrics of the site using the frame as ‘visitor time on site’ will improve only for the site using the frame and not you. Purpose of No Frames plugin is to detect these cases and break your site free from the shackles of the frame, thus presenting the user with your full page. This not only improves your visitor experience but your site metrics as well. Changelog: v0.2 – Disabled it for admin panel v0.1: – Released first version Plugin by Vladimir Prelovac. Looking for WordPress Consultant? License This file is part of No Frames. No Frames is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. No Frames is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with No Frames. If not, see http://www.gnu.org/licenses/.

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.