Skip to content

OpenNews/emergencymode.news

BranchesTags

Repository files navigation

emergencymode.news

Custom WordPress plugins, Python Notebooks and miscellaneous code version control for the Emergency Mode for News (EMFN) Newspack website.

badge status
Tests on main & staging CI
Release versioning on main Release
CodeQL CodeQL
Dependabot Dependabot Updates

Overview

This repository contains:

  • the emfn-action-pack-plugin — the active front-end integration for the Action Pack assessment flow
  • Python notebooks that generate and validate FEMA National Risk Index county-level CSVs consumed by the Action Pack plugin

Repository Structure

emergencymode.news/
├── .devcontainer/                          # Devcontainer config & setup script for local work
├── .github/
│   ├── dependabot.yml                      # Automated dependency updates (npm, GitHub Actions)
│   └── workflows/
│       └── release.yml                     # Automated release workflow on push to main
├── notebooks/                              # Python notebooks for risk-data generation and research
│   ├── US_disaster_risk_analysis.ipynb     # Action Pack #risks work
│   ├── CA-MX_disaster_risk_analysis.ipynb  # Draft of possible expansion 
│   ├── shared_setup.py                     # Shared setup utilities for notebooks
│   ├── README.md                           # Notebook documentation
│   └── cache/                              # Cached FEMA source downloads
│       └── NRI_Table_Counties.csv
├── plugins/
│   ├── emfn-action-pack-plugin/            # Gravity Forms augmentation
│   │   ├── emfn-action-pack-plugin.php     # Main plugin file
│   │   ├── readme.txt                      # WordPress plugin readme
│   │   ├── assets/
│   │   │   ├── css/
│   │   │   │   └── emfn-action-pack-plugin.css
│   │   │   ├── data/                       # CSVs used in geolocation & hash encoding/decoding
│   │   │   │   ├── _tallCategories.csv     # Category mapping registry
│   │   │   │   └── {ST}.csv                # State-specific NRI risk data (51 files)
│   │   │   ├── html-templates/
│   │   │   │   └── gravityForms-Your_Risks-body.html
│   │   │   └── js/
│   │   │       └── emfn-action-pack-plugin.js
│   │   ├── includes/
│   │   │   └── class-emfn-action-pack-plugin.php
│   │   └── languages/
│   └── shared/
│       └── emfn-types.d.ts                 # Shared Types for JavaScript
├── scripts/                                # Release and notebook hygiene utilities
│   ├── sync-release-version.sh             # Updates Release version across many files
│   ├── build-release-assets.sh             # Builds plugin ZIPs
│   ├── strip-notebook-outputs.sh           # Cleans notebook execution state
│   └── check-notebooks-clean.sh            # Checks notebooks for cruft
├── tests/                                  # Testing infrastructure
│   ├── js/                                 # JavaScript tests (Jest)
│   │   ├── setup.js                        # Test environment setup
│   │   ├── action-pack/                    # Action Pack plugin tests
│   │   └── lib/                            # Shared test utilities
│   ├── php/                                # PHP tests (PHPUnit)
│   │   ├── bootstrap.php                   # Test bootstrap with WordPress stubs
│   │   └── action-pack/                    # Action Pack plugin tests
│   ├── scripts/                            # Shell script tests
│   │   ├── test-helpers.sh                 # Test framework helpers
│   │   ├── test-build-assets.sh            # Build script tests
│   │   └── test-version-bump.sh            # Version logic tests
│   ├── fixtures/                           # Test data
│   │   ├── payload-test-cases.json         # Action Pack encoding tests
│   │   └── location-test-data.json         # Geolocation test data
│   ├── TESTING_PLAN.md                     # Testing strategy
│   └── README.md                           # Quick start for running tests
├── tmp/                                    # Temporary/scratch files (not deployed)
│   ├── _tallCategories.csv
│   └── ga.txt
├── tools/                                  # Development utilities (not deployed)
│   ├── README.md
│   ├── scripts/
│   │   ├── README.md
│   │   └── SheetsWPAppScript.js
│   ├── styles/
│   │   └── siteCustomRules.css
│   └── templates/
│       └── liteSitesFooter.html
├── .gitignore
├── AGENT.md                                # Agent guide: lessons learned, gotchas, best practices
├── composer.json                           # PHP dependencies (PHPUnit, WordPress stubs)
├── eslint.config.js                        # ESLint configuration
├── jest.config.cjs                         # Jest test configuration
├── jsconfig.json                           # Editor & Type config 
├── LICENSE
├── package.json                            # npm dependencies & scripts
├── phpunit.xml                             # PHPUnit configuration
├── pyproject.toml                          # Notebook dependencies
└── README.md                               # This file

