#wordpress 2026-01-12

2026-01-12 UTC
squidwizard, jeremycherfas, gRegor, ajwatts, Steven[d] and [pfefferle] joined the channel
#
[pfefferle] [dshanske] while working on https://github.com/indieweb/wordpress-micropub/issues/303 I thought about the dynamic rendering a bit more... this can get quite heavy, when we do the same rendering logic on every load? shouldn't we still use the content as "cache" that can be cleared or re-rendered?
DanQ, [KevinMarks], IWSlackGateway, [jeremycherfas], jeremycherfas and [snarfed] joined the channel
#
[snarfed] or maybe object cache, so it integrates better with WordPress's cache invalidation?
#
GWG Well, that's why the original issue is still open...and how the rendering works is still a hard issue. Not only do we have old school content, we have now the indieblocks implementation as well
[social] joined the channel
#
[snarfed] there are lots of paths to compatibility. if it's hard to do backward compatibility with existing posts with content in the db, you can always do a migration instead
#
GWG [snarfed]: Probably the most compatible option is to do it like blocks does... parse the content dynamically...
[Murray] joined the channel
#
GWG I had researched that early in blocks as the block parser does that
[aciccarello], [tantek], gRegor, [KevinMarks], DanQ, artlung, [artlung] and yashikru joined the channel