Release Notes - WebinarJam & EverWebinar

Product Key: WJ = specific to WebinarJam, EW = specific to EverWebinar, WJEW = applies to both services.

Improvements

  • CAPTCHA Update and Honeypot field
    • Introduced a hidden honeypot field to silently block bot submissions while avoiding friction for real registrants.
    • Added a new Captcha section in the Wizard → Registration section, allowing you to enable/disable CAPTCHA for registration and login pages. This option is off by default, and the setting carries to clones. (3760 WJEW)
  • Support uploading videos up to 200MB to inject into the live stream (not only external URLs). Upload via both live room and wizard. (3759 WJ)

Fixes

  • Fixed a 500‐error scenario that left a live event with a “finished” broadcast status, causing it to get stuck and unable to go live again. (3810 WJ)

  • Investigated and fixed a cluster of severe incidents (white screens, no audio/video, no replay, unrecoverable sessions, panic button not working) tied to 8pm FR time broadcasts across multiple customers. (3728 WJ)
  • Fixed looping behavior in EverWebinar where a segment of the video was replayed, causing the webinar to extend beyond its configured duration and apparently “never stop”. (3751 EW)

  • Resolved a mobile UX bug where entering chat comments caused the EverWebinar video to shift from centered to left‑aligned and get partially cut off. (3753 EW)

  • Fixed YouTube countdown videos that had no sound on the registration > countdown flow, unless “Show controls” was enabled. Now audio behavior is consistent regardless of that control setting. (3674 EW)

  • Resolved a bug where, for certain sessions, only confirmation emails were sent while pre‑webinar reminders, last‑minute reminders, and post‑webinar emails did not go out, despite correct WJ mail configuration and DKIM. (3634 WJ)

  • Implemented fix to ensure data from registration form custom fields is actually transmitted through Zapier to downstream systems, not just the field definitions. (3767 WJEW)

  • Corrected logic for time‑based tagging rules (e.g., left before 25 minutes, stayed at least 55 minutes), so attendees are tagged accurately based on actual watch time. (3625 WJEW)

  • Fixed cases where the {LIVE_LINK} shortcode produced a valid-looking link that redirected to an invalid page. (3310 WJEW)

  • Resolved validation/handling issue where some valid URLs (e.g. specific privacy‑policy links) were rejected in the Twilio SMS opt‑in text, while generic URLs like google.com worked. (3804 WJEW)