egemenerd

Shortcodes in WordPress comments, BuddyPress activities, bbPress topics and replies are disabled as default.
For example, let’s say you have a calendar plugin that produces a browsable calendar, which you embed to a page with a shortcode. What if you want to publish this calendar in a sticky topic in a forum? The shortcode will not evaluated, so you will just see literally the shortcode…
DV Shortcode Whitelist plugin allows you to enable the shortcodes in these fields with ease. You can enable all shortcodes or create whitelists to allow specific shortcodes.
Also you can enable the shortcodes for specific user roles or capabilities. For example, you can only allow site admins and forum moderators to use shortcodes.
Easy to use plugin settings allow you to enable or disable everything separately in a few clicks.
Documentation; http://www.wp4life.com/online/dvscwl/index.html

DV Shortcode Whitelist

I was looking everywhere for this.  "User Shortcuts" is what I googled and "buddypress user based shortcodes" but got nothing. 

I went on Buddypress.org and asked for support as these searches returned many results that did not do what this plugin does.  They told me it couldn't be done.  I started asking about hooks, and started researching hooks when I cam across another (out of date) plugin when I ran into this!

Thanks Guys/Gals, Ive tried it out and it does EXACTLY what I want it to do.  I need to create a shortcut for it to use, then present my users with that shortcut.  Perfect!  Now, I can update this information as we want without having to update the pages!  Woot!

Very Cool!  Thanks!

Thought I was screwed!

Shortcode Whitelist for bbPress, BuddyPress and WordPress Comments.

Amirhossein Hosseinpour

BlackSwanDev

