Linux 软件免费装

在这里免费安装WordPress以及其他软件

Banner图

Blurt Publisher

开发者 khrom
更新时间 2026年6月16日 00:10
PHP版本: 7.4 及以上
WordPress版本: 7.0
版权: GPLv2 or later
版权网址: 版权信息

标签

woocommerce blockchain publishing social-media blurt

下载

1.7.7 1.7.6

详情介绍:

Blurt Publisher connects WordPress with the Blurt blockchain. The recommended publishing mode is Direct RPC. In this mode WordPress prepares the Blurt transaction, signs it locally with the private posting key saved in the plugin settings, and broadcasts the signed transaction directly to public Blurt RPC nodes. No external plugin endpoint is needed. The plugin can publish:

安装:

  1. Upload the plugin folder to /wp-content/plugins/ or install the ZIP file in WordPress admin.
  2. Activate Blurt Publisher.
  3. Open Blurt Publisher → Welcome.
  4. Open Blurt Publisher → Settings.
  5. Enter your Blurt author account without @.
  6. Save your private posting key. Use the private posting key only.
  7. Keep Publishing Mode set to Direct RPC unless you explicitly need fallback endpoint mode.
  8. Configure tags, community, reward and schedule.
  9. Use Publish Next Post for a controlled test.
  10. If WooCommerce products should be published, configure Blurt Publisher → Product Settings.

升级注意事项:

1.7.7 Adds the WordPress.org View details link on the plugins screen. 1.7.6 Moves Settings CSS to enqueue and lowers admin menu position for review. 1.7.3 Scheduled runs now publish one item per run, matching the selected frequency. 1.7.2 Shortened upgrade notices for WordPress.org readme validation. 1.7.1 Restores the admin menu position near WordPress content management screens. 1.7.0 Renamed plugin package for WordPress.org review. 1.6.7
  • Fixed queue lookup after Plugin Check query changes. Manual Publish Next now scans the visible queue correctly and automatic publishing no longer stops after the first flagged batch.
1.6.6 Adds encrypted secret storage. Re-save private keys if encryption settings or WordPress salts changed.

常见问题:

Do I need an endpoint?

No. Direct RPC mode does not need an endpoint. The endpoint is only an optional fallback for hosting environments where Direct RPC cannot be used.

Does Direct RPC send my private posting key outside WordPress?

No. Direct RPC mode signs transactions locally inside WordPress and broadcasts only signed transactions.

Are private keys encrypted in WordPress?

Yes, private posting keys and endpoint fallback credentials are encrypted at rest when OpenSSL AES-256-GCM is available. If OpenSSL AES-256-GCM is unavailable, the plugin will show an admin warning and will not save new private keys securely.

Can I use a custom encryption key?

Yes. Define BLURT_PUBLISHER_ENCRYPTION_KEY in wp-config.php before saving keys if you want a custom encryption secret independent of WordPress salts.

Does legacy endpoint fallback send my private posting key?

Yes. Legacy fallback exists for compatibility. The request is protected with HMAC, nonce and timestamp, but the endpoint still receives the private posting key for that one publication request.

Can products use a different Blurt account?

Yes. Products have their own author and private posting key settings.

Can I publish only excerpts?

Yes. Posts and products can publish full content or excerpt/teaser-only content.

What key should I use?

Use the private posting key only. Never use the owner key or active key in this plugin.

更新日志:

1.7.7 1.7.6 1.7.3 1.7.2 1.7.1 1.7.0 1.6.7 1.6.6 1.6.4 1.6.3 1.6.2