Beskrivelse

AI-pluginet bringer AI-drevne funktioner direkte ind i din WordPress-administration og redigeringsoplevelse.

Kræver WordPress-blokredigeringsprogrammet. Plugin’et »Classic Editor« og andre redigeringsmiljøer, der ikke er baseret på blokredigeringsprogrammet, understøttes ikke.

Hvad indeholder det:

Dette plugin er bygget på initiativet AI Building Blocks for WordPress og kombinerer AI Client-biblioteket og Abilities API i én samlet oplevelse. Det fungerer både som et praktisk værktøj for indholdsskabere og som en referenceimplementering for udviklere.

Nuværende funktioner:

  • Abilities-udforsker – Gennemse og interager med registrerede AI-funktioner fra en dedikeret administrationsskærm.
  • AI-anmodningslogning – Logger AI-anmodninger til observerbarhed og fejlfinding.
  • Generering af alt-tekst – Generer beskrivende alt-tekst til billeder for at forbedre tilgængeligheden.
  • Comment Moderation – Automatically moderate comments based on toxicity detection and sentiment analysis, and give each comment a value score.
  • Connector-godkendelser – Kræv eksplicit administratorgodkendelse, før plugins eller temaer kan bruge AI-connectors, der er konfigureret på dette websted.
  • Indholdsklassificering – Foreslår relevante tags og kategorier til at organisere indhold.
  • Indholdsstørrelse – Forkort, udvid eller omformuler markeret blokindhold.
  • Indholdsopsummering – Opsummerer langt indhold til letfordøjelige oversigter.
  • Content Translation – Translates paragraph and heading blocks, and optionally the post title, into a selected language from the post editor.
  • Custom Abilities – Gates the plugin’s general-purpose WordPress Abilities behind a single opt-in toggle.
  • Kontrolpanel-widgets – AI-status og AI-funktioner-widgets samt framework til registrering af nye widgets.
  • Redaktionelle noter – Gennemgår indlægsindhold blok for blok og tilføjer noter med forslag til tilgængelighed, læsbarhed, grammatik og SEO.
  • Redaktionelle opdateringer – Anvend automatisk redaktionelle noter på indhold.
  • Uddragsgenerering – Opret automatisk korte opsummeringer til dine indlæg.
  • Eksperiment-framework – Opt-in-system, der lader dig aktivere kun de AI-funktioner, du vil bruge.
  • Retningslinjer – Lader funktioner respektere webstedsdækkende redaktionelle standarder.
  • Billedgenerering og -redigering – Opret og rediger billeder fra indlægsindhold i editoren og også via mediebiblioteket.
  • Nøglekryptering – Krypterer AI-udbyderens API-nøgler i hvile ved hjælp af den medfølgende libsodium-kryptering. Nøglerne dekrypteres automatisk ved læsning og krypteres igen ved skrivning. Hvis man deaktiverer eksperimentet eller plugin’et, gendannes nøglerne i klartekst.
  • Generering af metabeskrivelse – Genererer forslag til metabeskrivelser og integrerer dem med forskellige SEO-plugins.
  • Understøttelse af flere udbydere – Fungerer sammen med AI Connector-plugins til udbydere som OpenAI, Google og Anthropic.
  • Slug Generation – Suggest SEO-friendly permalink slugs for your posts from the permalink popover or the pre-publish panel, then edit and apply the one you want.
  • Suggest Reply – Adds a “Suggest Reply” action to the Comments screen and Activity widget, enabling moderators to quickly generate comment reply suggestions.
  • Titelgenerering – Generer titelforslag til dine indlæg med et enkelt klik. Perfekt til at brainstorme overskrifter eller finde den rette tone til dit indhold.
  • Type Ahead – Kontekstuel skrivehjælp til forslag, mens du skriver.

Opsætning af udbyder:

