Zach Tirrell

Matthew Batchelder

lucatume

Gustavo Bordoni

neillmcshea

GeoffBel

Victor Zarranz

András Guseo

Brian

leahkoerper

Juan Aldasoro

<p>This is a tool for developers who want to turbo-charge their custom post type listings with metadata, taxonomies, and more. An intuitive interface for adding (and saving) complex filtersets is provided, along with a drag-and-drop interface for choosing and ordering columns to be displayed. Metaboxes are also automatically generated for all your metadata-entry needs.</p>
<ul>
<li>Add columns to the post listing view</li>
<li>Filter post listings by custom criteria</li>
<li>Easily add metaboxes to custom post types</li>
<li>Automatically add registered taxonomies to post listings</li>
<li>Sort by post metadata</li>
</ul>
<p>See docs/documentation.html in the plugin directory for full documentation.</p>
<p>The team at The Events Calendar stands by our work and offers light support every Wednesday to the community via the WordPress.org support forums. Feel free to ask a question if you’re having a problem with implementation or if you find bugs.</p>
<h4>SUBMITTING PATCHES</h4>
<p>If you’ve identified a bug and want to submit a patch, we’d welcome it at our <a href="https://github.com/the-events-calendar/advanced-post-manager" rel="nofollow ugc">GitHub page for Advanced Post Manager.</a> Simply cue up your proposed patch as a pull request, and we’ll review as part of our monthly release cycle and merge into the codebase if appropriate from there. (If a pull request is rejected, we’ll do our best to tell you why). Users whose pull requests are accepted will receive credit in the plugin’s changelog. For more information, check out the readme at our GitHub page. Happy coding!</p>
<h3>Add-Ons</h3>
<p>But wait: there’s more! We’ve got a whole stable of plugins available to help you be awesome at what you do. Check out a full list of the products below, and over on <a href="https://evnt.is/18wn" rel="nofollow ugc">our website</a>.</p>
<p>Our Free Plugins:</p>
<ul>
<li><a href="https://wordpress.org/plugins/the-events-calendar/" rel="ugc">The Events Calendar</a></li>
<li><a href="https://wordpress.org/plugins/event-tickets/" rel="ugc">Event Tickets</a></li>
<li><a href="https://wordpress.org/plugins/gigpress/" rel="ugc">GigPress</a></li>
<li><a href="https://wordpress.org/plugins/image-widget/" rel="ugc">Image Widget</a></li>
</ul>
<p>Our Premium Plugins and Services:</p>
<ul>
<li><a href="https://evnt.is/18wi" rel="nofollow ugc">Events Calendar PRO</a></li>
<li><a href="https://evnt.is/197u" rel="nofollow ugc">Event Aggregator</a> (service)</li>
<li><a href="https://evnt.is/18wk" rel="nofollow ugc">Event Tickets Plus</a></li>
<li><a href="https://evnt.is/2g" rel="nofollow ugc">Community Events</a></li>
<li><a href="https://evnt.is/18wl" rel="nofollow ugc">Community Tickets</a></li>
<li><a href="https://evnt.is/fa" rel="nofollow ugc">Filter Bar</a></li>
<li><a href="https://evnt.is/2e" rel="nofollow ugc">Eventbrite Tickets</a></li>
</ul>


Advanced Post Manager

This plugin doesn't do anything. It says you have to install it and then get a developer to write some code to make it work. That means this isn't a plugin, it's just a useless piece of code. The plugin repository should only be for plugins that actually add some functionality to your WordPress website. This "plugin" is just taking up space and confusing people. Did the developers just get bored and decided not to finish their plugin? It should be removed from the plugin repository!

Should Be Removed

Turbo charge your posts admin for any custom post type with sortable filters and columns, and auto-registration of metaboxes.

Pedro Matias

<p><strong>Modules Insight</strong> helps WordPress developers and site managers audit installed plugins, assess the risk of upgrading PHP, and export complete reports — all from a single on-demand scan.</p>
<h3>PHP Upgrade Risk Evaluator</h3>
<p>Planning a server PHP upgrade? MI queries the <strong>WordPress.org API</strong> for each installed plugin and produces a colour-coded risk table showing how likely each plugin is to break on your target PHP version.</p>
<p>Each plugin is rated <strong>Low</strong>, <strong>Medium</strong>, <strong>High</strong>, or <strong>Not on WP.org</strong> based on two signals:</p>
<p><strong>1. Last Updated</strong> — how recently the plugin received a release on WordPress.org.<br />
<strong>2. Minimum PHP Declared</strong> — the <code>Requires PHP</code> field set by the plugin author.</p>
<p>Risk is assigned as follows:</p>
<ul>
<li><strong>High</strong> — Not updated in over 3 years, or declares a minimum PHP below 7.0. These carry the greatest risk of breaking on PHP 8.x and should be investigated before upgrading.</li>
<li><strong>Medium</strong> — Falls between High and Low. Test on a staging environment before upgrading production.</li>
<li><strong>Low</strong> — Updated within the last 12–18 months and declares PHP 7.4 or higher as its minimum. Likely compatible, but a quick smoke test after upgrading is still recommended.</li>
<li><strong>Not on WP.org</strong> — Not found in the WordPress.org directory (premium plugins, custom code). Compatibility must be verified manually with the vendor.</li>
</ul>
<p><strong>Important:</strong> risk ratings are based on publicly available metadata, not code analysis. A Low-rated plugin could still have incompatibilities; a High-rated plugin might work perfectly. Use the table as a triage guide, not a guarantee. Always test on a staging environment before upgrading PHP on a live server.</p>
<p>Results from the WordPress.org API are cached per plugin for 24 hours to avoid unnecessary external requests.</p>
<h3>Plugin List and Reports</h3>
<p>MI lists all installed plugins (active, inactive, and network-active on multisite) with version numbers, author details, and descriptions. It also reports the active WordPress version and active theme.</p>
<p>Reports can be exported as <code>.json</code> or <code>.csv</code>. Both formats include the PHP compatibility data if a check has been run prior to export.</p>
<p>Tested and fully compatible with <strong>WordPress 7.0</strong>.</p>
<h3>Key Features</h3>
<ul>
<li>PHP upgrade risk evaluation via the WordPress.org API</li>
<li>Colour-coded risk table: Low / Medium / High / Not on WP.org</li>
<li>Lists all installed plugins with status, version, author, and URIs</li>
<li>Reports WordPress version and active theme</li>
<li>Export as JSON or CSV (includes compat data when available)</li>
<li>Dashboard widget and <code>[plugin_list]</code> shortcode</li>
<li>Scan-on-demand — nothing runs automatically on page load</li>
<li>100% read-only — safe for production use</li>
</ul>
<h3>Use Cases</h3>
<ul>
<li>Assessing risk before upgrading PHP on a server</li>
<li>Managing multiple WordPress sites and keeping plugins audited</li>
<li>Client-facing reports on installed plugins</li>
<li>Pre-deployment or pre-update plugin audits</li>
</ul>
<h3>Credits</h3>
<p>Made with ❤️ by Pedro Matias for WordPress developers and admins.</p>


Modules Insight

Audit installed plugins, assess PHP upgrade risk via the WordPress.org API, and export full reports as JSON or CSV.

Advanced Post Manager vs Modules Insight