Cadence Connector

گزارش تغییرات

0.11.0

• The adopt endpoints answer one code, adopt_post_out_of_scope, and one
  sentence naming no id, for a post that is absent, of a type or in a state
  the key may not adopt, one of the site’s own pages, or carrying another
  key’s rows. post_missing, adopt_post_type_out_of_scope,
  adopt_post_unavailable and adopt_site_page are gone from them.
  post_already_identified now means the post carries this key’s own rows.
• A key’s release answers not_adopted, with no id, for an absent post as
  for one it did not adopt.
• The replace and slug-change endpoints refuse a post in a status that is
  not placed (trash, auto-draft and the like) with post_out_of_scope, as
  the read endpoint already does.

0.10.0

• The replace and slug-change endpoints answer one code, post_out_of_scope,
  and one sentence naming no id, for a post that is absent, not published or
  adopted through this plugin, or made by another key. replace_other_key is
  gone and post_missing no longer comes from these two endpoints. A key’s own
  piece in a post type it does not reach still answers
  existing_post_type_out_of_scope.

0.9.0

• New endpoint to read one post, signed and bound to this site and a short
  time window, for a key allowed to rewrite that post.
• The replace endpoint accepts an optional excerpt, SEO title and SEO
  description, each signed when present.
• New endpoint to change a post’s slug, signed and confirmed once, and only
  from the slug the caller saw. WordPress keeps redirecting the old address of
  a published post, as it does for any slug change.

0.8.0

• New capability, content.adopt, and four endpoints to use it: preview then
  adopt a post this connector did not create, by pasting its wp-admin edit
  link or its public permalink, so it can become the source of a translation
  group; preview then release one, undoing an adoption. A “Release from
  Cadence” row action does the same from the posts list in wp-admin.
• Rewriting an adopted post’s title or text through the replace endpoint now
  needs a signed, time-limited, one-time confirmation from the caller.
• Signed adopt, release and rewrite requests name the site by host and path,
  so two installs on one host cannot accept each other’s requests.
• Trashed pieces are now found by the duplicate-piece lookup, so a piece
  already trashed on the site is not published a second time.
• A status or password change made by hand while a rewrite is in flight is no
  longer reverted by that rewrite.
• Revisions, attachments and other posts that are not ordinary content are
  now refused by the endpoints that publish, replace and link, instead of
  being acted on.
• A translation group now holds one post type only; linking a plan that mixes
  types is refused.
• The settings screen no longer uses dashes.
• An attestation public key already attached to one connector key is refused
  on another, so each connector key needs its own signing key.
• Fixed: the settings screen could fail to load for a key whose id was all digits.

0.7.0

• The translation-linking route now requires an Ed25519 attestation over the
  plan’s own bytes, as the publishing and replacing routes already did.
• Connector keys carry the post types they may reach; a key that no longer
  publishes a type no longer links it either.