AI-pluginet indeholder ikke i sig selv adgangsoplysninger til udbydere eller implementeringer fra udbydere. For at kunne bruge AI-baserede funktioner skal du installere og aktivere mindst ét AI Connector-plugin og derefter konfigurere dets adgangsoplysninger under Indstillinger -> Connectors. Funktionerne vises muligvis som utilgængelige, indtil en connector er installeret, godkendt og i stand til at udføre den påkrævede handling.

Blandt plugins til udbyderforbindelser findes Anthropic, Google, OpenAI og andre.

Kommer snart:

Vi udvikler aktivt nye funktioner, der kan forbedre dit WordPress-workflow:

  • AI Playground – Eksperimenter med forskellige AI-modeller og udbydere.
  • Indholdsassistent – AI-drevet skrivning og redigering i Gutenberg.
  • Webstedsagent – WordPress-administration med naturligt sprog.
  • Workflowautomatisering – AI-drevet automatisering af opgaver.

Dette er et eksperimentelt plugin. Funktionaliteten kan ændre sig, efterhånden som vi indsamler feedback fra fællesskabet.

Roadmap:

Du kan se pluginets aktive roadmap i en filtreret visning i WordPress AI GitHub Project Board.

For udviklere

AI-pluginet er designet til at blive studeret, udvidet og bygget videre på. Uanset om du er pluginudvikler, bureau eller hostingudbyder, kan du gøre følgende:

Udvid pluginet:

  • Byg brugerdefinerede eksperimenter – Brug basisklassen Abstract_Feature til at oprette dine egne AI-drevne funktioner.
  • Prækonfigurer udbydere – Hostingfirmaer og webbureauer kan konfigurere AI Connector-plugins, så brugerne ikke behøver deres egne API-nøgler.
  • Abilities-udforsker – Test og udforsk registrerede AI-funktioner (tilgængelig når eksperimenter er aktiveret).
  • Registrer brugerdefinerede funktioner – Kobl dig på Abilities API for at tilføje nye AI-muligheder.
  • Tilsidesæt standardadfærd – Brug filtre til at tilpasse prompts, svar og UI-elementer.
  • Omfattende hooks – Filtre og handlinger i hele kodebasen til tilpasning.

Udviklerværktøjer kommer snart:

  • AI Playground – Eksperimenter med forskellige AI-modeller og prompts.
  • MCP (Model Context Protocol) – Integrer og test Model Context Protocol-muligheder i WordPress-workflows.
  • Udvidede udbydere – Understøttelse af eksperimenter med yderligere eller alternative AI-udbydere.

Kom i gang:

  1. Læs bidragsvejledningen for opsætning af udviklingsmiljøet
  2. Deltag i samtalen i #core-ai på WordPress Slack
  3. Gennemse GitHub-repositoriet for at se, hvordan eksperimenter er bygget
  4. Deltag i diskussioner om, hvordan pluginet bedst bør udvikles.

Vi byder bidrag velkommen! Uanset om du vil bygge nye eksperimenter, forbedre eksisterende funktioner eller hjælpe med dokumentation, kan du kigge i vores GitHub-repositorium for at komme i gang.

Skærmbilleder

Installation

  1. Upload pluginfilerne til mappen /wp-content/plugins/ai, eller installer pluginet direkte via WordPress’ pluginskærm.
  2. Aktivér pluginet via skærmen ‘Plugins’ i WordPress.
  3. Installer og aktiver mindst ét AI Connector-plugin, og gå derefter til Indstillinger -> Connectors og konfigurer dets adgangsoplysninger.
  4. Go to Settings -> AI and enable the features or experiments you want to use.
  5. Begynd at eksperimentere med AI-funktioner! For eksperimentet Titelgenerering skal du redigere et indlæg og klikke i titelfeltet. Du bør se en Generer/Generer igen-knap over feltet. Klik på den knap, og når anmodningen er fuldført, vises titelforslag i en modal. Vælg den titel, du kan lide, og klik på knappen Vælg for at indsætte den i titelfeltet.

