96532
results for "wordpress"
-
It means that the plugin needs mf2 dependencies to parse Microformats out of content, probably
GWG
at
2026-01-13 17:56
-
I would like like to have the post_content set, this way it is more reliable and does not break the site when you deactivate the plugin. I think we should have a way to clear the content, so that it will be re-generated
[pfefferle]
at
2026-01-13 14:29
-
I had researched that early in blocks as the block parser does that
GWG
at
2026-01-12 16:17
-
[snarfed]: Probably the most compatible option is to do it like blocks does... parse the content dynamically
GWG
at
2026-01-12 16:04
-
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
[snarfed]
at
2026-01-12 15:55
-
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
GWG
at
2026-01-12 15:51
-
or maybe object cache, so it integrates better with WordPress's cache invalidation
[snarfed]
at
2026-01-12 15:48
-
[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?
[pfefferle]
at
2026-01-12 06:25
-
I accepted a small-medium quest line. Im going to help assess the sturdiness of a volunteer orgs wordpress calendar plugin. Ill make suggestions but basically I think Ive managed expectations that Im mostly an assisting source
[morgan]
at
2026-01-10 05:01
-
why can't I merge https://github.com/indieweb/wordpress-micropub/pull/304 🤔
[pfefferle]
at
2026-01-09 22:22