v0.47.0

v0.47.0

• Added: Extra custom fields — a new setting listing the post meta keys whose
  values belong in the Markdown. Their content is appended to the end of the
  body, in the order listed. One setting covers ACF, JetEngine, Meta Box and
  WordPress's own Custom Fields box, because underneath they all store post meta,
  so a page whose text comes partly from a template's fields is no longer
  published half missing. Empty by default and never detected automatically: a
  field starts appearing when you type its key into the box, and not before.
  Values that are not text — an image, a repeater, anything stored as an array —
  are skipped rather than guessed at.
• Added: sysmda_markdown_extra_meta_keys (Stable) as the filter behind the new
  setting, so the list can be varied per post from code.
• Changed: a post that does not carry any of the configured keys keeps its
  document and its cache validator byte-identical, so configuring a field for a
  couple of landing pages does not make every article on the site revalidate.
• Fixed: ACF field values added through sysmda_acf_field_keys never reached a
  Bricks page's Markdown. Such a page is rendered through Bricks' own API, which
  does not read the post content the values were appended to, so they were
  dropped silently — since 0.46.0. Both they and the new custom fields now go
  through a dedicated sysmda_markdown_appended_html filter (Advanced) that is
  honoured on every render path.
• Fixed: the Excluded builder elements setting added in 0.46.0 was not removed
  on uninstall.