
BLACKSWAN | BLOCK EXTERNAL REQUEST
BlackSwan | Block External Request compatibility with REEID Translate
BlackSwan | Block External Request compatibility with REEID Translate is being reviewed using official plugin documentation. Intercepts and blocks server-side outgoing HTTP requests (wp_remote_get/post) via the pre_http_request filter using domain blacklists and URL whitelists. No specific text shown to visitors is currently confirmed for translation.
AWAITING VERIFICATION
What BlackSwan | Block External Request does
Official plugin information supports the compatibility context documented for this category.
MANUAL REVIEW
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
BlackSwan | Block External Request is documented in the Performance category with 6 documented features.
DOCUMENTATION REVIEW
We use official plugin documentation to describe what the plugin does. Translation support is listed only for text that can be identified and tested.
COMPATIBILITY REVIEW
How BlackSwan | Block External Request compatibility is evaluated
01 · Review official plugin documentation
Confirm documented plugin behaviour before making multilingual compatibility claims.
02 · Identify text shown to visitors
Check whether the documented features display text that visitors can read.
03 · Separate content from functionality
Structure, settings, logic, integrations and runtime behaviour are not treated as translatable content unless they include specific visible text.
04 · Confirm what can be translated
List supported content only after specific text shown to visitors has been identified and can be validated.
PLUGIN INFORMATION
What the plugin does
Plugin capabilities
- Intercepts and blocks server-side outgoing HTTP requests (wp_remote_get/post) via the pre_http_request filter using domain blacklists and URL whitelists.
- Deregisters enqueued JavaScript and CSS files from blacklisted external domains, with separate toggles for admin backend and public frontend.
- Blocks specific local or external JS/CSS resources by matching full URLs, partial paths, or filenames without requiring code edits.
- Replaces standard WordPress core asset sources with custom CDN URLs based on defined pattern-matching rules for improved performance.
- Provides a safe mode bypass (?bswan-safe=1) to temporarily disable all blocking mechanisms if access to wp-admin is lost.
- Stores all configuration settings as a single JSON option in wp_options with autoload disabled to minimize database query overhead.
TRANSLATION BOUNDARY
BlackSwan | Block External Request capabilities and translatable content are documented separately.
Official documentation describes the plugin functionality, but does not currently identify specific text shown to visitors that can be translated.
A feature is not considered translatable unless it includes text that users can read.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility. No specific content shown to visitors is confirmed for translation in this category.
FREQUENTLY ASKED QUESTIONS
BlackSwan | Block External Request and REEID Translate FAQ.
What does BlackSwan | Block External Request do?
BlackSwan | Block External Request has 6 documented features listed in its official documentation. See the Plugin Information section for details.
Does BlackSwan | Block External Request have any content currently confirmed for translation?
No specific content is currently confirmed for translation in this integration.
What needs to be confirmed before translating content from BlackSwan | Block External Request?
Official documentation must identify specific text, such as labels, titles, descriptions or messages, that can be tested in the integration.
RELATED GUIDES
Explore more compatibility guides.
COMPATIBILITY INFORMATION
Evaluate BlackSwan | Block External Request in a multilingual WordPress workflow.
REEID documents BlackSwan | Block External Request functionality separately from confirmed translation support so the distinction is clear.
Supported content will be listed when specific translatable text is identified in the official documentation.