emfn-action-pack-plugin

This is the core custom plugin in the EMFN Newspack site.
Responsibilities:

  • Setup
    • Enqueues the Action Pack CSS and JS bundles
    • Exposes window.emfnData.dataUrl and an ap2.-prefix in the final quiz URL to help both client and server see canonical data
  • Geolocation
  • Submission client-side Hash Encoding
  • PHP server-side Hash Decoding
    • Decodes the same actionPack payload/hash on the server and maps them to Newspack Query Loop query params including category__in, filtering and sort-order

Page Detection

These event bindings and /data/ file fetches can be memory-intensive and we want to simplify that for EMFN site visitors experiencing an emergency or amid recovery from a disaster.

Assets load on any frontend page with either of these querystring parameters:

  • ?mode=<value> → quiz/form pages
  • ?actionPack=<hash> → results pages

Debugging & Troubleshooting

Debug Mode (emfnDebug=true)

Add &emfnDebug=true to Action Pack URLs to request debug logging:

.../start/action/?mode=mode-during&emfnDebug=true
.../start/action-pack/?actionPack=ap2.xyz123&emfnDebug=true

Server-side PHP debug output only appears when emfnDebug=true and the current user is a WordPress administrator or editor.

What Gets Logged:

  • Client-side JS (browser console): Form values, category mappings, encoded payloads
  • Server-side PHP (footer <script>): Payload presence signal, decoded term IDs, and CSS class-based block filters

Where to Look:

  • Open browser DevTools Console (F12)
  • Enable "Persist logs" to preserve output across page navigation
  • PHP debug entries appear as console.debug() calls in footer scripts
  • Look for EMFN: prefixes on PHP debug labels

When to Use:

  • Form not redirecting with proper actionPack parameter
  • Results page showing wrong/no content
  • Category filtering not working
  • Troubleshooting payload encoding/decoding mismatches
  • Verifying CSV category order synchronization between client and server

Sample Debug Output

<LOG_TIMESTAMP> .hashable form values: (6) ['mode-during', 'disasterType-flooding', 'size-25', 'activeReporting-true', 'pubSituation-0', 'contactPlan-true']
<LOG_TIMESTAMP> Encoded Action Pack categories: (32) ['Flooding (1)', 'Power & connectivity (2)', 'Solo operator (1)', 'Small newsroom (1)', 'Co-located team (1)', 'Rural (3)', ...]

Navigated to https://<domain>/start/action-pack/?actionPack=ap2.<hash>&emfnDebug=true

<LOG_TIMESTAMP> EMFN: Block categories applied {
  className: "emfn-action-pack emfn-content-cards is-style-default",
  termIds: (23) [3, 153, 121, 122, 72, 151, ...],
}

Action Pack Flow

The Action Pack operates in two phases, with payload encoding/decoding coordinated between emfn-action-pack-plugin.js and class-emfn-action-pack-plugin.php.

Phase 1: Assessment (.emfn-forms)

  • Multi-"page" Gravity Form at /action/ collects location, disaster type, newsroom characteristics
  • JS plugin binds geolocation
  • On submit, collects .hashable-marked form entries
  • Fetches _tallCategories.csv to map answers → WP Category IDs → compact ap2. bitmask payload
  • Writes encoded payload to .hashMarker input (to save to Form entry) and form redirects with ?actionPack=ap2.<hash>
  • Location data persists in sessionStorage across form pages, as a backup mechanism

Phase 2: Action Pack Customization

  • User lands on results page with ?actionPack=ap2.<hash> parameter
  • PHP decodes payload using _tallCategories.csv category order (synchronized with client JS)
  • Resolves Category names → WordPress term IDs
  • Filters Newspack Content Loop blocks with .emfn-action-pack class to matched categories
  • URL is shareable; returns user a similarly ranked personalized Action Pack configuration... at least until we change any Categories in WP, then they all break
    • Not much we can do about that except re-compute _tallCategories with the new Category-tagging strategy for the content store
  • Debug mode (&emfnDebug=true) logs decode details when the user is logged in to WordPress

Content Recommendation Algorithm

