| 开发者 | archiver |
|---|---|
| 更新时间 | 2026年8月18日 01:53 |
| PHP版本: | 8.1 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
SERVIX_API_KEY in wp-config.php, or enter a key under Settings > Servix Market Data.Yes. The plugin requires an API key with active test or paid access. Current availability, duration, and quotas are described on the Servix website.
Not by default. A site owner may explicitly enable the Servix.cc attribution link under Settings > Servix Market Data. The setting does not change data access or disable plugin functionality. If an active Servix plan requires attribution, enable the setting before displaying that plan's data.
Yes. A customer with an active API entitlement may display selected values on a customer-controlled website under the active plan and Servix terms.
No. Requests originate from WordPress PHP and the plugin never places the key in HTML, JavaScript, URLs, or public responses.
Only when an administrator tests the connection, the block editor requests the supported catalog or a preview, or a frontend display needs data that is not available in its valid cache.
Deactivation preserves settings for later reactivation. Uninstalling through WordPress removes plugin settings, the stored API key, and plugin-owned cache entries. Existing posts retain only asset codes, shortcode text, and presentation options; they do not contain the API key or complete API responses.
Contact info@servix.cc with the plugin version, WordPress and PHP versions, safe diagnostic code, and request time. Never send an API key or complete authenticated API response.
WordPress.org provides approved Persian translations as a separate language pack. Persian sites may temporarily show the English source text until the community translation is reviewed and the language pack becomes available.
servix-market-data text domain.