| 开发者 | monirkhan07 |
|---|---|
| 更新时间 | 2026年11月20日 12:45 |
| PHP版本: | 8.2 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
Yes. Monir Newsroom uses a bring-your-own-API-key model — you obtain API keys directly from Anthropic, OpenAI, and/or Google, and you pay those providers at their published rates. The plugin adds zero markup. This keeps costs transparent and means your API spend is governed by the same billing dashboard you'd use for any direct API project.
Anthropic Claude, OpenAI GPT, and Google Gemini. You can configure as many providers as you have keys for; the router falls back automatically when one is unavailable. Feature images come from Pexels stock photos (optional key) or a bundled placeholder.
Yes. The plugin sends RSS source content, generated drafts, and supporting context to whichever AI provider you configure. Choose providers you trust with your editorial pipeline. Provider settings include direct links to each company's data-handling policies, and the External services section below lists every service with its terms and privacy policy. Self-hosted models are not currently supported.
Not by default. Every beat starts in draft mode: drafts stay as WordPress drafts until an editor clicks Approve and Publish at the Editor's Desk. A beat can be switched to auto-publish, which publishes a draft the moment the Fact-Checker approves it; drafts with concerns or a rejected verdict always wait for an editor. A beat can also queue the drafts an editor approves for the publishing times set on the beat; approval is still the editor's click.
The Provider Health monitor catches credit and auth errors immediately. A "fast-fail" rule marks the provider as failed after a single occurrence (no point retrying when a 401 won't fix itself), and the router cascades to the next available provider. The System Status panel shows which provider failed, the verbatim error message, and a direct link to the provider's billing page. Beat dispatches that would have used the failed provider are skipped pre-flight rather than burning calls into a known-broken endpoint.
Yes. Settings → Routing exposes per-day and per-month spending caps in USD. When spend hits 80% of either cap an alert renders in the admin notice area; when it hits 100% the router stops dispatching new work. Caps reset on the day / month boundary. The Newsroom Dashboard shows today's spend.
Not on its own: drafts are written in the language of their sources. Translation into a publication language (Bengali, Hindi, Arabic, French, Spanish, German, Portuguese and more) is part of the Monir Newsroom Pro add-on.
Placement and styling are customizable — you can choose where in the article the disclosure renders, edit the text, and apply your theme's CSS. The disclosure itself cannot be removed. This is a deliberate architectural rule, not a setting toggle. Schema.org metadata for AI authorship is also always present.
Articles that have already been published stay published with their disclosure blocks intact. Draft articles in the Editor's Desk queue stay as drafts and remain accessible if you reactivate. If you uninstall (delete the plugin), your data is preserved by default — beats, sources, configuration, wire items, pipeline drafts, agent-run history, and per-article editorial metadata (fact-check status, image attribution, AI disclosure tags) all survive a delete-and-reinstall cycle. To explicitly wipe data on uninstall, enable "Delete plugin data on uninstall" at Newsroom → Settings → System Status (Danger zone) BEFORE removing the plugin. Published article post content is always preserved.
Support: https://monirtechsolutions.com/plugins/monir-newsroom/ — include your WordPress version, PHP version, plugin version (Newsroom → Settings → System Status), and a minimal reproduction.
monirnr_ / MONIRNR_ / monirnr- prefix instead of mnr_ / MNR_ / mnr- (WordPress.org requires a distinctive prefix of at least four characters). The REST namespace is now monirnr/v1 and the WP-CLI command is wp monirnr. CSS class names and DOM ids are unchanged.monirnr_ data, so leftover mnr_ tables and options from 1.3.x are not removed; delete the 1.3.x plugin with "Delete plugin data on uninstall" enabled before installing 1.4.0 if you want them gone.monirnr_delete_on_uninstall option.wp_monirnr_beats. On Free, beats are silently locked to en (Translator is a Pro feature). On Pro, the column tracks the operator's per-beat language choice; the per-beat picker UI lands in v1.3. Pre-v1.2.0 the site-wide monirnr_publication_language option could carry a stale value across plugin resets, producing English bodies with non-English image captions — fixed by snapshotting the gated value at draft-create time and reading it back in Photo Editor's attribution path.MONIRNR_Setup_Wizard::handle_save_provider rejects POSTs that lack a test_connection_<provider> success row within the last 30 minutes; failed bypass attempts redirect back to Step 3 with monirnr_wizard_notice=test_required. Wizard test handler now records the test to wp_monirnr_agent_runs so the gate has an audit trail.MONIRNR_Post_Creator. When the Beat Reporter's draft response truncates mid-JSON (Gemini 2.5 Flash counts hidden reasoning tokens against maxOutputTokens, eating the visible budget before the sources field is written), the wp_post_content was previously saved without a Sources block at all despite monirnr_source_urls postmeta carrying valid URLs. Post Creator now detects the absence and synthesises a Sources block from the postmeta URLs using MONIRNR_Source_Names::for_url() for friendly outlet labels. Logged to wp_monirnr_agent_runs with agent_name='post_creator' and event marker defensive_sources_block_appended so operators can monitor frequency.waiting_for_sources and no_matches (recent_drafts=0) render as "Wire warming up" amber; skipped_provider renders as "Provider issue" deep red with a 3px left-border accent. failed + recent_drafts>0 de-escalates to "Active (intermittent)" amber. The rollup uses a 24h wp_posts recent-drafts count to distinguish "terminal failure" from "intermittent run inside a productive day."<ul> for any 2-segment-TLD host (.com.au, .co.uk, .com.bd, .com.br, .co.in). Root cause: MONIRNR_Source_Names::for_url() walked the subdomain chain by mutating $parts and the SLD fallback read $parts[0] after the mutation, landing on the TLD fragment. Fix preserves the original parts array; SLD is read from the unmutated leftmost segment. Added reneweconomy.com.au, theage.com.au, smh.com.au, abc.net.au to the KNOWN outlet map while fixing the fallback.wp_monirnr_beats.last_run_at timezone-unification. The v0.13.0 writer flip to LOCAL had drifted out of sync with every reader (REST API explicitly appended ' UTC'; admin views relied on PHP's default UTC; agent_runs.created_at was always UTC). Operators saw "X hours ago" deltas off by gmt_offset on the Beats card, Dashboard widget, and Pipeline page. Writer flipped back to UTC (current_time('mysql', true)); 3 admin-view readers now append ' UTC' so strtotime() is unambiguous; back-stamp migration maybe_run_v120_tz_unification_migration runs once on upgrade to convert pre-flip LOCAL rows to UTC (DATE_SUB by gmt_offset minutes; supports fractional zones).is_feature_enabled('beats_unlimited') + get_active_beats_count() and renders a Pro-lock pill + disabled button when at the 2-beat Free cap. Counter above the grid reads "X / Y active beats — Pro removes the cap."/beat-status/{id} no longer flags waiting_for_sources and safety_skip as failed:true. Both are informational non-failure states; the pre-v1.2.0 classifier put anything outside success + no_matches into the failure bucket, which short-circuited the pipeline-visibility JS to "Failed" red regardless of the labelmap entry. Now classified as non-failure; pill renders "Wire warming up" / "Skipping" correctly.c:\tmp\v120-soft-reset-v2.php operator tool previously preserved API keys + wizard pick across resets to save re-entry, but a stale invalid Anthropic key carried between cycles concealed the test_connection bypass that Bug 13 fixed. Now clears every monirnr_*_api_key, monirnr_default_provider, monirnr_routing_mode, plus LIKE-pattern sweeps for monirnr_provider_% / monirnr_routing_% / monirnr_route_% / monirnr_agent_provider_% / monirnr_agent_model_%. Truncates wp_monirnr_provider_health. Tooling fix, not plugin code.maxOutputTokens. Affected drafts are skipped automatically (the cluster fails with malformed_draft_json and Beat Reporter moves on); the defensive Sources-block guard above recovers attribution when the body is salvageable but the sources field was cut off. A focused fix (provider thinkingConfig parameter, max-tokens bump to 8192+, or prompt restructure) is scheduled for v1.2.1.min_cluster_size distinct sources (default 3) reporting the same story before drafting. Operators can lower the threshold per beat via Settings → Beats → Edit, or switch the beat from source_filter_mode=auto to curated source picks for faster matching.tools/verify-v1-2-0.php — 294+ scenarios A-AA + nested v1.1.0 chain green.last_run_status and re-encrypt any plaintext API keys.
1.0.5
Hotfix: New AI Draft page now resolves any active provider instead of being hardcoded to Anthropic. Display-only fix; draft generation was already provider-agnostic.
1.0.4
Wizard marquee redesign: Step 2 consolidates source loading + beat picking; Step 4 shows a live pipeline stage list; Step 5 ends on the actual produced article preview. One-time step-state migration for mid-wizard users.
1.0.3
Display-string fix: Beats page no longer renders the misleading "Image source: Global (None)" label on Free first-runs.
1.0.2
Foundation hotfix: Free-tier first-run articles now sideload the bundled placeholder image. Optional Pexels API key slot added to wizard Step 3.
1.0.1
Hotfix: two routing bugs that caused beats to silently fail on fresh installs — the v0.17.1 free-tier routing override now applies to both preflight and dispatch paths, and the wizard's API-key save now goes through the canonical encrypt-and-persist path so provider classes can decrypt. New Test Connection button on wizard Step 4.
1.0.0
First public release. WordPress.org submission preparation: refreshed tagline, placeholder plugin-page assets, submission documentation, GPL-compatibility audit, and Plugin Check pass. Minimum required: WordPress 6.5, PHP 8.1.
0.16.0 - 0.17.1