Fixes the dashboard video analytics widget: it read SAPI responses at the wrong path and quietly rendered the "no data" empty state even on publications with real traffic. After upgrading, the widget now shows Views \/ Player Loads \/ Play Rate, Top 5 Videos, and the device breakdown. Also adds a one-click admin notice when the plugin is installed but has no API credentials yet, and a red error panel inside the widget when a SAPI call fails (instead of the misleading empty state).<\/p>","2.0.1":"
This is the first 2.x release shipped via wordpress.org (2.0.0 was distributed via GitHub only). Upgrading from 1.x is a MAJOR update with breaking changes: requires PHP 8.1+, replaces the upload flow with direct browser-to-storage uploads, removes the blue_billywig_progress_list filter, and REST endpoints now require authentication. Read the 2.0 migration guide in USER-GUIDE.md before updating in production. 2.0.1 itself adds a fail-closed fix to the content-gate recursion cap, observability for gate-error and JWT-pepper persistence failures, a Solr-fq validation parity fix on a library AJAX endpoint, and regression tests.<\/p>","2.0.0":"
Major update with breaking changes. Direct browser-to-storage uploads via Uppy (no more PHP upload limits), Gutenberg blocks with SEO, oEmbed support, content protection, video analytics dashboard, folder browsing, and more. Requires PHP 8.1+. The blue_billywig_progress_list filter has been removed \u2014 see release notes if you used it in custom code.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3041421,"resolution":"128x128","location":"assets","locale":""},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3041423,"resolution":"256x256","location":"assets","locale":""},"icon.svg":{"filename":"icon.svg","revision":3041424,"resolution":false,"location":"assets","locale":false}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3041420,"resolution":"1544x500","location":"assets","locale":""},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3041418,"resolution":"772x250","location":"assets","locale":""}},"assets_blueprints":{},"all_blocks":{"bluebillywig\/embed":{"name":"bluebillywig\/embed","title":"Blue Billywig Clip"},"bluebillywig\/channel":{"name":"bluebillywig\/channel","title":"Blue Billywig Channel"},"bluebillywig\/shorts":{"name":"bluebillywig\/shorts","title":"Blue Billywig Shorts"}},"tagged_versions":["1.0.0","1.0.1","1.0.10","1.0.11","1.0.12","1.0.13","1.0.14","1.0.15","1.0.2","1.0.3","1.0.4","1.0.5","1.0.6","1.0.7","1.0.8","1.0.9","2.0.1","2.0.2"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3041425,"resolution":"1","location":"assets","locale":""}},"screenshots":[],"jetpack_post_was_ever_published":false},"plugin_section":[],"plugin_tags":[224718,224717,224716,222],"plugin_category":[50],"plugin_contributors":[224719],"plugin_business_model":[],"class_list":["post-180088","plugin","type-plugin","status-publish","hentry","plugin_tags-billywig","plugin_tags-blue-billywig","plugin_tags-bluebillywig","plugin_tags-video","plugin_category-media","plugin_contributors-bluebillywig","plugin_committers-bluebillywigplugin"],"banners":{"banner":"https:\/\/ps.w.org\/blue-billywig\/assets\/banner-772x250.png?rev=3041418","banner_2x":"https:\/\/ps.w.org\/blue-billywig\/assets\/banner-1544x500.png?rev=3041420","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":"https:\/\/ps.w.org\/blue-billywig\/assets\/icon.svg?rev=3041424","icon":"https:\/\/ps.w.org\/blue-billywig\/assets\/icon.svg?rev=3041424","icon_2x":false,"generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/blue-billywig\/assets\/screenshot-1.png?rev=3041425","caption":""}],"raw_content":"\n
The Blue Billywig plugin enhances Blue Billywig's capabilities by integrating with WordPress. This plugin allows users to seamlessly upload media directly to their Blue Billywig publication.<\/p>\n\n
Documentation:<\/strong> See USER-GUIDE.md in the plugin directory for a complete walkthrough of all features.<\/p>\n\n This plugin relies on the Blue Billywig Online Video Platform to provide video uploading capabilities. By using this plugin, you acknowledge and agree to the following:<\/p>\n\n What data is transmitted to Blue Billywig from site visitors?<\/strong><\/p>\n\n Every page that embeds a Blue Billywig video loads the player from Consent integration (GDPR \/ ePrivacy \/ TTDSG).<\/strong><\/p>\n\n The plugin exposes a WordPress filter When this filter returns Cookies and local storage.<\/strong><\/p>\n\n CTA email capture \u2014 consent.<\/strong><\/p>\n\n The CTA editor can optionally include an email-capture form. The plugin requires an explicit consent checkbox on the form and rejects non- Content protection JWT.<\/strong><\/p>\n\n When you enable JWT-based content protection and a logged-in WordPress user requests a protected clip, a short-lived token (\u2264 7200s, clamped) is minted. The user-ID claim in the token is an HMAC of the WordPress user ID (never the raw ID) using Admin-side third-party code.<\/strong><\/p>\n\n On plugin admin pages, the Uppy uploader library is bundled locally ( Uninstall.<\/strong><\/p>\n\n Uninstalling the plugin deletes every The plugin ships with starter translations for German, French, Swedish, Danish, Norwegian Bokm\u00e5l, Finnish, and Dutch (in Please help us improve them.<\/strong> Once the plugin is listed on wordpress.org, any translation you contribute at translate.wordpress.org\/projects\/wp-plugins\/blue-billywig<\/a> automatically rolls out to every site running that locale \u2014 no plugin release required. If you already translate other WordPress plugins, the process is the same; if you don't, it takes about five minutes to sign up and suggest a correction.<\/p>\n\nThird-Party Service Integration<\/h3>\n\n
\n
Privacy & GDPR<\/h3>\n\n
{publication}.bbvms.com<\/code>. When the script runs, the visitor's IP address, User-Agent, Referer and page URL are transmitted to Blue Billywig so the player can fetch the clip, apply geo\/language rules, and record analytics.<\/p>\n\nbluebillywig_consent_granted<\/code> so consent-management plugins (Complianz, Cookiebot, Iubenda, Osano, \u2026) can defer loading the player until the visitor opts in:<\/p>\n\nadd_filter( 'bluebillywig_consent_granted', function() { return your_cmp_has_video_consent(); } );\n<\/code><\/pre>\n\nfalse<\/code>, BB embed blocks, channel blocks, Shorts blocks, shortcodes, and oEmbed all render a neutral placeholder explaining that loading will transmit data to bbvms.com. No IP\/UA is shipped to Blue Billywig until consent is granted (or until the visitor reloads after accepting).<\/p>\n\n\n
bbtl_{clipId}<\/code> to the visitor's localStorage<\/code> after a successful submit, so the form does not re-ask an engaged visitor. This key only carries the submitted email and a timestamp.<\/li>\n.bbvms.com<\/code> domain for playback\/analytics. See Blue Billywig's privacy statement for details.<\/li>\n<\/ul>\n\nhttps<\/code> submit endpoints. Captured emails are sent to the customer-configured endpoint (if any); Blue Billywig's own backend does not receive or store these emails.<\/p>\n\nwp_salt('auth')<\/code>. Pages carrying a JWT emit Cache-Control: private, no-store<\/code> to keep shared caches from serving one user's token to another.<\/p>\n\nadmin\/assets\/vendor\/uppy\/<\/code>) \u2014 no request to releases.transloadit.com<\/code> on every admin page load.<\/p>\n\nblue-billywig-*<\/code> option (including stored API keys and the content-protection shared secret) and every bb_*<\/code> transient. A reinstall starts from a clean slate.<\/p>\n\nTranslators<\/h3>\n\n
\/languages\/<\/code>). They were generated automatically and cover every string, but they have not been reviewed by native speakers.<\/p>\n\n