BASIC URL SHORTCODES

Basic URL ShortCodes compatibility with REEID Translate

Basic URL ShortCodes compatibility with REEID Translate is being evaluated from available plugin evidence. Provides multiple shortcodes that output core WordPress URLs (e.g., home_url, site_url, theme_url_template, parent_theme_url, upload_url/UPLOAD_URL, content_url, plugins_url, admin_url, rest_url, login_url/logout_url, current_url). No specific visitor-facing translation surface is currently confirmed.

Visit Basic URL ShortCodes ↗

AWAITING VERIFICATION

What the available evidence establishes for Basic URL ShortCodes.

Official plugin information supports the compatibility context documented for this category.

AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.

PLUGIN PROFILE
Basic URL ShortCodes is documented in the Navigation category with 7 concrete capabilities identified in the current evidence.

EVIDENCE COVERAGE
Plugin capabilities are documented from available official evidence. Translation support is listed only when concrete visitor-facing content is explicitly established.

COMPATIBILITY REVIEW

How Basic URL ShortCodes compatibility is evaluated

01 · Review official plugin evidence
Establish documented plugin behaviour before making any multilingual compatibility claim.

02 · Identify visitor-facing content
Determine whether the documented behaviour exposes human-readable values that visitors can see.

03 · Separate content from functionality
Keep structure, configuration, logic, integrations and runtime behaviour outside translation scope unless concrete content values are identified.

04 · Confirm translation scope
Publish supported content only when concrete visitor-facing values are explicitly established and can be validated.

PLUGIN INTELLIGENCE

What the official plugin evidence shows

Plugin capabilities

  • Provides multiple shortcodes that output core WordPress URLs (e.g., home_url, site_url, theme_url_template, parent_theme_url, upload_url/UPLOAD_URL, content_url, plugins_url, admin_url, rest_url, login_url/logout_url, current_url).
  • Supports an optional `path` attribute for most shortcodes to append a path segment to the generated URL (example: `[home_url path="contact"]`).
  • Implements safety checks for `path`: if `path` starts with a URL scheme (`http:`), a protocol-relative prefix (`//`), or a backslash, the value is ignored to prevent off-site targeting.
  • Escaping behavior is configurable via `esc` attribute: defaults to HTML entity encoding, and `esc="raw"` skips HTML entity encoding (intended for JavaScript consumption rather than `href`).
  • For login/logout shortcodes, supports an optional `redirect` attribute; off-site redirect targets are rejected.
  • Registers prefixed alias shortcode tags with a `burl_` prefix (e.g., `[burl_home_url]`) to avoid clashes; if an unprefixed tag is already taken by another plugin, this plugin leaves it alone rather than overriding it.
  • Renders shortcodes in widgets: runs shortcodes through classic text widgets, and in the block editor a Shortcode block can be used.

CONTENT BOUNDARY

Basic URL ShortCodes capabilities and translation scope are documented separately.

The available evidence documents plugin functionality, but does not currently establish a specific visitor-facing translation surface.

Functional capability alone is not treated as evidence that a value should be translated.

LIMITATIONS & QA

Verification notes

  • This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.

COMMON QUESTIONS

Basic URL ShortCodes and REEID Translate FAQ.

What does Basic URL ShortCodes do according to the available plugin evidence?

Basic URL ShortCodes has 7 concrete capabilities documented from the currently available official plugin evidence. See the Plugin Intelligence section for the individual capabilities.

Is a REEID translation surface currently confirmed for Basic URL ShortCodes?

No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.

What would establish translation scope for Basic URL ShortCodes?

The evidence must identify concrete visitor-facing values such as labels, titles, descriptions, messages or other human-readable content that can be validated through the integration workflow.

RELATED GUIDES

Continue through the compatibility library.

INTEGRATION EVIDENCE

Evaluate Basic URL ShortCodes in a multilingual WordPress workflow.

REEID documents Basic URL ShortCodes functionality separately from evidence-backed translation support so compatibility claims remain specific and testable.

Translation scope will be published when concrete visitor-facing content is established by evidence.

Shopping Cart
Scroll to Top