web_share Shortcode
The web_share shortcode displays the sharing actions enabled under Theme settings → Templates → Blog → Post single. The current public page, author, taxonomy, posts page or post-type archive supplies the shared URL. Current titles and featured images are used where a network supports them. Reusable layouts share the page displaying them, not the layout itself.
The attributes below match the current Page Builder controls and public output. Use raw syntax only for reviewed content that cannot be maintained through the visual controls.
Usage
[web_share]Attributes
| Attribute | Default | Accepted values | Purpose |
|---|---|---|---|
device_visibility |
— | Space-separated web-hide-on-lg, web-hide-on-md, web-hide-on-sm, web-hide-on-xs |
Applies the selected responsive visibility rules. |
el_id |
— | Valid unique HTML ID | Assigns an ID to the sharing wrapper. |
el_class |
— | Space-separated CSS class names | Adds classes to the sharing wrapper. |
Theme-controlled actions
The shortcode follows the site's sharing enablement, alignment, shape, colors, label and per-network choices. Supported actions include Facebook, X, LinkedIn, Pinterest, Menéame, WhatsApp, email and copy URL. Disabled networks are omitted; copy URL remains available while sharing is enabled. The entire component remains empty when content sharing is disabled.
Email is available for published, publicly viewable content without a password or theme post-type permission rule. Archives have no email action or post counters. Each email form requires a destination, sender name and explicit recipient-permission confirmation; optional comments are plain text. Existing forms, Modal behavior and sharing assets are shared with Gutenberg. Multiple placements have independent forms.
Local counters measure sharing-action activations, not confirmed shares reported by external networks. Copying a URL is not counted. See the Share guide for rate limits, email delivery checks and cache considerations. The Gutenberg block also offers per-instance presentation overrides; these are not additional Legacy shortcode parameters.
Verification
Open the component on a single item and an author archive. Test every enabled action, verify generated URLs describe the current content, and confirm the email and copy-URL interactions work with keyboard input. Also check the disabled state does not leave an empty heading or wrapper visible.
Email tests should use a consenting recipient. A success response means the mail service accepted the message, not that delivery has been independently confirmed. Sharing works with static HTML page caches: each email or counter action obtains a fresh security token before submission. Changing the sharing configuration still requires refreshing the affected cached page so its visible controls match the current settings.