SHILBe Connector

Description

Connect SHILBe to a WordPress site to import selected articles, send new drafts, and review changes to linked articles. Activating the plugin alone does not contact SHILBe. Pairing starts the article catalog sync and periodic checks for requested actions, as described under External services.

New articles may also be scheduled from SHILBe after an explicit date and automatic-publication confirmation. Scheduled creation requires the connected administrator’s post-type publication permission. Overdue requests are rejected instead of being published immediately. WordPress cron performs the eventual publication; changing or cancelling a reservation remains a WordPress administrator action. Disconnecting or ending the SHILBe subscription does not cancel reservations already registered in WordPress. Update the SHILBe API before updating this connector.

New articles may also be published upon receipt after explicit SHILBe confirmation. This requires publication permission and a publicly viewable post type. The complete draft is verified before publication, and the request expires within ten minutes. Publishing existing linked drafts remains a WordPress administrator action.

If a linked article is permanently deleted, SHILBe may request a new unpublished draft after a recent signed deletion check. The plugin checks again that neither the old post ID nor its UUID exists. Trashed, restored or inaccessible articles cannot be recreated. The replacement receives a new post ID and URL. Retries reuse the same operation; if an attempted publication or recreation result is unknown, SHILBe blocks new attempts to prevent duplicates. Check WordPress before further action.

A revision proposal never changes its source article when received. Applying it requires a separate confirmation under Settings > SHILBe Connector, stops if either article changed after the proposal was requested, and first preserves the source title and body in another unpublished backup draft. Applying changes only the source title and body; it does not change publication status, permalinks, publication dates, taxonomies, media, or custom fields. Disconnecting or uninstalling the plugin does not delete posts, pages, custom posts, or media.

New articles accept an optional slug: up to 80 lowercase ASCII letters, digits and separating hyphens. WordPress controls URLs and resolves collisions. Linked URLs stay unchanged. Update the SHILBe API before the plugin.

External services

This plugin connects to the SHILBe API when an administrator starts pairing or a catalog sync, and every five minutes after connection to check for user-requested article actions.
Pairing sends a single-use pairing code, the site URL and identifier, the protocol version, and the site’s supported post types and capabilities. WordPress login credentials stay in WordPress.

Connected posts are also checked automatically, up to 50 per cycle with a rotating cursor. Only posts already linked to SHILBe are checked. Signed reports include identity, publication status, safe public URL, UTC post date, visibility flags and a content fingerprint, never body text. Reports do not modify WordPress posts. Access-dependent WP-Cron can delay checks; configure server-side cron before production. Missing or inaccessible posts retain their last SHILBe record with a warning, rather than being assumed published or deleted.

Catalog data includes the site UUID, WordPress site URL, supported post types, post ID, immutable post UUID, post type, publication status, title, same-site URL, modification time, conversion support status, and a SHA-256 content fingerprint used to detect changes without sending the article body. Catalog data excludes article bodies, excerpts, images, arbitrary custom fields, and WordPress user information.

Article content is sent from WordPress only after the user explicitly requests an import, link, or change review for that article in SHILBe. Content sent for change review is used for a read-only comparison and does not update or publish the WordPress post.

Content sent from SHILBe to WordPress is applied only after the user explicitly requests a new draft or scheduled article, a per-article draft update, or a separate revision proposal. New content is created with draft status by default, or future status only for an explicit scheduled request, with the selected supported post type and connected administrator as author. Existing unpublished content is updated only when the connection, article UUID, post ID, post type, administrator capability, draft status, and previously observed fingerprint all match. The plugin stops if it cannot create a pre-update revision for an existing draft. Preallocated article UUIDs, operation IDs, and result fingerprints prevent duplicate writes when the same operation is delivered again.

A revision proposal is stored as a separate unpublished draft and leaves the source published article unchanged. Applying it requires an additional WordPress administrator confirmation and matching source and proposal fingerprints. Before changing the source title and body, the plugin creates a separate unpublished backup draft. The signed application result is sent to SHILBe and retried without repeating the article update if delivery fails.