The Action Pack delivers personalized content recommendations by converting quiz responses into a smart, multi-factor relevance score. This section explains how the system ensures quality and diversity even with a modest content library.

How Quiz Answers Become Recommendations

When you complete the Action Pack assessment, your answers generate a ranked list of content categories that match your newsroom's needs. The system then uses a three-tier scoring algorithm to surface the most relevant articles:

1. Editorial Quality Tiers (Primary Sort)

All Action Pack content is Tagged with quality tiers (resources-tier-1, resources-tier-2, resources-tier-3):

  • Tier 1: Flagship resources, essential guides, thoroughly vetted practices
  • Tier 2: Solid supporting content, case studies, practical templates
  • Tier 3: Supplementary material, experimental approaches, niche topics

Tier tags act as quality bands — all tier-1 content ranks above tier-2, regardless of other factors. This ensures your top results always reflect editorial priorities.

2. Category Relevance Weights (Secondary Sort)

Your quiz responses create a weighted category list. Categories that match more of your answers (higher "Total Rank" in the scoring table) receive higher weights. For example, if your quiz emphasizes staff safety and field reporting challenges, those categories get prioritized.

Within each quality tier, the algorithm calculates a relevance score based on:

  • Category weight: How strongly your quiz responses align with that category
  • Multi-category bonus: Articles matching multiple relevant categories score higher
  • Scarcity multiplier: Rare, specific content gets a boost (explained below)

3. Scarcity Diversity Mechanism

Here's where the algorithm prevents your highest-weighted category from dominating results: the scarcity multiplier gives extra credit to high-quality content in categories with fewer total articles.

Why this matters: Imagine your quiz strongly matches "Staff safety" (which might have 8 articles) and moderately matches "Field reporting" (which has only 3 articles). Without scarcity balancing, you'd see mostly staff safety content. The multiplier boosts the field reporting articles so they appear alongside staff safety pieces, giving you topical diversity instead of redundancy.

For A LOT more on content strategy growth and query optimization, see /data/_tallCategoriesREADME

Risk data flow

For the U.S., we match countyFIPS to NRI risk scores, where the score is at least x, the riskThreshold constant/variable in plugins/emfn-action-pack-plugin/assets/js/emfn-action-pack-plugin.js.

The plugin currently maps ~18 FEMA NRI hazard families based on the RiskRenderer.hazardLabels property defined in plugins/emfn-action-pack-plugin/assets/js/emfn-action-pack-plugin.js.

Example API response for NRI

county_fips,state,county,AVLN_risk_score,CFLD_risk_score,CWAV_risk_score,DRGT_risk_score,ERQK_risk_score,HAIL_risk_score,HWAV_risk_score,HRCN_risk_score,ISTM_risk_score,LNDS_risk_score,LTNG_risk_score,IFLD_risk_score,SWND_risk_score,TRND_risk_score,TSUN_risk_score,VLCN_risk_score,WFIR_risk_score,WNTW_risk_score
01001,Alabama,Autauga,,,28.18066157760814,45.64249363867685,67.84351145038168,44.30661577608143,85.90237636480411,72.090112640801,42.98567144285238,73.50508905852418,81.67938931297712,65.52162849872774,51.68575063613231,74.10941475826972,,,45.73791348600509,9.038828771483132

Supporting files

  • plugins/emfn-action-pack-plugin/assets/data/{st}.csv contains per-state county risk data generated by the notebooks.
  • plugins/emfn-action-pack-plugin/assets/data/_tallCategories.csv, an export from Google Sheets of every uniquely meaningful Category per quiz response
  • plugins/emfn-action-pack-plugin/assets/html-templates/ stores HTML snippets which exist within the Gravity Form "HTML field", which provides the DOM for our #risks info

Development & Dependencies

Python (Notebooks)

Python dependencies are managed with uv and defined in pyproject.toml using compatible release constraints (~=), allowing patch and minor version updates while keeping major versions stable.

Setup:

# From repo root
uv sync

Within notebooks:

  • Cell 2 runs uv sync to keep the environment in sync with uv.lock
  • Cell 3 (using shared_setup.py) verifies the environment is healthy; output will recommend next steps if issues are detected
  • Each notebook's output will guide you through any upgrades needed

See notebooks/README.md for details on the shared setup utilities.

JavaScript / npm

Plugin dependencies and dev tools are managed via npm with Dependabot automation for regular updates.

npm install

GitHub Actions & Dependabot

