Description
Capitol GAINS (Government Archives & Information Navigation Suite) is a comprehensive WordPress plugin that provides a suite of tools for managing congressional operations, including meetings, participants, members, files, and related data. The plugin integrates with Advanced Custom Fields (ACF) Pro and Elementor for content management and display.
Key Features
- Meeting Management: Create, update, and manage congressional meetings with full metadata support
- Participant & Member Tracking: Manage witnesses, nominees, and committee members
- File Management: Upload and organize meeting files with embargo support
- REST API: Complete REST API for external system integration
- CSV Import: Bulk import meetings, panels, panel members, members, participants, and files via CSV
- Elementor Integration: Custom widgets for displaying meetings, files, filters, and more
- Live Meetings: Support for live streaming and upcoming meeting alerts
- Advanced Filtering: Dynamic filter system with real-time count updates
- Preview System: Generate previews of meetings before publishing
Requirements
- WordPress: 6.4.0 or higher
- PHP: 7.4 or higher
- ACF Pro: Required (plugin will show notice if not active)
- Elementor: Optional but recommended for frontend display
Custom Post Types
The plugin registers the following custom post types:
- Meetings (
meeting) – Main meeting post type - Participants (
meeting_participant) – Witnesses and nominees - Members (
meeting_member) – Committee members - Meeting Files (
meeting_file) – Files associated with meetings
Taxonomies
- Meeting Status (
meeting_status) - Meeting Type (
meeting_type) - Committee Type (
committee_type) - Privacy Type (
privacy_type) - Congress (
congress) - Subcommittee (
subcommittee) - Participant Type (
participant_type)
Taxonomies can be enabled/disabled and assigned to different post types via plugin settings.
Database
The plugin uses custom database tables for optimized data storage:
wp_capigacr_meetingmeta– Meeting metadatawp_capigacr_participantmeta– Participant metadatawp_capigacr_membermeta– Member metadatawp_capigacr_filemeta– File metadata
Database migrations are handled manually via admin UI.
API Integration
The plugin provides a comprehensive REST API for external system integration with endpoints for:
- Creating and updating meetings
- Managing files
- Checking meeting existence
- Getting live meetings
- Filter counts
- Preview generation
Base URL: /wp-json/meetings/v1/
External Services
This plugin may fetch data from external services in the following scenarios:
- File Imports: When importing files via CSV, the plugin may download files from external URLs if specified in the import data. This is user-initiated and requires explicit import action.
- Congress.gov Member Roster: The plugin can fetch Senate roster and member data from the Congress.gov API (
api.congress.gov), operated by the Library of Congress. This request only fires when a site administrator has entered a Congress.gov API key in Meetings Settings, and only while that administrator is browsing the member picker on a meeting edit screen or selecting a senator from it — with no key entered, no request is ever made. Each request sends the site’s Congress.gov API key in a request header, the congress number being browsed, and, when a senator is selected, that senator’s bioguide identifier; no site content, user data, or personal information is sent. The service returns public-domain congressional member records (name, party, state, chamber, official website), which are stored on the created member post. See the Congress.gov / Library of Congress terms of use and privacy policy.
All external requests use WordPress’s built-in HTTP API with proper SSL verification and timeouts.
Installation
- Upload the plugin files to
/wp-content/plugins/creativengine-congressional-utilities/ - Activate the plugin through the WordPress admin panel
- Ensure ACF Pro is installed and activated
- Database tables will be created automatically on activation
- Configure settings via the Meetings and CE Utilities settings sub-menu items in the WordPress admin
FAQ
What are the requirements for this plugin?
This plugin requires WordPress 5.0 or higher, PHP 7.4 or higher, and Advanced Custom Fields Pro. Elementor is optional but recommended for frontend display.
How do I create a meeting?
Meetings can be created via:
* WordPress Admin: Create a new Meeting post type
* REST API: Use the /wp-json/creativengine-meetings/v1/write endpoint
* CSV Import: Import meetings in bulk via the admin import interface
How do I use the Elementor widgets?
- Edit a page with Elementor
- Add widgets from the CE Utilities category
- Configure widget settings
- Publish the page
Available widgets include Meeting Display, Meeting Files, Meeting Info, Live Meetings Alert, Meeting Filters, Search Button, and more.
Can I import meetings in bulk?
Yes, the plugin supports CSV imports for meetings, panels, panel members, participants, members, and files. Access the import interface via Meetings → Import in the WordPress admin.
What is the REST API base URL?
Frontend endpoints use /wp-json/creativengine-capitol-gains/v1/. Proforma/admin endpoints use /wp-json/creativengine-meetings/v1/. See the plugin documentation for complete API endpoint details.
Changelog
1.5.0
- Security: Embargoed meeting files are now real scheduled posts that WordPress publishes automatically at their release time. Logged-out visitors get a 404 on an embargoed file’s address instead of being redirected to the file, and, as with any scheduled post, embargoed files are left out of REST listings and sitemaps until they are released.
- Fix: The file-link endpoint used by the embargo countdown now only returns a file that belongs to the requested meeting and has been released (it previously returned any file’s address).
- Change: Only files Proforma flags as embargoed are held. Unflagged files — including CSV-imported and WordPress-created files — are no longer hidden on meetings that have an embargo date or have not started yet. A flagged file with no embargo date is held until the meeting starts.
- Change: A meeting file’s Publish status and date now follow its meeting’s embargo settings; manual changes are reset on save with a notice, and any manual draft/private/pending status that is replaced is kept in the file’s
_capigacr_file_prior_statusfield. - New: A one-time background update runs after you click Run Update for the database update (database version 1.20.0). It applies the new rules to files that already exist, in small batches, as administrators browse wp-admin or from the “Run now” link in the admin notice, and it can be re-run safely. Files whose embargo flag cannot be recovered from stored data are treated as not embargoed and stay published. Until the update has run and finished, an embargoed file that was already published before this release is still hidden on meeting pages and refused by the file-link endpoint, but it is not yet a scheduled post. After it finishes, purge any page cache and the Elementor element cache once: a cached page, or a widget individually set to Elementor’s “Element Caching” option, can keep serving the previous version of a meeting page.
- Removed: The public embargo-status response no longer includes the meeting’s original_id.
- Note: While files are uploaded through the Proforma API, a new file can be briefly public until its meeting data arrives (one sync).
- Known limitation: A file’s direct uploads address (/wp-content/uploads/…) is served by the web server and cannot be protected by post status; anyone who already has that exact address can download it before release. Use host-level rules if that matters for your site.
- Security: The embargoed file block shortcode (
[capigacr_file_block]) no longer prints a held file’s download link to logged-out visitors when it sits on an ordinary page; the held state is now worked out from the file’s own meeting, and a file that is not published is treated as held, so the shortcode answers “File not found.” for it. Files that are not embargoed still show their link. - Security: Adding
?preview=trueor?preview=1to an embargoed file’s address no longer shows the file’s page to logged-out visitors; they get the same 404 as without it, on both the pretty address and the?p=address. Only a user who can edit the file can still preview it. - Fix: Moving a file to a different meeting now recomputes its embargo state immediately, so the file follows the new meeting’s release time instead of keeping the old meeting’s; previously a held file could be published early, or a released one left hidden, until some other change touched it. Saving the same meeting again or changing another field changes nothing.
- Fix: A CSV bulk update of a meeting’s start date now recomputes the embargo state of the live meeting’s files; previously, when a preview copy of the same meeting existed, the update could pick the preview copy and leave the live meeting’s files on their old release time.
- Fix: The embargo recompute that runs at the end of a request is now capped per meeting and logs a warning when the cap is reached, so a third-party hook that keeps re-triggering a recompute can no longer make a request loop indefinitely.
- Fix: The one-time embargo update now reports a file it could not update as an error instead of counting it as unchanged: the Tools page shows a warning with the error count, the runner message reads “Finished with errors.” instead of “Complete.”, and the details are written to the plugin log. Previously a failed write on a still-public embargoed file looked like a clean run.
- Fix: The one-time embargo update is safer to run alongside another batch: it takes its lock before reading its progress, so a batch that finished a moment earlier is no longer overwritten, and it flushes the object cache’s in-memory copy only from the admin runner and only on cache backends that support it, never in the middle of an ordinary administrator page load.
- New: Loop Grid widgets gained a “Multiple Sources” option on the Source dropdown for multi-source queries, letting an admin combine several post types in one grid — each with its own taxonomy/term filter — into a single query with native pagination and ordering, instead of needing a separate grid per post type.
- Fix: Manually including or excluding specific posts on a Loop Grid using Multiple Sources now works — the Query section’s own Include/Exclude “Search & Select” pickers previously returned no results at all for these grids, so a post could not be selected either way.
- New: A Loop Filters widget paired with a multi-source Loop Grid now computes its dropdown options and their available/unavailable state across every post type the grid combines, instead of only the first one — so a term that exists only on one of the combined sources is now offered at all, and options with no matching posts anywhere in the grid’s combined scope are correctly greyed out. A Loop Filters widget paired with an ordinary single-post-type grid behaves exactly as before. Elementor’s native Include/Exclude post pickers on a multi-source Loop Grid now search the grid’s own configured source post types instead of an unscoped, site-wide search, and no longer offer results outside those types.
- New: Loop Filters taxonomy and date filter rows gained a “Hide field when empty” switcher, above “Show only available options” — when enabled, a filter field is removed from the page entirely (not just greyed out) if it would offer zero selectable options for the widget’s post type and Base Scope; a widget with no row using this toggle issues no additional queries.
- Fix: A meeting’s files were displaying the long physical upload filename, random identifier and all, instead of the clean name configured for the file — the file-upload step of a publish was overwriting the name the meeting snapshot had just set moments earlier. The archive/Amend Export import path, which supplies its own genuine display name, still renames files exactly as it always has.
- Fix: A file could silently fail to upload during a Proforma publish, leaving no meeting file at all and nothing in the log to explain why — a dropped upload was indistinguishable from a request that was never sent. A failed file upload now still appears in the files list with a “missing” status, and the cause (including a truncated transfer) is written to the log, so a silent failure can finally be told apart from one that simply never happened.
- Fix: The Re-check Meeting Files tool (Tools → Congress Utilities) reported every single file as skipped and never updated any file’s status — it looked for the file URL and status in post meta, while that data actually lives in the plugin’s own file meta table, so no record ever had anything to check, and nothing it did write was ever read back by the Files list. The tool now also flags records with no recorded file URL as missing instead of passing over them silently, which is the state a failed Proforma file upload (fixed above) leaves behind.
- Fix: Meeting files still showed the long physical upload filename, random identifier and all, instead of the clean configured name — this is the complementary half of the fix above: that one stops an existing name from being overwritten, but files created fresh by the upload step itself (most commonly amendment files, which have no earlier record for that fix to protect) were never given the right name in the first place, because the upload endpoint was ignoring the clean display name Proforma already sends alongside the file. Renaming a file in Proforma now also updates the existing record’s name the next time it is published.
- Fix: Changing the Meeting permalink slug away from the default
meetingscould silently replace an existing page at that same slug (e.g. an Elementor page) with the plugin’s built-in meeting archive — WordPress gives post-type archive rewrite rules priority over a page’s own rewrite rule whenever they share a slug. The Meeting post type’s built-in archive is now disabled by default, since the plugin does not rely on it. After updating, resave Settings > Permalinks (or otherwise flush rewrite rules) for the change to take effect.
1.4.8
- Removed: The built-in redirect utility and its Migration-tab settings are gone in favor of the site’s dedicated redirect plugin; existing redirect data is left untouched.
- Fix: Loop Filters “Post Meta (ACF)” date source with Meta Type “Date (Y-m-d)” matched no posts — the availability range bounds were built as hyphenated
Y-m-dwhile ACF’s Date Picker actually persists compactYmdon disk, so theCHAR BETWEENcomparison could never match. - Fix: A Loop Filters taxonomy dropdown could omit a newly assigned term for up to five minutes — its cached term list was not covered by the availability cache invalidation, so a term-only change had to wait out the cache’s TTL instead of appearing immediately.
- Fix: Loop Filters options with no matching posts now render greyed out and disabled when “Show only available options” is off, as the control’s own description already promised — previously the toggle also gated whether availability was computed at all, so with the default (off) setting nothing happened.
- Fix: A Loop Filters widget with more than one date item ignored the per-item “Date Source” setting on all but the first item — a Year item set to Post Meta (ACF) silently filtered on the post date whenever a Month item was ordered before it.
- Fix: A failed Loop Filters availability query (e.g. a transient database error) is no longer indistinguishable from a genuine “no matching posts” result — previously both rendered every dropdown option (including Month and Year) as disabled. The availability aggregates now check for a database error and fail open (all years/months enabled; the affected taxonomy is left unrestricted) instead of disabling the entire filter UI, and the degraded result is never cached.
- Fix: Loop Filters availability could silently render every dropdown option (Month, Year, and taxonomy terms) as disabled on a post type with several thousand posts — the availability aggregates built a temporary list of every matching post ID and spliced it into a SQL
IN (...)clause, so the generated statement’s length scaled with the size of the post type. Past roughly 16KB of SQL the statement was silently discarded before reaching the database (no error raised), and the resulting empty result was indistinguishable from “no posts match.” The aggregates now express each active taxonomy/date filter as a size-bounded database-level lookup instead of an enumerated post-ID list, so the generated SQL’s size no longer depends on how many posts the post type has. - New: The Loop Filters widget’s Linking section gained a Base Scope setting where you name a taxonomy and one or more term slugs, so that when the paired Loop Grid is itself restricted to a term, the filter dropdowns compute which years, months and terms actually have matching posts inside that restriction instead of across the whole post type — previously options with no matches inside the grid’s scope still appeared selectable. Shared-template widgets can set a different base scope per mapped page, and a widget with no base scope behaves exactly as before.
- Fix: When a Loop Grid’s own taxonomy restriction was configured to match any of several terms, applying a filter from the dropdowns widened the results instead of narrowing them, because the filter was combined with the grid’s restriction using the grid’s own “any of” logic rather than being required on top of it.
- New: The Select Participant modal’s Create New form now offers all 8 editable participant fields (Salutation, Middle Name, Suffix, Title, Title (Additional), Organization, City, State) instead of just Title and Organization, so a quick-created participant no longer needs a second trip through the participant’s own edit screen to fill in the rest. The Select Member modal’s Create New form (Party, State) is unchanged.
- Fix: The Select Participant modal’s Create New form now lists its name fields in the same order as the participant edit screen (Salutation, First Name, Middle Name, Last Name, Suffix) ahead of Title, Title (Additional), Organization, City and State — previously First Name and Last Name were always pinned to the top of the form regardless of the other fields’ order. The Select Member modal’s field order is unchanged.
- Fix: The Select Participant and Select Member modals’ “Create and select” button no longer gets stuck disabled after a successful quick-create — previously the first successful quick-create anywhere on the page left the button permanently disabled for the rest of that page load, silently blocking any further quick-create attempt and even leaving the button pre-disabled the next time the modal was reopened on another row. Several people can now be quick-created in a row in one sitting, for both members and participants.
- New: A participant’s Participant Type (Panel Witness or Nominee) is now set when the meeting is saved, based on which repeater the participant ends up in — a panel’s member list, the nominations list, or both — rather than at the moment they are picked or created in the Select Participant modal. A row added and then removed before saving never leaves a stray type behind, and a participant who appears in both lists carries both types rather than one replacing the other. The Select Member modal is unaffected.
- Fix: Removing a nominee from a saved meeting’s nominations list now correctly unlinks that meeting from the nominee’s own participant record, matching the behavior meeting members and panel participants already had — previously a nominee kept a meeting on their record forever once added, even after being removed from it.
- New: The participant Location field is now split into separate City and State fields, populated automatically by normalizing the raw “City, ST” value from imported meeting snapshots. Existing participants keep working without re-import — their City and State are resolved from the previously-stored value on read, and the combined location is kept up to date automatically wherever it is still used.
- New: The participant edit screen gained a Display Mode toggle so the individual Title/Agency/City/State fields and the Formatted Display editor no longer compete for the same space — only one is shown at a time, and switching back never loses whatever was entered in the hidden one.
- New: The participant edit screen now has a dedicated Participant Name box above Participant Data, and the Formatted Display editor moved into the Participant Data box alongside the Display Mode toggle that controls it. No stored participant data changes.
- Fix: Importing a meeting snapshot no longer discards the pre-rendered witness display text that Proforma supplies for panel witnesses — it now populates the participant’s Formatted Display editor on import, exactly as it already did for witnesses whose display text the plugin generates itself.
- Fix: A witness or nominee whose Formatted Display content was already stored now actually renders it on the front end — previously the display content was dropped while assembling the panel or nomination listing, so a participant set to Formatted Display mode appeared as though it had none.
- New: The Panels and Nominations widgets now render a witness’s or nominee’s Formatted Display content in place of the configured Member Details fields whenever it has been set, and each widget’s Style tab gained a new Formatted Display section for typography, color, and spacing.
- Fix: A participant’s pre-rendered Formatted Display content arriving in an imported meeting snapshot lost all of its formatting and collapsed onto a single line, because the shared meeting-payload sanitizer treated the snapshot’s markup field as plain text instead of post content; it is now sanitized as post content, so bold, italics, line breaks and paragraphs survive the import. Affects Amend Export, the Single Meeting Snapshot (JSON) import, and the demo/seed generator alike, since they share one sanitizer. Meetings imported before this fix need a re-import to recover their formatting — it was discarded at write time and cannot be restored retroactively.
- Fix: Editing a participant in the admin now shows up on the front end right away, on every meeting that participant appears in — previously an edit to a participant’s details could keep displaying the previously stored version on meeting pages until the meeting was imported again.
- Fix: A participant’s Formatted Display content whose lines were separated by a plain newline in the editor, rather than an explicit line-break tag, now renders those breaks on the front end — previously the lines ran together. Content already using paragraphs or explicit breaks is unaffected.
- Fix: The Witness Directory widget, and any other listing that gathers a meeting’s participants, now correctly includes nominees when filtering by meeting attributes such as congress or date range — previously a nominee could only be found by searching participant attributes directly, never by filtering meetings first.
- Fix: The Panels and Nominations widgets now honor a participant’s Display Mode choice — a panel witness or nominee explicitly set to “Individual Fields” shows their Title/Agency/City,State fields instead of an imported bio, even when that bio is still stored. A participant whose Display Mode has never been touched still shows the bio exactly as before. Note: importing a meeting snapshot that carries formatted content for a participant sets their Display Mode to “Formatted Display” and persists it — this will override a previously chosen “Individual Fields” selection for that participant on the next import that still delivers formatted content.
- New: The Select Member modal now lists live Congress.gov senators alongside the site’s own member posts, in one merged list scoped to the congress of the meeting being edited. Each row is marked either as already in the library or as available to add from Congress.gov, and picking a Congress.gov senator creates a fully populated member post and selects it into the row in one action. A senator who already exists locally is matched by bioguide ID and never duplicated. This requires a free Congress.gov API key entered in Meetings Settings; with no key entered, the picker behaves exactly as before.
- Fix: Loop Grid filter controls for date and taxonomy read and wrote different GET parameter names between the widget and the query that consumes them, so a Congress, Meeting Type, or other taxonomy selection made in the Loop Filters or Meetings Table widget could silently fail to apply or match the wrong set of meetings. Meeting date filters are also now correctly scoped to meeting-specific metadata instead of matching against the generic post date.
- Fix: Meeting Calendar events now render in the site’s configured timezone instead of each visitor’s own local timezone, so a meeting shows the same clock time to every visitor. An earlier named-timezone approach shipped earlier in this same release proved unreliable and has been replaced with a floating-time technique that no longer depends on the visitor’s browser timezone data; this update also fixes the Meeting post type not reliably appearing in the Loop Filters dropdown.
- Fix: An admin using the “Preview with Embargoed Files” link on a meeting could still be blocked from viewing embargoed files, because a second, unreachable security-token check on the override path could never be satisfied. Removing it restores the intended override.
- Fix: Nominee panel data is now stored per-panel using the same nested structure meeting panels already use, fixing a bug where saving a meeting with more than one nominee panel could collapse its entire nominations list to empty. A nominee panel now keeps its own identity across delete and reorder saves, so editing one panel’s members no longer shifts members into another panel. A repair tool is available under Tools > Congress Utilities (“Repair Flattened Nominee Panels”) for any meeting whose nominee data was already saved in the old, flattened shape, with a dry-run pass to preview the changes before a separate confirming pass writes them.
- New: Both the Panels and the Nominations widgets gained a Default Panel Name control that supplies a fallback header title for a panel with no name of its own — previously an unnamed panel rendered with no header at all. Blanking the control restores the previous behavior of hiding the header for unnamed panels.
- Fix: The Congress.gov roster picker introduced in this release has been hardened: the search box now filters the Congress.gov results as well as the site’s own member posts, including by first name; the Cached Roster control on the Setup tab now operates independently of saving settings instead of being silently dropped inside the settings form; a member’s cached Congress.gov match is now cleared whenever that member is edited or deleted so a stale match can never persist; picking a Congress.gov senator into a row no longer risks a duplicate or a stale “Add from Congress.gov” row if picked more than once; reconciling a Congress.gov senator with an existing member post now works on sites where members are only ever created through Proforma import; and opening the Setup tab no longer wipes a stored Congress.gov API key when that key is supplied by a wp-config.php constant.
1.4.7
- Fix: Congress taxonomy filtering in the Loop Filters widget and the Loop Grid/Meetings Table query handlers now compares against the actual registered taxonomy slug (e.g.
capigacr_congress) instead of the hardcoded literalcongress, and no longer hardcodes an exclusion list for meeting-only taxonomies/post types — both bugs silently broke Congress filtering depending on which modules were enabled or how the taxonomy slug was configured.
1.4.6
- Fix: Single Meeting Snapshot (JSON) import no longer creates a
meeting_filerecord for files attached to panel participants — the meeting-snapshot ingestion path had no equivalent of the live API’s separate “Write/Upload File” step, so a panel member’s referenced files (visible in the pasted JSON) never got their own WordPress file post created. A metadata-only file record is now created for each panel-member file reference during import, matching how every other file location (meeting files, transcripts, meeting members, nominee panels) already behaves. - Fix: Amend Export / snapshot import silently dropped the meeting Start Date (both the ACF field and the
meeting_startdatabase column) for meetings with a title longer than 255 characters — most commonly nomination hearings that list every nominee’s full name and position, but also long Executive Session titles. The plugin’s internalcapigacr_meetingmeta.titlecolumn was avarchar(255), and the title was written in the same database statement asmeeting_start; under strict SQL mode (the modern MySQL/MariaDB default), a too-long title caused that entire statement — including the start date — to fail, with no error surfaced anywhere in the import results. Thetitlecolumn is nowTEXT(matching the already-unboundedagendacolumn), removing the failure entirely. Existing sites are updated automatically via a database migration on the next admin page load. - Fix: Removed the Bootstrap
btn btn-sm btn-primary(and sibling variant) classes from meeting-files and meeting-links card action buttons — buttons now carry only the design-systemButtonclass. The now-obsolete “File Button Style” (meeting-files) and “Link Button Style” (meeting-links) Elementor controls, and all their wiring, were removed. - Fix: Taxonomy fields (Congress, Meeting Type, etc.) now display correctly on WordPress-source meeting edit screens — a slug format mismatch in
adjust_field_editability()caused all taxonomy fields to be hidden regardless of the enabled taxonomies setting. - Fix: Agenda items card and row layout — content now renders inside
.capigacr-widget-cardli elements. Therender_agenda_itemclosure was emitting its own<li>wrapper, which when nested inside the template’s<li class="capigacr-widget-card">caused browsers to auto-close the outer li, producing empty card wrappers followed by bare li elements with the actual content. - Feature: Agenda Items widget — consolidated “List Indentation” and “List Numbering Styles” Elementor controls into a single “List Style Per Level” repeater. Each row now configures both numbering style and indentation for that level, supporting unlimited nesting depths.
- Feature: Legislation widget — same “List Style Per Level” repeater added to match the Agenda Items widget. Removes the two static indent controls; indentation now applies to amendments at any depth via inline margin-left, and list-style-type is wired to the outer ol.
- Fix: Coast Guard Lists widget — “Preview” header field now renders HTML content (e.g.
<p>tags) as formatted HTML instead of escaping it to literal text, in both card and row layout styles. - Fix: Filter Auto-Refresh on the Loop Filters widget is now permanently disabled — the toggle control was removed and the availability-computation path (which fired uncached /filters/counts REST calls with unbounded WP_Query + per-taxonomy term lookups) can no longer be enabled. Resolves site-wide slowdowns caused by frontend filter changes.
- Feature: Button icon style controls (all widgets) and the Meeting Page Defaults Card/Row attachment icon sections gain a “Square Icon” toggle that forces the icon container to a square aspect ratio (width: 1em; box-sizing: content-box) matching its font-size. Opt-in — off by default, no change to existing pages.
- Fix: Per-widget button label visibility can now override the page-wide default in both directions. The on/off “Hide Button Label” toggle is replaced by a three-state “Button Label” control (Default / Show Label / Hide Label) in the shared button style helper and the Meeting Page Defaults Card/Row attachment sections — setting “Show Label” on an individual widget now re-displays its label even when labels are hidden page-wide.
- Fix: Corrected the “Button Label” visibility control (Default/Show/Hide) so Show and Hide actually take effect on the frontend — the prior fix used an Elementor pattern (condition-gated hidden helper controls) that never emitted CSS. Replaced with Elementor’s
selectors_dictionarymechanism directly on the driver control. - Fix: Further corrected the Button Label visibility control’s CSS delivery — the prior fix’s selector template was a bare
{{VALUE}}with no leading CSS property, which produced no output; reshaped to lead withposition:matching the plugin’s other working selectors_dictionary controls (e.g. Icon Alignment). - Feature: New public REST endpoint
GET /meetings-calendarreturns published meetings as a FullCalendar-shaped events feed (id/title/start/end/url), plus a new Meeting Calendar Elementor widget that renders a self-hosted FullCalendar month grid fed by that endpoint — no CDN dependency, clicking an event navigates to the meeting page. - Fix: Meeting Calendar widget failed to render — the widget’s init script was registered without
elementor-frontendas a script dependency, and relied solely on Elementor’sfrontend/element_readyhook, which is not reliably dispatched at a consistent point relative to widget script execution across Elementor versions/setups. The widget now initializes any.capigacr-meeting-calendarelement already in the DOM via a direct scan on page load, with the Elementor hook kept as a best-effort addition so the calendar also initializes correctly if added to the page later (editor live preview, popups, AJAX-loaded content).
1.4.5
- Fix: File embargo URL suppression — PHP now withholds file download URLs from HTML during embargo; JS fetches and injects the real URL via a new REST endpoint only after the embargo lifts, preventing URL leakage in page source.
- Feature: New REST endpoint
GET /meeting/{id}/file-url/{file_id}returns a file’s download URL after server-side embargo verification. - Fix:
filesEmbargoDateTimeis now sent as UTC ISO 8601 (withZsuffix) from the embargo-status API, eliminating browser-timezone misinterpretation when the visitor’s timezone differs from the WordPress site timezone. - Fix:
meeting_startembargo fallback now correctly treats the stored value as UTC rather than source timezone, fixing incorrect embargo lift times whenfilesEmbargoDateTimeis absent. - Fix: Embargo-checker.js now derives server time from the HTTP
Dateresponse header plus half-RTT latency, replacingcurrent_time/current_timestampbody fields that go stale on CDN-cached responses. - Fix:
Cache-Controlon the embargo-status endpoint is now conditional — usesapi_cache_intervalfrom Live Video settings when configured, otherwise sendsno-storeheaders (replaces hardcoded 5-minute cache). - Fix:
scheduleEmbargoRecheckno longer triggers an infinite polling loop when the embargo is already lifted — returns early instead of immediately rechecking. - Fix: Embargo reveal now clears the inline
style="display:none"set by PHP block templates in addition to removing the CSS class, so elements become visible after lift. - Fix: Embargo-checker now handles a null or absent
filesEmbargoDateTimegracefully — treats it as immediately lifted and reveals any elements hidden on load. - Feature: Embargo-status API URL includes a predictable
_tcache-bucket parameter aligned to the configured CDN interval, matching the live-meetings pattern. - Feature:
cacheIntervalandcacheBucketare injected intocapigacrEmbargoSettingswhen a CDN cache interval is configured, enabling JS to compute matching cache-bucket values client-side. - Feature: ACF taxonomy select field for File Type replaces the default WordPress tag meta box on meeting file edit screens with a proper select-style dropdown.
- Fix:
get_meeting_file_type_label()now resolves the label viawp_get_object_terms()when a post ID is provided, giving more reliable results than slug-based term lookup. - Fix: Files uploaded via REST API are now registered as stubs in
local_overrides.files[]so they appear in the hydrated snapshot on the front-end. - Fix: Proforma file type handler now checks
proforma-file-typeparameter before falling back totype. - Feature: Upcoming Hearings Query widget now includes a “No Upcoming” (count=0) option.
- Fix: Embargoed file anchors now render as
role="button" aria-disabled="true"…