Skip to content

UPPCC.org

uppcc.org is part of the website portfolio maintained and supported by Online Services.

Repository

Item Value
GitHub repository NASPO-ValuePoint/uppcc
Canonical local path ~/Sites/naspo/uppcc.org

Current Verification Status

The canonical local clone at ~/Sites/naspo/uppcc.org is initialized as a Git repository with remote git@github.com:NASPO-ValuePoint/uppcc.git, but it currently has no checked-out project files and no commits on local main.

The local status reported:

No commits yet on main...origin/main [gone]

Do not infer hosting, branch conventions, deployment behavior, WordPress/server layout, plugin management, or mail configuration from other NASPO sites. Verify the active remote branches, current production code location, and existing deployment process before documenting or changing UPPCC operations.

Production Hosting

Production status last verified August 12, 2026:

Item Value
Public site https://uppcc.org
AWS Lightsail instance uppcc-new
Public IP 98.81.53.72
Platform Bitnami WordPress
WordPress root /opt/bitnami/wordpress
home https://uppcc.org
siteurl https://uppcc.org
WordPress version observed 7.0.4

Use WP-CLI as root with the explicit WordPress path:

sudo wp <command> --path=/opt/bitnami/wordpress --allow-root

Running WP-CLI as the normal Bitnami daemon user returned "Please run this script as a superuser."

WordPress Stack

Production plugins and themes observed August 12, 2026 include:

  • Hello Elementor
  • hello-elementor-child
  • Elementor
  • Elementor Pro
  • ACF Pro
  • Gravity Forms
  • The Events Calendar
  • Event Tickets
  • TablePress
  • WP Remote
  • WP Mail SMTP

No mu-plugins directory was present when initially inspected.

Transactional Mail

NASPO Secure Mail is the active production mail path after the August 12, 2026 migration. WP Mail SMTP no longer serves as the active transport. Confirm plugin state before documenting WP Mail SMTP as removed.

Production Secure Mail configuration:

Setting Value
Gateway identity uppcc-prod
Gateway endpoint https://naspo-mail-gateway.naspo.workers.dev/v1/mail
Protected config file /opt/naspo/secure-mail/uppcc-prod.php
Delivery mode send
Allowed From webmaster@naspo.org, webmaster@uppcc.org
Default From UPPCC, webmaster@uppcc.org
Max recipients 50
Max payload 10 MiB
Rate limit 60 per minute, 600 per hour
SendGrid sandbox false

The protected config was confirmed readable from WordPress. Its secret was present with the expected length, but the secret value must not be documented.

Adding webmaster@uppcc.org was a gateway policy update. It did not require rotating the existing site HMAC secret.

Mail Validation

Production mail validation completed August 12, 2026:

  • A controlled wp_mail() test succeeded.
  • Worker tail showed mail_sent for uppcc-prod.
  • The controlled production test was received.
  • The live UPPCC contact form was successfully tested after sender policy and form configuration were corrected.
  • A live WordPress account-reset email was received.

Gravity Forms details verified during the migration:

  • The Contact Us Page Form admin notification sends to info@uppcc.org.
  • The CE Approval Requests form was inspected and updated to route appropriately, including info@uppcc.org as decided during the operator workflow.

Known Issues and Follow-Up

  • WP-CLI repeatedly emits AI Engine / MWAI constant redefinition warnings. Do not conflate these with Secure Mail unless mail behavior is directly affected.
  • An unrelated Action Scheduler issue was observed for a missing table similar to zie_actionscheduler_logs.
  • Confirm whether WP Mail SMTP remains installed as a rollback path before documenting it as removed.
  • Confirm active repository state, production code location, branch/environment mapping, deployment trigger, plugin/package management, rollback contact, and ownership notes.

Documentation to Capture

Add validated details about deployment, Cloudflare, integrations, analytics, accessibility, SEO, runbooks, and known issues as they are discovered.

Unknown/TODO: confirm active repository state, production code location, branch/environment mapping, deployment trigger/process, plugin/package management, rollback process, and ownership/contact notes.