Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Generated wiki posts can disappear after primary-mode reload

Open
  • Is something wrong?
#99 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
42/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
markdown, php
Domain
backend, database

Research direction

Start by reproducing the reported WP-CLI count and readiness checks, then inspect wp-content/markdown/wiki/wordpress-com/ alongside the primary-mode reload behavior. Trace how normal WordPress API writes for generated wiki posts are persisted and reloaded. Done means generated pages remain available after deploy/reload and the wordpress-com readiness report still includes them.

Written by the indexing model from the issue text.

Description

Summary

On intelligence-chubes4, Data Machine/Intelligence generated hundreds of wiki posts under wordpress-com during live ingestion, but after an Intelligence deploy/reload the WordPress.com corpus collapsed back to the markdown-backed seed tree.

Observed

Before deploy/reload:

  • wp post list --post_type=wiki --post_status=publish --format=count reported 486.
  • wp intelligence wiki eval readiness --root=wordpress-com --sample=100 was green.
  • Newly generated WordPress.com pages included high-ID posts like:
    • Dotcom Updates — 2022-12-06 (6971)
    • Avalancha Team Updates - June 6th (6975)
    • The Ankler launch (6974)
    • Gutenberg rollout dated pages (6755, 6758, 6763)

After deploying Intelligence and re-running WP-CLI:

  • wp post list --post_type=wiki --post_status=publish --format=count returned 111.
  • wp intelligence wiki status wordpress-com --format=json reported only 12 pages under wordpress-com and readiness false.
  • wp-content/markdown/wiki/wordpress-com/ contains only the seed tree, not the generated pages.
  • Searching wp-content/markdown/wiki found no generated files for gutenberg-rollout, dotcom-updates, or ankler.

Why this matters

intelligence-chubes4 runs Markdown Database Integration in primary mode. If generated wiki posts are not mirrored durably to markdown (or are otherwise lost on markdown-index reload), Data Machine/Intelligence ingestion can appear successful in SQLite but disappear after a deploy/reload.

Expected

Generated wiki posts written through normal WordPress APIs should persist durably across primary-mode reloads, either by writing markdown files or by having an explicit supported path for generated/transient content.

Notes

The new Intelligence operator status report in Automattic/intelligence#482 surfaced the issue by reporting only the durable 12-page wordpress-com tree after deploy. Debug log entries show HTML-to-block conversion warnings for generated pages around the time they were created, but the posts were visible/readable before reload.

Dominant language
PHP
Stars
7
Forks
1
Avg merge
26m
Merged PRs (30d)
26

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Automattic/markdown-database-integration

All issues in Automattic/markdown-database-integration

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.