Dependency automation is configured in .github/dependabot.yml:

Ecosystem Frequency Notes
npm Weekly Plugin production dependencies + dev tools
github-actions Weekly Workflow & CI/CD tool updates (if available)
pip Disabled Python deps manually maintained (notebooks are rarely used)

Data Analysis Notebooks

The notebooks/ directory contains Python workflows that generate and validate FEMA National Risk Index county data consumed by the Action Pack plugin.

Current notebooks:

  • US_disaster_risk_analysis.ipynb — Downloads FEMA NRI data and generates per-state CSVs for all 50 US states plus DC
  • CA-MX_disaster_risk_analysis.ipynb — Research notebook exploring Canada and Mexico data; does not currently generate runtime output

Setup: Each notebook runs uv sync on startup to ensure dependencies are in sync, then verifies the environment is healthy via shared_setup.py.

Output location:

  • plugins/emfn-action-pack-plugin/assets/data/ (51 US state + DC CSVs)
  • notebooks/cache/ (cached FEMA source downloads)

Managing dependencies: See the Dependency updates section above, or refer to notebooks/README.md for detailed dependency management instructions.

The notebooks are managed with uv and are not deployed to WordPress—they support data generation and validation only.

Shared JS Types And Tooling

The plugin JavaScript uses JSDoc typing backed by plugins/shared/emfn-types.d.ts.

window.emfnData now localizes only environment-specific runtime values needed by the browser, currently dataUrl and the ap2. payload prefix.

jsconfig.json scopes editor support to plugin JS and shared .d.ts files so the repo gets lightweight type assistance without a full TypeScript build.

Node-side repo tooling:

Formatting & Linting:

  • npm run format — Prettier auto-fix for markdown, JSON, HTML, CSS, JS
  • npm run format:check — Verify formatting without changes
  • npm run eslint — Lint plugin JavaScript files
  • npm run eslint:fix — Auto-fix ESLint issues
  • npm run shellcheck — Lint all shell scripts
  • npm run lint — Run all checks (format, eslint, shellcheck, notebooks)

Testing:

  • npm test — Run JavaScript and shell script tests
  • npm run test:all — Run all tests (JavaScript, PHP, shell scripts)
  • npm run test:js — Jest tests only
  • npm run test:js:watch — Jest in watch mode
  • npm run test:js:coverage — Jest with coverage report
  • npm run test:php — PHPUnit tests only
  • npm run test:php:coverage — PHPUnit with HTML coverage report
  • npm run test:scripts — Shell script tests only

Notebooks:

  • npm run notebooks:strip — Strip notebook outputs
  • npm run notebooks:check-clean — Verify notebooks are clean

Recommended notebook workflow

Use the VS Code devcontainer for notebook work. It provides the expected Debian/Python environment and runs the repo setup script automatically.

Typical setup:

uv sync
uv run jupyter lab

Python dependencies currently live in pyproject.toml and include jupyterlab, pandas, requests, numpy, ipykernel, and tqdm.

Prevent Notebook Output In Git

This repo uses local pre-commit hooks to keep notebooks clean in commits.

Install hooks with:

uv tool install pre-commit
pre-commit install

The configured hooks:

  • strip notebook outputs and execution metadata from changed notebooks
  • fail the commit if executed notebook state remains

Relevant scripts live in scripts/strip-notebook-outputs.sh and scripts/check-notebooks-clean.sh.

Automated Maintenance

Dependabot Configuration

This repo uses Dependabot (.github/dependabot.yml) for automated dependency management:

  • npm dependencies: Weekly checks for updates with grouped minor/patch PRs (if available)
  • Python/pip dependencies: Not configured in Dependabot; notebook deps are maintained manually
  • GitHub Actions: Weekly checks for workflow dependency updates (if available)

Dependabot PRs can be auto-merged after CI passes, enabling frequent maintenance with minimal manual intervention.

Continuous Integration (CI) Checks

The .github/workflows/ci.yml workflow runs on all pull requests and pushes to main/staging:

  1. Lint checks: npm run lint (Prettier, ESLint, shellcheck, notebook cleanliness)
  2. JavaScript tests: npm run test:js (Jest with 54 tests)
  3. PHP tests: npm run test:php (PHPUnit with 22 tests)
  4. Shell script tests: npm run test:scripts (34 shell tests)

Test results appear in GitHub Checks on PRs, providing immediate feedback before merge. All checks must pass before merging to main.