FAQ

Hvad bruges dette plugin til?

Dette plugin bringer AI-drevne skrive- og redigeringsværktøjer direkte ind i WordPress. Det er også en referenceimplementering for udviklere, der vil bygge deres egne AI-funktioner.

Er det sikkert at bruge på et produktionswebsted?

Dette er et eksperimentelt plugin, så vi anbefaler at teste i et stagingmiljø først. Funktioner kan ændre sig, efterhånden som vi indsamler feedback fra fællesskabet. Alle AI-funktioner er opt-in og kræver manuel aktivering – der sker intet automatisk uden din godkendelse.

Hvilke AI-udbydere understøttes?

Pluginet kan bruges sammen med udbyder-connector-plugins fra Anthropic (Claude), Google (Gemini), OpenAI og andre. Installer og aktiver det relevante connector-plugin, og konfigurer det derefter under Indstillinger -> Connectors.

Skal jeg bruge en API-nøgle for at bruge funktionerne?

Ja, i øjeblikket skal du selv angive din API-nøgle til det konfigurerede AI Connector-plugin, f.eks. OpenAI, Google AI eller Anthropic.

Hvad koster det?

Selve pluginet er gratis, men du skal betale for brugen af API’et hos den AI-udbyder, du vælger. Omkostningerne varierer alt efter udbyder og forbrug. De fleste udbydere tilbyder gratis prøvekreditter, så du kan komme i gang. Der findes også nogle lokale, open source- og gratis udbydere (som f.eks. Ollama), som du ligeledes kan benytte.

Kan jeg bruge dette uden kodekendskab?

Helt sikkert! Pluginet er designet til indholdsskabere og webstedsadministratorer. Når dine AI-connectors er konfigureret, kan du bruge AI-funktionaliteten direkte fra indlægseditoren.

Understøtter dette plugin den klassiske editor?

Nr.

AI-pluginet understøtter i øjeblikket kun Block Editor (også kendt som Gutenberg). Pluginet er udviklet med udgangspunkt i moderne editor-API’er, blokbaserede arbejdsgange for indhold og de stadigt udviklende redigeringsfunktioner, der udvikles inden for WordPress-kernen (herunder Gutenberg).

Blokredigeringsværktøjet har været standardredigeringsværktøjet i WordPress siden WordPress 5.0 i 2018 og er fortsat det primære fokus for den aktive udvikling af redigeringsværktøjet. Ved at koncentrere udviklingsindsatsen om blokredigeringsværktøjet kan projektet hurtigere lancere nye funktioner, eksperimenter og integrationer, samtidig med at man undgår den kompleksitet, der er forbundet med at vedligeholde parallelle implementeringer på tværs af flere redigeringsværktøjer.

Selvom Classic Editor-pluginet fortsat har en stor brugerbase, har Core AI-teamet valgt at prioritere innovation og eksperimentering inden for Block Editor-økosystemet. På nuværende tidspunkt er der ingen planer om at tilføje officiel understøttelse af Classic Editor.

Hvor kan jeg få hjælp eller rapportere problemer?

Du kan stille spørgsmål i #core-ai-kanalen på WordPress Slack eller rapportere problemer i GitHub-repositoriet.

Anmeldelser

13. september, 2026 1 svar
It is quite useful and performs well, but why did you change the language from “Basic summary” to TL;DR as the title for content summarization? Not everyone who visits our site is a teenager on social media, 25 hours per day.
3. juni, 2026 1 svar
I love the idea in theory, and connecting my OpenAI account was easy enough. I was hoping to be able to use the plugin to help with content writing, rather than copying and pasting from ChatGPT. As I use Elementor Page Builder I have the Classic Editor plugin installed – unfortunately this plugin doesn't work with the Classic Editor, so I can't see any of the AI features when writing Posts. Hopefully there will be improvements in the future 🙂
Læs alle 9 anmeldelser

