Jay Kavanagh

Custom Post Type Toggle gives you a clear overview of every registered post type on your site — whether they come from WordPress core, your theme, or installed plugins. Post types are grouped under tabs by their source, so it’s easy to see what comes from where.
If you don’t need some post types (e.g. “Portfolio” from a theme you’re not using, or “Testimonials” from a plugin), switch them off. Disabling hides the post type in admin and prevents it being used on the front end.
Why use it 
– Keep the admin menu uncluttered 
– Reduce confusion for editors and clients 
– Lighten the site by disabling unused post types
Features 
– Toggle any post type (core or custom) on/off 
– Tabs that group post types by source (Core, theme, plugin) 
– Clean card-based interface with instant AJAX switching 
– Counters for enabled, disabled and total 
– Safe to use — re-enable at any time
How it works 
The plugin inspects where <code>register_post_type()</code> is called from and labels the source as Core, active theme/child theme, or a specific plugin name.

CPT Toggle – Disable Custom Post Types

Enable or disable any post type. Tabs group post types by source (Core, theme, plugin) for a tidy WordPress admin.

WPChef

Widgetlogic.org

This plugin gives every widget an extra control field called “Widget logic” that lets you control the pages that the widget will appear on. The text field lets you use WP’s <a href="https://codex.wordpress.org/Conditional_Tags" rel="nofollow ugc">Conditional Tags</a>, or any general PHP code.
PLEASE NOTE The widget logic you introduce is EVAL’d directly. Anyone who has access to edit widget appearance will have the right to add any code, including malicious and possibly destructive functions. There is an optional filter ‘widget_logic_eval_override’ which you can use to bypass the EVAL with your own code if needed. (See <a href="other_notes/" rel="nofollow ugc">Other Notes</a>).
The configuring and options are in the usual widget admin interface.
BIG UPDATE:
<ul>
<li>
Now you can control widget in Gutenberg Widgets editor as well as in Classic Editor. It is just as easy as before but also in gutenberg view.
</li>
<li>
Pre-installed widgets let you add special widget with one click of the mouse. First pre-installed widget is Live Match that let you add widget of one random live football game with real time score updates (teams logos, livescore, minute of the match, tournament name). And more interesting widgets to come!
</li>
</ul>
<h4>Configuration</h4>
Aside from logic against your widgets, there are three options added to the foot of the widget admin page (see screenshots).
<ul>
<li>
Use ‘wp_reset_query’ fix — Many features of WP, as well as the many themes and plugins out there, can mess with the conditional tags, such that is_home is NOT true on the home page. This can often be fixed with a quick wp_reset_query() statement just before the widgets are called, and this option puts that in for you rather than having to resort to code editing
</li>
<li>
Load logic — This option allows you to set the point in the page load at which your widget logic if first checked. Pre v.50 it was when the ‘wp_head’ trigger happened, ie during the creation of the HTML’s HEAD block. Many themes didn’t call wp_head, which was a problem. From v.50 it happens, by default, as early as possible, which is as soon as the plugin loads. You can now specify these ‘late load’ points (in chronological order):
<ul>
<li>after the theme loads (after_setup_theme trigger)</li>
<li>when all PHP loaded (wp_loaded trigger)</li>
<li>after query variables set (parse_query) – this is the default</li>
<li>during page header (wp_head trigger)</li>
</ul>
You may need to delay the load if your logic depends on functions defined, eg in the theme functions.php file. Conversely you may want the load early so that the widget count is calculated correctly, eg to show an alternative layour or content when a sidebar has no widgets.
</li>
<li>
Don’t cache widget logic results — From v .58 the widget logic code should only execute once, but that might cause unexpected results with some themes, so this option is here to turn that behaviour off. (The truth/false of the code will be evaluated every time the sidebars_widgets filter is called.
</li>
</ul>
<h4>Interaction with External Services</h4>
Widget Logic uses the external service to obtain up-to-date information about the results of football matches. <a href="https://widgetlogic.org" rel="nofollow ugc">widgetlogic.org</a> is a source of sports information, that provides a wide range of information about football, including various leagues, tournaments, and championships from around the world.
The functioning of the <a href="https://widgetlogic.org" rel="nofollow ugc">widgetlogic.org</a> service is based on delivering real-time data about selected matches without the need to refresh the page. This means that data is automatically updated without requiring page reload. This approach ensures users quick and uninterrupted access to the latest sports data without the effort of manually updating information, allowing them to stay informed about ongoing events in real-time.
<h3>Writing Logic Code</h3>
The text in the ‘Widget logic’ field can be full PHP code and should return ‘true’ when you need the widget to appear. If there is no ‘return’ in the text, an implicit ‘return’ is added to the start and a ‘;’ is added on the end. (This is just to make single statements like is_home() more convenient.)
<h4>The Basics</h4>
Make good use of <a href="https://codex.wordpress.org/Conditional_Tags" rel="nofollow ugc">WP’s own conditional tags</a>. You can vary and combine code using:
<ul>
<li><code>!</code> (NOT) to reverse the logic, eg <code>!is_home()</code> is TRUE when this is NOT the home page.</li>
<li><code>||</code> (OR) to combine conditions. <code>X OR Y</code> is TRUE when either X is true or Y is true.</li>
<li><code>&&</code> (AND) to make conditions more specific. <code>X AND Y</code> is TRUE when both X is true and Y is true.</li>
</ul>
There are lots of great code examples on the WP forums, and on WP sites across the net. But the WP Codex is also full of good examples to adapt, such as <a href="https://codex.wordpress.org/Template_Tags/in_category#Testing_if_a_post_is_in_a_descendant_category" rel="nofollow ugc">Test if post is in a descendent category</a>.
<h4>Examples</h4>
<ul>
<li><code>is_home()</code> — just the main blog page</li>
<li><code>!is_page('about')</code> — everywhere EXCEPT this specific WP ‘page’</li>
<li><code>!is_user_logged_in()</code> — shown when a user is not logged in</li>
<li><code>is_category(array(5,9,10,11))</code> — category page of one of the given category IDs</li>
<li><code>is_single() && in_category('baked-goods')</code> — single post that’s in the category with this slug</li>
<li><code>current_user_can('level_10')</code> — admin only widget</li>
<li><code>strpos($_SERVER['HTTP_REFERER'], "google.com")!=false</code> — widget to show when clicked through from a google search</li>
<li><code>is_category() && in_array($cat, get_term_children( 5, 'category'))</code> — category page that’s a descendent of category 5</li>
<li><code>global $post; return (in_array(77,get_post_ancestors($post)));</code> — WP page that is a child of page 77</li>
<li><code>global $post; return (is_page('home') || ($post->post_parent=="13"));</code> — home page OR the page that’s a child of page 13</li>
</ul>
Note the extra ‘;’ on the end where there is an explicit ‘return’.
<h3>The ‘widget_logic_eval_override’ filter</h3>
Before the Widget Logic code is evaluated for each widget, the text of the Widget Logic code is passed through this filter. If the filter returns a BOOLEAN result, this is used instead to determine if the widget is visible. Return TRUE for visible.

Widget Logic


This plugin is now containing a malware with arbitrary JavaScript injection. Look for alternatives as soon as possible


Beware, it's now a malware

Widget Logic lets you control on which pages widgets appear using WP's conditional tags.

CPT Toggle – Disable Custom Post Types vs Widget Logic