Automated Release Workflow

On every push to main, .github/workflows/release.yml executes:

  1. Lint checks: Runs npm run lint (Prettier, ESLint, shellcheck, notebook cleanliness)
  2. Test execution: Runs npm run test:all (JavaScript, PHP, shell script tests)
  3. Version increment: Computes next patch version tag (e.g., v1.0.0 → v1.0.1)
  4. Version sync: Updates all version references via scripts/sync-release-version.sh:
    • package.json version
    • pyproject.toml version
    • Plugin PHP headers (Version: field)
    • Plugin PHP constants (EMFN_*_PLUGIN_VERSION)
    • Plugin readme.txt stable tags
    • Plugin readme.txt changelog entries
  5. Commit sync: Pushes version updates back to main as a bot commit
  6. Build assets: Creates plugin ZIP files via scripts/build-release-assets.sh
  7. GitHub Release: Publishes release with auto-generated notes and ZIP attachments
  8. Tag updates: Maintains floating latest and vX tags

Infinite loop prevention: The workflow skips when the latest commit is already a version sync, preventing recursive triggers.

Developer workflow benefits:

  • Merge PR → automatic version bump and release
  • No manual version file editing
  • Tests run automatically before release
  • Consistent versioning across all files
  • Release notes auto-generated from commit history
  • Safe for Dependabot auto-merge after CI passes

Deployment

Deployment to Newspack staging and production is handled manually by site owners. We SHOULD NOT ask Newspack Support TAMs about this custom plugin.

For plugin deployment:

  1. Merge changes to main (automated release workflow creates GitHub Release)
  2. Download plugin ZIP from the newly generated (and successfully vetted and created) GitHub Release
  3. Install WordPress Admin and activate, overriding the prior plugin if necessary

The devcontainer, notebooks, scripts, tests, and tmp/ files are not deployed to WordPress.

Testing

This repository includes comprehensive test coverage across JavaScript, PHP, and shell scripts.

Quick Start

# Run all tests
npm run test:all

# Run specific test suites
npm run test:js          # JavaScript tests (Jest)
npm run test:php         # PHP tests (PHPUnit)
npm run test:scripts     # Shell script tests

# Run with coverage
npm run test:js:coverage      # Coverage in terminal
npm run test:php:coverage     # HTML report in coverage/php/

Test Infrastructure

JavaScript (Jest)

  • Plugin JavaScript unit tests
  • JSDom environment for browser APIs
  • Coverage tracking enabled
  • Test files: tests/js/**/*.test.js

PHP (PHPUnit)

  • WordPress plugin class tests
  • WordPress function stubs in tests/php/bootstrap.php
  • Strict mode enabled (fail on warnings)
  • Test files: tests/php/**/*Test.php

Shell Scripts

  • Custom bash test framework (tests/scripts/test-helpers.sh)
  • Tests for build, version sync, and notebook scripts
  • Automatic test discovery (test-*.sh files)

Test Fixtures

  • tests/fixtures/payload-test-cases.json — Action Pack encoding/decoding test cases
  • tests/fixtures/location-test-data.json — Geolocation resolution test data
  • tests/fixtures/test-categories.csv — Category mapping test data

Pre-commit Hooks

Pre-commit hooks automatically run tests and linters:

# Install hooks (one-time setup)
pre-commit install

# Hooks will run on git commit:
# - Prettier formatting
# - Shellcheck linting
# - ESLint on changed .js files
# - Notebook output stripping
# - Notebook cleanliness check

Development Workflow

Before committing changes:

# Run all checks (same as pre-commit hooks)
npm run lint
npm run shellcheck
npm run test:all

# Or run pre-commit manually
pre-commit run --all-files

See AGENT.md for lessons learned, common gotchas, and troubleshooting tips when working with the test infrastructure.

Development Notes

Coding Standards

  • Follow WordPress coding standards: https://developer.wordpress.org/coding-standards/
  • Prefix custom functions, classes, and hooks with emfn_ to reduce conflicts
  • Use phpDoc comments for WordPress plugin headers and function documentation
  • JavaScript uses JSDoc typing backed by plugins/shared/emfn-types.d.ts

Version Management

  • Never manually edit version numbers — the automated release workflow handles this
  • All version references are synced automatically on merge to main via scripts/sync-release-version.sh
  • Plugin source files use both WordPress Version: headers and PHP constants
  • Both version indicators must match and are updated together

