| 开发者 | giusetavera |
|---|---|
| 更新时间 | 2026年7月6日 16:52 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 6.9 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
[gtlss] shortcode anywhere in the content[gtlss] shortcode for manual placementYes. You need a valid OpenAI API key to use this plugin. You can create one at https://platform.openai.com/account/api-keys. OpenAI offers a free trial credit for new accounts.
No. Summaries are generated only when you explicitly click Generate in the post editor, or run a bulk generation from the admin panel. Once generated, the summary is stored in the post and served directly from the database — no API calls happen on the frontend.
The summary is stored in the WordPress database as post meta, associated with the individual post. It is not part of the post content and can be regenerated or erased at any time.
You can configure a fallback position in GTLSS → Settings. The summary can be inserted before or after the post content when no H2 heading is found.
Yes. Set the display mode to Shortcode in Settings, then add [gtlss] anywhere inside the post content.
No. The summary is generated once and cached in post meta. On the frontend, the plugin only queries the database for the stored summary — it never calls the OpenAI API during page load.
No. The plugin contains no telemetry, analytics, or tracking code of any kind.
The plugin uses gpt-4o-mini by default. Developers can change the model via the gtlss_provider_model filter.
The endpoint, headers, and request body are all overridable via filters (gtlss_provider_endpoint, gtlss_provider_headers, gtlss_provider_body), making it possible to point the plugin at any OpenAI-compatible API.
[gtlss] shortcode support for manual placement