creativestrategy24

Conference Manager is a WordPress plugin designed for academic societies and conference organizers. It provides end-to-end management of event registration, payments, and document generation.
Features:
<ul>
<li>Member management (import/export via CSV/Excel)</li>
<li>Event and session management</li>
<li>Registration forms with group (team) registration support</li>
<li>Bank transfer and Stripe credit card payment</li>
<li>Automatic invoice and receipt PDF generation</li>
<li>Participant list and MyPage (with Passkey/WebAuthn authentication)</li>
<li>AES-256-GCM encryption for personal data</li>
<li>Audit logging, rate limiting, and bot protection</li>
<li>Transactional email notifications (OTP, confirmations)</li>
<li>SNS share buttons (Twitter/X, Facebook, LINE)</li>
<li>Full Japanese / English localization</li>
</ul>
<h3>External Services</h3>
This plugin connects to the following external services.
<h4>Stripe Payments (optional)</h4>
When the site administrator configures Stripe API keys (Secret and Publishable) under Conference → Setup, and a participant chooses Stripe at checkout, the plugin:
<ul>
<li>Loads Stripe.js from <code>https://js.stripe.com</code> on the registration page.</li>
<li>Creates a PaymentIntent on Stripe’s servers via the Stripe PHP SDK.</li>
<li>Stripe Elements (an iframe hosted by Stripe) collects the card data directly; the card number never touches the WordPress server.</li>
<li>Optionally receives webhook callbacks from Stripe to confirm payment status.</li>
</ul>
What data is sent to Stripe:
<ul>
<li>Payment amount and currency.</li>
<li>Participant email address (for Stripe receipts).</li>
<li>Billing details if provided by the participant.</li>
<li>Registration ID and registration number as metadata.</li>
</ul>
When:
<ul>
<li>Only when a participant selects Stripe as the payment method and submits the registration form.</li>
<li>When Stripe sends a webhook back to the site (server-to-server callback).</li>
</ul>
Links:
<ul>
<li>Stripe Terms of Service: <a href="https://stripe.com/legal/ssa" rel="nofollow ugc">https://stripe.com/legal/ssa</a></li>
<li>Stripe Privacy Policy: <a href="https://stripe.com/privacy" rel="nofollow ugc">https://stripe.com/privacy</a></li>
</ul>
<h4>IPAex Font Download (PDF generation)</h4>
To render Japanese text in PDF documents (invoice, receipt), the plugin needs the open-source IPAex Gothic and IPAex Mincho fonts. From the admin Dashboard you can install them with one click; the plugin then downloads the font files (one-time, per font). No user data is transmitted — it is a file download only. If the server cannot reach the download host, you can instead upload the <code>.ttf</code> files directly from the Dashboard (no external connection required).
<ul>
<li>Download host (mirror maintained by the plugin author): <a href="https://cs24.biz/conference/fonts/" rel="nofollow ugc">https://cs24.biz/conference/fonts/</a></li>
<li>Data sent: none (file download only)</li>
<li>The download URL can be overridden via the <code>conf_manager_font_source_url</code> filter.</li>
<li>Original font source / IPAex Font License (IPA, Information-technology Promotion Agency): <a href="https://moji.or.jp/ipafont/license/" rel="nofollow ugc">https://moji.or.jp/ipafont/license/</a></li>
</ul>
<h3>Development / Building from source</h3>
The admin and public interfaces are built with React (JSX). The human-readable 
source for the compiled, minified bundles <code>build/admin-app.js</code> and 
 build/public-app.js is shipped inside this plugin under the <code>src/</code> directory:
<ul>
<li><code>src/admin/</code> — source for <code>build/admin-app.js</code> (admin dashboard app)</li>
<li><code>src/public/</code> — source for <code>build/public-app.js</code> (public registration / MyPage app)</li>
</ul>
Build toolchain: the project uses <a href="https://www.npmjs.com/package/@wordpress/scripts" rel="nofollow ugc">@wordpress/scripts</a> 
(a wrapper around webpack and Babel). The webpack configuration is included as 
 webpack.config.js, and all dependencies and build scripts are declared in 
 package.json (with <code>package-lock.json</code> for reproducible installs).
To rebuild the compiled assets from source:
<ol>
<li>Install Node.js 18+ and npm.</li>
<li>From the plugin directory, run <code>npm install</code>.</li>
<li>Run <code>npm run build</code>. This regenerates <code>build/admin-app.js</code> and 
 build/public-app.js (and their <code>*.asset.php</code> dependency manifests). 
Use <code>npm start</code> for an unminified development watch build.</li>
</ol>
Third-party libraries bundled into the compiled JavaScript (all open source, 
installed from the public npm registry and declared in <code>package.json</code>):
<ul>
<li><code>@stripe/react-stripe-js</code> and <code>@stripe/stripe-js</code> — Stripe Elements payment UI (MIT)</li>
<li><code>html5-qrcode</code> — QR code scanner used for participant check-in (Apache-2.0)</li>
</ul>
WordPress-provided packages (<code>wp-element</code>, <code>wp-components</code>, <code>wp-api-fetch</code>, 
 wp-i18n, <code>react</code>, <code>react-jsx-runtime</code>) are declared as externals and are NOT 
bundled — they are loaded from WordPress core at runtime.

ConferenceManager

Academic conference management plugin — registration, payment, and document automation for scholarly events.

John Hawkins

toddhuish

Josh Harrison

Shayne Sanderson

This plugin creates a custom post type for event speakers. Includes speakers page and single-speakers page templates.
If you are upgrading from an earlier version, you will need to manually move the template_speakers.php and single-speakers.php files from the <code>/wp-content/plugins/cpt-speakers/</code> folder in to the folder for your active theme. If the file already exists in your theme folder, overwrite it with the new one.

CPT – Speakers

Easily create your conference speaker's page using CPT - Speakers.

ConferenceManager vs CPT – Speakers