Version sync safeguards:

  • Validates semver format (X.Y.Z)
  • Rejects unrealistic version components (> 10.99.99)
  • Checks against latest GitHub release (blocks major version jumps > 1)
  • Prevents version downgrades
  • Can bypass checks with --force flag (for fixing version history issues only)
  • Automatically skipped in CI workflows

Manual version sync (for emergency fixes only):

# Normal usage
./scripts/sync-release-version.sh 1.2.3

# Force mode (bypasses GitHub release check)
./scripts/sync-release-version.sh --force 1.2.3

Development Environment

  • Use the VS Code (or sibling editor) devcontainer for consistent Python/Node.js/PHP environment
  • WordPress core and third-party plugin versions are managed on the hosted Newspack environment
  • This repo stores EMFN custom code and supporting data-generation assets
  • Pre-commit hooks enforce code quality, linting, and test cleanliness (install with pre-commit install)

Devcontainer includes:

  • Python 3.13 (notebooks, pre-commit)
  • Node.js LTS (npm, jest, eslint, prettier)
  • PHP 8.3 with Composer (PHPUnit, WordPress stubs)
  • Shellcheck (script linting)
  • GitHub CLI (release automation)

Key configuration files:

  • .devcontainer/devcontainer.json — Container features and VS Code extensions
  • .devcontainer/setup.sh — Post-create setup script
  • .pre-commit-config.yaml — Pre-commit hook configuration
  • AGENT.md — Lessons learned, gotchas, and troubleshooting guide

Troubleshooting

Common Issues and Solutions

Plugin not loading

  • Symptoms: No custom styles, JS not executing, form looks like default Gravity Forms with the royal blue progress bar, etc.
  • Causes: Page detection failing
  • Solutions:
    • Confirm WordPress not in safe mode or plugin not disabled
    • Verify page has .emfn-forms class on the form element or .emfn-action-pack on results blocks
    • Make sure our custom Gravity Forms block is in page content
    • Confirm page slug matches action (for /start/action/ pages)
    • Clear WordPress object cache if using caching plugins
    • Check is_action_pack_page_request() returns true via debug mode

No risk data showing

  • Symptoms: Location autocomplete works but no hazards display in form
  • Causes: Geolocation API failures, CSV access issues
  • Solutions:
    • Confirm WordPress not in safe mode or plugin not disabled
    • Verify Google Places API key is valid and has Places API (New) enabled
    • Check browser console for FCC Area API errors (CORS, 404, invalid lat/lon errors -- all should be logged to dev-tools Console)
    • Confirm state CSV files exist in assets/data/{ST}.csv (uppercase state abbreviation)
    • Verify countyFIPS resolved correctly from FCC API response and shows up in recent submissions

Payload not decoding

  • Symptoms: Results page shows no filtered content, empty category list in debug output
  • Causes: CSV category order mismatch, invalid base36 encoding
  • Solutions:
    • Confirm WordPress not in safe mode or plugin not disabled
    • Enable debug mode (&emfnDebug=true) and ensure PHP debug gating conditions are met
    • Verify _tallCategories.csv is identical on client and server
    • Check payload format starts with ap2. prefix
    • Confirm category order hasn't changed between encoding and decoding
    • Manually test base36 decoding with browser console: parseInt('7', 36) should return decimal value

Categories not filtering content

  • Symptoms: Results page shows all posts or no posts instead of filtered content
  • Causes: Category ID resolution failed, block class missing
  • Solutions:
    • Confirm WordPress not in safe mode or plugin not disabled
    • Verify Newspack Content Loop block is present in page and has .emfn-action-pack class
    • Check debug output for resolved category IDs (should be array of integers)
    • Confirm WordPress categories exist matching decoded category names (exact match required)
    • Verify posts are assigned to the resolved categories
    • Inspect filter_action_pack_newspack_block_data() execution in debug logs

References

About

Custom Newspack & WordPress plugins for Emergency Mode for News, a collaboration between OpenNews, Newspack and NC Local, with funding from Press Forward.

emergencymode.news

Topics

wordpress-plugin news journalism emergency disaster-preparedness newspack newsrooms

Resources

Readme

License

MIT license
Activity
Custom properties

Stars

2 stars

Watchers

2 watching

Forks

0 forks
Report repository

Releases 13

v0.3.1 Latest
May 26, 2026
+ 12 releases

Contributors

Languages