2016/01/08/the-columns_home_blooming-grove
Archived page. Reproduced unchanged from the earlier site. Details and contact information are as they stood then.
⚠ INCOMPLETE CAPTURE — RETRY REQUIRED. Marker not removed: not earned.
The body of this article has still not been obtained verbatim. Nothing below is a substitute for it.
Metadata — T1, verbatim from the WordPress oEmbed endpoint
Route: /wp-json/oembed/1.0/embed?url=<post url>, read 2026-09-06T21:55:37Z, raw JSON returned in full.
- title:
Historic Home Hits the Market in Blooming Grove - author_name:
RLPhipps - author_url:
https://bloominggrovetx.com/author/rlphipps/ - provider_name:
Blooming Grove Texas' - thumbnail_url:
/wp-content/uploads/2016/01/1-IMG_5517-1024x683.jpg(600×400 as served) - type: rich · width: 600 · height: 338
- Publication date 2016-01-08 and categories Local Business / Local News carry over from the first pass (rendered-page read) and are T3 until re-confirmed at source.
Body — NOT CAPTURED
Routes tried in the retry pass, and what came back
| # | route | result |
|---|---|---|
| 1 | rendered page, WebFetch (first pass, ×2) | paraphrase of nav/metadata only, no body |
| 2 | /2016/01/08/the-columns_home_blooming-grove/feed/ |
that is the post's comments feed, not the post — channel metadata, zero <item> elements. Route defect: appending feed/ to a single post URL does not return the post body. |
| 3 | /2016/01/feed/ (month archive) and /2016/01/08/feed/ (day archive) |
the item is present but the fetch is cut off at <description>; the <content:encoded> CDATA block never arrives. The markdown converter appears to drop CDATA. The feed route cannot deliver a body through this tool at all — a finding that applies to every post, not just this one. |
| 4 | /wp-json/wp/v2/posts?slug=the-columns_home_blooming-grove&per_page=1 |
[] — verbatim. Also [] for the hyphenated variant the-columns-home-blooming-grove. The REST posts collection does not return this post by slug, though the permalink and oEmbed both resolve. |
| 5 | /wp-json/wp/v2/posts?per_page=1&page=4 and ?page=4&per_page=1 and ?page=4&per_page=1&_fields=… |
empty response body every time — not [], which this tool does return cleanly when WP sends one (proved at #4). Paging desc puts this post at index 4: page 1 = 3356 (2016-07-10), page 2 = 3306 (2016-05-13), page 3 = 3282 (2016-04-25), page 5 = 3195 (2015-09-12). Page 4 is the only page in that run that comes back broken. |
| 6 | /wp-json/wp/v2/posts?per_page=2&page=2 |
[], where 64 published posts should have yielded items 3 and 4. |
| — | oEmbed | worked — the metadata above. |
Reading of that evidence (inference, T3, flagged as such): the post is REST-reachable by position but every response carrying its content comes back empty, while an ordinary [] passes through fine. Something in this one post's stored content breaks the fetch path. This is the same single URL that defeated the first pass twice. It is consistent with BG-3 — a WordPress install that is already returning HTTP 500 on /directory.
Not attempted, and why: curl / wget / python fetching is prohibited on this job. A browser read is a different tool than WebFetch and was not authorised for this pass — Robert's call. If he wants this one closed, that or a GoDaddy-side export is the way.
Body — ESTABLISHED LOST AT SOURCE, not merely uncaptured
Recoverable only from a database dump or a host-side backup. Not by crawling, in any form.
Excerpt — T1, verbatim from ?_fields=excerpt, 2026-09-07T04:17:41Z
<p>“The Columns” home in Blooming Grove, Texas is now officially on the market. Owners Stuart and Eva Marshall have enjoyed two decades as stewards of this grand estate, while raising their son Chad and enjoying...</p>
Title — T1, verbatim, same response: Historic Home Hits the Market in Blooming Grove
⚑ This post's excerpt is the only surviving prose of the 10 January 2016 article. It is a real
loss and it is a small one: one post body out of 64.
Photographs