Bidragsydere & udviklere

“AI” er open source-software. Følgende personer har bidraget til dette plugin.

Bidragsydere

“AI” er blevet oversat til 18 sprog. Tak til oversætterne for deres bidrag.

Oversæt “AI” til dit eget sprog.

Interesseret i udvikling?

Gennemse koden, tjek SVN repository, eller abonner på udviklerloggen via RSS.

Ændringslog

1.4.0 – 2026-10-05

Tilføjet

  • When comment moderation is run, calculate a value score, providing a relevance signal (0–1) for each comment based on how substantive and on-topic it is relative to the post it was left on. Show this score in a new column on the comment screen (#681).
  • New experiment, Markdown Feeds, that creates markdown feeds at /feed/markdown/ (available in every feed context) and of individual posts and pages via ?output_format=markdown (#855).
  • User-triggered retry for Content Translation if it fails (#941).
  • Limit comment moderation bulk analysis queue size (#972).
  • Storage and CRUD layer for embedding vectors (new wpai_embeddings table) that can be used to recording the provider and model alongside every vector (#976).
  • 9 new default target languages to the Content Translation experiment (#986).
  • Guideline categories support to the Content Translation Ability (#987).
  • New Vector_Math and Vector_Ranker classes, allowing users to run similarity and ranking queries against vectors (#993).
  • Loading indicator for type-ahead suggestion requests (#1029).
  • Integrate Alt Text Generation with the Image block’s decorative setting (#1031).

Ændret

  • Bump minimum supported WordPress version to 7.0.3 (#1001).
  • Display specific taxonomy labels in Content Classification notice error messages instead of generic terminology (#916).
  • Show a notice and disable title translation when the post title is too short (#967).
  • Update to the latest version of the embedding code from the
    PHP AI Client (#975).
  • Our generate_embeddings helper function now requires a
    specific embedding model. Pass model (a model ID or a ModelInterface
    instance) and, for a model ID, the provider that offers it. This is a
    breaking change for anyone that happened to start using this function (#975).
  • Update Settings vertical ellipsis icon to tool icon (#1001).
  • The core/read-content and core/read-users abilities are renamed to core/content-query and core/users-query. The old names keep working as deprecated aliases for now (#1002).
  • Use gpt-image-2.5-flare as our default OpenAI image generation model (#1023).
  • The core/read-settings ability has been renamed to core/settings-get. The old name keeps working as a deprecated alias for now (#1087).

Deprecated

  • The ai/get-post-details ability. Use the single-post mode of core/content-query instead (#1002).

Fjernet

  • Unnecessary URL validation that is now handled by WordPress core (#1011).
  • The Enable AI header toggle from the AI settings page (#985).

Rettet

  • Ensure focus moves to the Accept button when content generation completes in the Content Resizing modal (#917).
  • Increase the default request timeout from 5 seconds to 30 seconds when Core revalidates API keys. If this validation request times out, Core will delete the API key so this is an attempt to fix that (#947).
  • Cached the active SEO plugin detection – with a TTL and immediate invalidation on any plugin activation/deactivation – so meta description meta-key lookups no longer re-scan active plugins on every request (#973).
  • Improves the Content Translation loading animation to preserve existing text and background colors (#977).
  • Settings page failing to render on Gutenberg 23.9+ after @wordpress/dataviews was removed from the private-apis allowlist (#989).
  • Ensure our guidelines integration reads published guideline rows from the wp_knowledge post type instead of the removed wp_guideline so those work with the latest version of Gutenberg. We don’t migrate data from the old post type and taxonomy to the new so anyone that had previously set guidelines in an older version of Gutenberg will need to re-add those (#988).
  • Import core’s prefixed PSR EventDispatcher in the vendored EmbeddingBuilder (#1005).
  • Reserve space for type-ahead text generation when caret is at the end (#1008).
  • Updated the settings page container min-height so that it spans the full viewport height (#1013).
  • Fix focus style on collapsible card by updating the @wordpress/dataviews package to latest version (#1035).
  • AI Request Logs now records HTTP error responses (4xx/5xx) from providers as error with the status code and message, instead of success; Gemini text generation requests are no longer mislabeled as Metadata (#1040).
  • Hide the “Suggest Reply” button when the inline comment form is in Quick Edit mode (#1049).
  • Editorial Notes only reviewing template blocks when “Show template” mode is enabled in the block editor (#1053).
  • Insert the generated summary into the post content when Show template is enabled (#1055).
  • Aligned the focus styles of Content Classification suggestion pills with the core Button component (#1060).
  • Connector Approvals no longer blocks core’s connector key check by attributing it to the provider plugin or to Gutenberg (#1070).
  • Abilities Explorer no longer crashes when an ability’s input property lists several types (#1073).
  • Preserve HTML entities and text between shortcodes when normalizing content, while still encoding entity-encoded tags (#1077).
  • Prevent options.php validation error when saving general settings with abilities active (#1080).
  • Ensure post titles, the site tagline and excerpts no longer contain HTML entities in the markdown feeds (#1086).
  • Ensure markdown feeds don’t 404 when the rewrite rules were rebuilt without the feed in place (#1110).

Sikkerhed

  • Ensure we check for the moderate_comments capability before we allow bulk comment moderation and then check for the edit_comment capability for each individual comment that is being moderated (GHSA-pjw7-q94g-4q34).
  • Harden the Playground preview publishing workflow to derive pull request and commit metadata from the triggering workflow run (#978).
  • Harden JSON data parsing on admin screen (#991).

1.3.0 – 2026-08-18

Tilføjet

  • New Experiment: Content Translation; translates Paragraph and Heading blocks—and optionally the post title—into a selected language directly from the post editor (#747).
  • New Experiment: Slug Generation; suggest SEO-friendly permalinks that can be set as the slug (#897, #932).
  • New Experiment: Custom Abilities. Gates the plugin’s custom WordPress Abilities (ai/get-post-details, ai/get-post-terms, core/read-settings, core/read-users, core/read-content) behind a single opt-in toggle, so enabling it exposes all of them at once via the Abilities API. Note for anyone that is using these Abilities, you’ll need to enable this new experiment first for those to be available (#881).
  • New Developer Tool: Import/Export functionality for non-sensitive AI settings (#734).
  • Cleanup plugin data when the plugin is deleted (#692).
  • AI-specific Site Health integration and status tests (#734).
  • New filters, wpai_content_classification_available_terms, wpai_content_classification_min_confidence and wpai_content_classification_candidate_pool_size, to allow more control over Content Classification (#633).
  • Prompt template extension points, making it easy for others to filter prompts and prompt builders (#770).
  • Brought the embedding code over from the PHP AI Client and load that conditionally so those using the AI plugin can start to take advantage of embedding generation (#892, #946).
  • Public WordPress\AI\log_ai_request() API so MCP servers and ability consumers can record requests in the AI Request Log (#914).

Ændret

  • Updated all meta keys to use the wpai_ prefix instead of just ai_. Note this changes the prefix on the ai_generated, ai_generated_summary and ai_note meta so if you are directly using those, update to using the wpai_ names (#867).
  • Updated preferred models to more recent ones for the three default providers (#913).
  • Bump WordPress tested-up-to version 7.1 (#934).
  • Improve the relevance of category and tag suggestions produced by the
    Content Classification experiment (#633).
  • Editorial Updates now links to the visual revisions screen when reviewing refined content, falling back to the classic revisions screen when visual revisions are unavailable (#861).
  • Reordered setting experiments list; grouped linked experiments and sorted editor experiments alphabetically (#871).
  • Improved keyboard focus handling when generating, accepting, or dismissing classification suggestions (#873).
  • The Abilities Explorer provider filter dropdown now includes custom providers, and the overview statistics count abilities by origin so custom-provider abilities remain in their Core/Plugins/Theme bucket (#884).
  • Set focus to the generated title textarea when generating a title (#901).
  • The core/read-users ability now returns collections ordered by display name, A to Z (#948).

Deprecated

  • The AI_Service class and the get_ai_service() helper introduced in 0.2.1 will be removed in the next major release. Neither is used anywhere in the plugin; experiments and abilities call wp_ai_client_prompt() directly (#905).
  • Filter wpai_meta_description_result_temperature is no longer being used and will be removed in the next release (#913).

Fjernet

  • No longer set custom temperature values on any of our requests (#913).

Rettet

  • The AI Request Log REST endpoint now registers its operation filter parameter, so it appears in the REST schema and a non-string value returns a 400 instead of causing a fatal error (#758).
  • Inline reply textarea not receiving focus after generating a suggested reply (#877).
  • Meta Description suggestions applied on pages and custom post types were lost on save when Yoast SEO was active (#886).
  • Improved accessibility and keyboard usability for the request logs provider/model details (#889).
  • Improved keyboard and focus handling for the Suggest Reply tone dropdown (#907).
  • Synchronized generating state across the inline and modal excerpt generation buttons (#908).
  • Ensure caller detection in the encryption experiment properly matches the calling plugin, not the host plugin (#909).
  • Synchronized loading state between the sidebar and block toolbar regenerate summary buttons (#912).
  • Preserve inline HTML when resizing content (#915).
  • Bulk actions no longer re-run when sorting or paginating the list after the action completes (#928).
  • Apply editorial updates to blocks that store editable text in the value attribute (#930).

Sikkerhed

  • Ensure any content we render from the LLM or content we send to the LLM is properly sanitized (#950).
  • Add proper nonce check prior to bulk alt text and summarization generation (GHSA-hfp9-55vw-ccjc).
  • When passing a custom image URL to the Alt Text Generation Ability, ensure that URL is public, that it points to an allowed image type and that the final URL we download matches the initial one we verify (GHSA-v2wx-9j88-4rqq).

1.2.0 – 2026-07-14

Tilføjet

  • New Experiment: Suggest Reply; gives comment moderators a quick way to generate a reply to a comment through the admin (#724).
  • New “Advanced settings” option in Developer Tools to show/hide additional configuration options for features and experiments (#842).
  • Bulk “Generate AI Summary” action to the posts and pages list table, enabling summary generation for multiple posts at once (#650).
  • New core/read-content Ability with secure single-post and query modes (including include and opt-in fields) to enable read-only content access (#739).
  • New core/read-users Ability that retrieves a single user by ID, email, login, or nicename, or a filtered and paginated users collection, with sensitive fields opt-in and permission-gated (#774).
  • An inline admin notice when Connector Approvals are enabled and no AI connectors are yet approved, prompting admins to approve the AI plugin for use (#830).
  • Introduce new wp_ai_client_default_request_timeout filter to make the default request timeout configurable. Use this for the image generation request timeout (#862).

Ændret

  • Content Summary block detection now checks within nested blocks (#810).
  • Move all existing configuration options into a new “Advanced settings” section which is hidden by default (#842).

Rettet

  • Focus restoration after AI setting saves (#812).
  • Added descriptive alt text to AI Home feature card images for improved screen reader accessibility (#819).
  • Prevent Type-Ahead assets from loading on the front end (#820).
  • Dismissing a type-ahead suggestion with escape should not trigger a new suggestion request (#840).
  • Type-ahead ghost text placement and stale suggestions overlapping empty-block placeholders (#847).
  • MutationObserver crash when editor iframe body isn’t ready when using Title Generation (#849).
  • Respect an explicit show_in_abilities value on curated settings, and leave the flag to WordPress core once core declares it (#852).
  • Register initial settings before core/read-settings snapshots them (#856).

Ældre changelog-poster findes i filen CHANGELOG.md.