| 开发者 | zimplico |
|---|---|
| 更新时间 | 2026年6月1日 23:56 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
<img> tags when saved.site_id that the API validates per-request against the registered domain via the browser's Origin header.
Privacy
Text and images submitted via zimpliScribe are sent to the zimplico.de API and forwarded to the AI provider for processing. Content is not stored long-term by zimplico.de — see the privacy policy at https://zimplico.de/privacy.html for specifics on retention, processing, and provider details.
External services
This plugin relies on external services to provide its functionality. No data is sent before you actively register your site, and no AI request is sent until you submit one.
zimplico.de API (https://api.zimplico.de/zimpliscribe)
zimpliscribe folder to /wp-content/plugins/, or install through the WordPress plugin directory.No. The plugin connects to zimplico.de, which handles AI provider relationships and billing on your behalf. You only need a zimplico.de account, which is created automatically when you register your site.
Every new site gets 25 welcome credits (non-expiring) plus 5 free credits a month. Beyond that, top up via the billing portal — current per-credit pricing is shown at registration time and on the billing page.
The plugin will display the response from the API and offer a link to the billing portal in a new tab. Your in-progress text is preserved.
No — that's the point. Provider keys live server-side at zimplico.de, where they can be rotated and monitored centrally. WordPress never holds AI credentials.
The dedicated zimpliScribe admin page works regardless of editor. The Gutenberg sidebar requires the block editor.
Each site in a multisite network registers separately and has its own credit balance. The plugin will be activatable network-wide in a future release.
esc_attr_e() into the non-existent esc_attresc_html_e(), which crashed the Content Tool / Settings / Contact tabs (and prevented site registration, since the page died before its JavaScript loaded). Restored to esc_attr_e()./* translators: */ comments to sit immediately above their __() calls inside wp_kses() wrappers, so the WPCS i18n sniff picks them up. No functional or text changes._e() output with esc_html_e(); wrap intentional inline HTML strings with wp_kses(__()); add /* translators: */ comments for placeholder-bearing translations; wp_unslash() superglobals before sanitization; cache attachment-by-filename lookup. No functional changes.https://api.zimplico.de/zimpliscribe (was …/zimplscribe) to match the renamed Go service. Pairs with the 1.14.0 plugin rename; both ends now use the consistent zimpliscribe path.zimpliscribe throughout (folder, file names, Text Domain, internal identifiers) to match the brand and the wordpress.org slug. Breaking change for sites running the dev zimplscribe version: deactivate and delete the old plugin folder, install fresh, and re-register the site. WP options (zimplscribe_* → zimpliscribe_*), REST namespace (zimplscribe/v1 → zimpliscribe/v1), and AJAX action names were all renamed; the previous installation's stored data is not migrated.sslverify => false from all wp_remote_* calls).