BlackSwan Block External Request gives you granular control over every outgoing connection your WordPress site makes — both server-side PHP requests and browser-loaded JS/CSS resources.
WordPress, plugins, and themes constantly send background HTTP requests: update checks, license pings, analytics, font downloads, CDN calls, and more. On slow servers or restricted hosting environments, these requests can add seconds to every admin page load.
This plugin lets you block what you don’t need and keep what you do.
<h4>What it does</h4>
Server-side HTTP Blocking (PHP) 
Intercepts outgoing <code>wp_remote_get</code> / <code>wp_remote_post</code> calls via the <code>pre_http_request</code> filter. Add domains to the blacklist and they’ll be blocked before the request is even made. Whitelist specific URL patterns to let essential requests through (e.g. plugin update API).
Browser-side Resource Blocking (JS/CSS by Domain) 
Deregisters enqueued JavaScript and CSS files loaded from blacklisted external domains. Toggle separately for admin panel and public frontend. Your own site’s assets are never touched.
Block Specific Resources (by URL) 
Block individual JS or CSS files by full URL, partial path, or even just a filename — works for both local and external resources. Per-item backend/frontend toggle. Perfect for removing unwanted plugin assets without editing code.
<h4>Features</h4>
<ul>
<li>Blacklist & whitelist with inline edit, delete, and delete-all</li>
<li>Block external JS/CSS by domain (backend, frontend, or both)</li>
<li>Block specific resources by URL pattern (local or external)</li>
<li>One-click pause/resume — instantly disable all blocking</li>
<li>Safe mode via <code>?bswan-safe=1</code> — emergency bypass for any admin page</li>
<li>Settings page auto-bypasses resource blocking so you never lock yourself out</li>
<li>Export/import all settings as a single JSON file</li>
<li>AJAX-powered save — no page reloads</li>
<li>Query Monitor integration — detect, activate, or install from settings</li>
<li>All settings stored as a single JSON option with <code>autoload=no</code> for performance</li>
<li>Fully standalone — zero external dependencies (inline Lucide SVG icons)</li>
<li>Modern liquid glass UI with dot-grid background</li>
<li>WordPress native postbox layout with collapsible sections</li>
<li>Translation-ready with full text domain support</li>
</ul>
<h4>Who is this for?</h4>
<ul>
<li>Sites on slow or restricted hosting where external calls cause timeouts</li>
<li>Developers debugging performance issues</li>
<li>Agencies managing client sites that don’t need update checks</li>
<li>Anyone who wants a faster wp-admin experience</li>
</ul>
<h4>Developer Hooks</h4>
Four filters are available for developers to customize blocking behavior programmatically. These run on every page load and merge with the values from the settings page.
<code>BlackSwan\block_external_request\block_url_list</code>
Filter the array of blocked domain strings. Each entry is matched via <code>strpos()</code> against the full request URL.
<pre><code>add_filter( 'BlackSwan\block_external_request\block_url_list', function( $domains ) {
 $domains[] = 'analytics.example.com';
 return $domains;
});
</code></pre>
<code>BlackSwan\block_external_request\whitelist_urls</code>
Filter the array of whitelisted URL patterns. If a blocked URL also matches a whitelist pattern (via <code>strpos()</code>), the request is allowed through.
<pre><code>add_filter( 'BlackSwan\block_external_request\whitelist_urls', function( $patterns ) {
 $patterns[] = '//api.example.com/v2/license';
 return $patterns;
});
</code></pre>
Whitelist patterns take priority over blacklist domains. Both filters accept and return a flat array of strings.
<code>BlackSwan\block_external_request\blocked_resources</code>
Filter the array of specific JS/CSS resources to block. Each entry is an associative array with <code>url</code>, <code>backend</code>, and <code>frontend</code> keys. The <code>url</code> is matched via <code>strpos()</code> against each registered script/style source.
<pre><code>add_filter( 'BlackSwan\block_external_request\blocked_resources', function( $resources ) {
 $resources[] = array( 'url' => 'some-plugin/tracking.js', 'backend' => false, 'frontend' => true );
 return $resources;
});
</code></pre>
<code>BlackSwan\block_external_request\cdn_replacements</code>
Filter the array of CDN replacement rules. Each entry is an associative array with <code>pattern</code>, <code>cdn</code>, <code>backend</code>, and <code>frontend</code> keys. When an enqueued asset source contains the <code>pattern</code>, it is replaced with the <code>cdn</code> URL.
<pre><code>add_filter( 'BlackSwan\block_external_request\cdn_replacements', function( $replacements ) {
 $replacements[] = array( 'pattern' => '/wp-includes/js/jquery/jquery.min.js', 'cdn' => 'https://cdn.example.com/jquery/3.7.1/jquery.min.js', 'backend' => false, 'frontend' => true );
 return $replacements;
});
</code></pre>
<h4>Links</h4>
<ul>
<li><a href="https://amirhp.com/" rel="nofollow ugc">Developer — AmirhpCom</a></li>
<li><a href="https://blackswandev.com/" rel="nofollow ugc">BlackSwan</a></li>
<li><a href="https://github.com/blackswandevcom/blackswan-block-external-request/" rel="nofollow ugc">Plugin GitHub Page</a></li>
<li><a href="https://wordpress.org/support/plugin/blackswan-block-external-request/reviews/#new-post" rel="ugc">Rate 5-Star</a></li>
<li><a href="https://wordpress.org/support/plugin/blackswan-block-external-request/" rel="ugc">Support & Issues</a></li>
</ul>
<h3>Copyright</h3>
BlackSwan Block External Request is free software distributed under the terms of the GNU General Public License v2 or later.
Copyright (c) AmirhpCom — <a href="https://amirhp.com/" rel="nofollow ugc">amirhp.com</a>
This plugin is developed and maintained by <a href="https://blackswandev.com/" rel="nofollow ugc">BlackSwan Lab</a>.
You are free to use, modify, and distribute this plugin under the GPLv2 license. The developers are not responsible for any issues caused by misconfigured blocking rules. Always maintain proper backups before making changes to your site’s HTTP request behavior.

BlackSwan | Block External Request

Block unwanted external HTTP requests in WordPress. Blacklist/whitelist management, resource blocking, and one-click pause.

DV Shortcode Whitelist vs BlackSwan | Block External Request