When both SHILBe and WordPress changed after the last sync, neither version is applied automatically. After the user retrieves and reviews the current comparison in SHILBe, selecting the SHILBe version reuses the same guarded operation: an unchanged WordPress draft receives a revision-backed update, while a published source receives only a separate unpublished revision proposal. A changed fingerprint stops the operation.

New-article delivery can include SHILBe-owned featured and inline images, category and tag names. Images are transferred as frozen bytes over the existing authenticated HTTPS connection, not fetched from arbitrary URLs. JPEG, PNG and WebP are supported, up to eight distinct images and 8 MB total, 8000 pixels per side and 16 million pixels per image. Upload, taxonomy assignment and taxonomy creation capabilities are checked. Existing terms are reused only when names resolve uniquely; ambiguous names and slug collisions stop delivery. Existing terms are never edited or deleted. An unselected category retains the WordPress default. Images and terms are verified before a scheduled draft becomes a future post. Retried operations reuse their attachments and post, and concurrent delivery is locked. Failed delivery may leave an unpublished draft, unused media or newly created terms; check WordPress before retrying.

Supported: headings, paragraphs, line breaks, simple lists starting at one, sourced quotes, callouts, tables up to 100 rows/20 columns, and SHILBe-managed images. Tables/images require PHP DOM. Image updates reuse unchanged files and isolate changed thumbnail metadata; removal never deletes files. Updates preserve categories, tags, URL and publication settings. Explicit proposal application backs up the prior body and thumbnail. Media changes participate in conflict checks. Arbitrary image import, merged cells, column widths, multi-paragraph/list cells, nested lists, embeds, arbitrary HTML and unknown blocks stop the whole operation without omission. Update the backend before the connector.

The default API endpoint is https://api.shilbe.jp. For development, an administrator may define SHILBE_CONNECTOR_API_BASE_URL in wp-config.php with a publicly reachable HTTPS origin.

Service: https://shilbe.jp/
Terms of service: https://shilbe.jp/terms/
Privacy policy: https://shilbe.jp/privacy-policy/

Privacy

Connection credentials are encrypted using WordPress salts and stored in a non-autoloaded option.
An immutable UUID is stored in post metadata to prevent article mix-ups after reconnection. Revision proposal, source, backup, fingerprint, operation, and result-delivery identifiers are also stored in post metadata so an administrator action can be verified and retried safely. Article bodies are not stored in connector options or logs. These post identifiers are retained after uninstall; connection credentials, operational status, and scheduled hooks are removed.

Installation

You need a SHILBe account with access to WordPress integration and a WordPress site reachable over HTTPS. Only a WordPress administrator can connect the site.

  1. Upload the plugin ZIP in WordPress and activate it.
  2. Open Settings > SHILBe Connector.
  3. Generate a pairing code in the SHILBe site settings and enter it in WordPress.

For help with setup, pairing or disconnecting, use the SHILBe support form.

Reviews

There are no reviews for this plugin.

Contributors & Developers

“SHILBe Connector” is open source software. The following people have contributed to this plugin.

Contributors

Translate “SHILBe Connector” into your language.

Interested in development?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.

Changelog

0.2.2

  • Limit block parsing to 1 MB, 10,000 parsed nodes and 64 levels; stop without partial exports or fingerprints.

0.2.1

  • Use the WordPress URL parser for links in imported and delivered articles. Document account requirements and support. Verified on WordPress 7.1.

0.2.0

  • Managed image updates/proposals, removal, reuse, backups and media-aware conflict checks. Capability checks stop incompatible connectors.

0.1.0

  • Provisional pairing and metadata-only catalog implementation.
  • Explicit per-article import and link snapshot handling with fail-closed block conversion.
  • Explicit read-only change review snapshots without WordPress writes.
  • Explicit idempotent creation of new unpublished WordPress drafts for supported post types.
  • Explicit idempotent updates for unchanged WordPress drafts with revision and fingerprint guards.
  • Separate revision proposals for unchanged published articles, explicit WordPress-side application, pre-application backup drafts, and signed idempotent result reporting.
  • Explicit conflict resolution using reviewed versions, with no automatic overwrite when both sides changed.