Michael Sablone
Forum Replies Created
-
More thinking: while i’m hesitant to enable
Accept: text/markdowncontent negotiation by default, I agree there are valid advanced use cases, so I’m considering exposing it behind a developer filter. That would let site owners explicitly opt in once they’ve confirmed their cache layer respectsVary: Accept. Do you have the ability to add in your own custom hooks?Forum: Reviews
In reply to: [LLM Markdown – Expose Content as .md] Just what I neededThank you!
Thanks for the suggestion. I agree the
Accept: text/markdownpattern is becoming more common for AI-oriented content negotiation, and I did spend some time evaluating it.At the moment, I’m intentionally not implementing that behavior because I think the operational risk outweighs the upside for a WordPress plugin intended to run across a wide variety of hosting and caching environments.
The plugin currently uses explicit
.mdroutes instead, which are much safer and more predictable from a caching and infrastructure perspective.Serving Markdown conditionally from the same URL based on the
Acceptheader introduces a number of edge cases:- CDN/cache variation requirements (
Vary: Accept) - Reverse proxy compatibility
- Cache poisoning or stale cache scenarios
- Hosts that ignore or mishandle content negotiation
- The possibility of Markdown accidentally being cached and served to normal browsers
On highly cached WordPress sites, especially with Cloudflare, Varnish, Nginx microcache, or aggressive edge caching, this could realistically result in broken page output if misconfigured.
Because of that, I’m currently treating
.mdURLs plus the existing<link rel="alternate" type="text/markdown">output as the safer and more deterministic implementation.I may revisit this later as an optional advanced setting, but I don’t currently feel comfortable enabling negotiated Markdown responses by default.
Forum: Plugins
In reply to: [LLM Markdown – Expose Content as .md] Tables supportPlease remember to leave a review 🙂
Forum: Plugins
In reply to: [LLM Markdown – Expose Content as .md] Tables supportThis has been added to v1.0.1!
Forum: Plugins
In reply to: [LLM Markdown – Expose Content as .md] Tables supportGood catch. Tables are currently flattened during conversion, which is not ideal for comparison or technical content. I agree this should be handled more explicitly. I’m planning to add Markdown table conversion so
<table>,<thead>,<tbody>,<tr>,<th>, and<td>structures are preserved as pipe-table Markdown where possible.Will definitely consider this in the next release!
Forum: Reviews
In reply to: [LLM Markdown – Expose Content as .md] Works wellThanks!
Forum: Reviews
In reply to: [LLM Markdown – Expose Content as .md] Excellent ResultThank you!
I think all images failing to load — without warning or explanation — on a live production site is lethal.
Forum: Plugins
In reply to: [Time-based Revision Cleanup] Revisions not disappearingDo you know if CRON is working on your site? If you enable Save-based Cleanup and then go to the post, and make a small edit ( to activate the revision logic ) — do old ones get deleted?
Forum: Plugins
In reply to: [Time-based Revision Cleanup] Revisions not disappearingHmm — that really shouldn’t be an issue. Can you tell me all your settings?
- CDN/cache variation requirements (